From 533f28d8e1e82b24d591bbefe8d2635d04e0f487 Mon Sep 17 00:00:00 2001 From: Drinkwater Date: Wed, 1 May 2024 11:59:43 -0400 Subject: [PATCH 01/55] wg-provider-audits Update README.md update meeting table with proper dates and times. Signed-off-by: Drinkwater --- wg-provider-audit/README.md | 13 ++++--------- 1 file changed, 4 insertions(+), 9 deletions(-) diff --git a/wg-provider-audit/README.md b/wg-provider-audit/README.md index 9f56f27e..74f68390 100644 --- a/wg-provider-audit/README.md +++ b/wg-provider-audit/README.md @@ -15,15 +15,10 @@ 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, March 20, 2024 10:00 AM PT (Pacific Time) | | | -| #3 | Wed, April 17, 2024 10:00 AM PT (Pacific Time) | | | -| #4 | Wed, May 22, 2024 10:00 AM PT (Pacific Time) | | | -| #5 | Wed, June 19, 2024 10:00 AM PT (Pacific Time) | | | -| #6 | Wed, July 17, 2024 10:00 AM PT (Pacific Time) | | | -| #7 | Wed, August 21, 2024 10:00 AM PT (Pacific Time) | | | -| #8 | Wed, September 18, 2024 10:00 AM PT (Pacific Time) | | | -| #9 | Wed, October 16, 2024 10:00 AM PT (Pacific Time) | | | -| #10 | Wed, November 20, 2024 10:00 AM PT (Pacific Time) | | | +| #2 | Wed, May 1st, 2024 09:00 AM PT (Pacific Time) | | | +| #3 | Wed, June 19, 2024 10:00 AM PT (Pacific Time) | | | +| #4 | Wed, July 17, 2024 10:00 AM PT (Pacific Time) | | | + ## Contacts From 80e3847189f7f21b32b61d044a86cc7f6ae6b09a Mon Sep 17 00:00:00 2001 From: Drinkwater Date: Wed, 1 May 2024 12:45:37 -0400 Subject: [PATCH 02/55] sig-economics Update README.md update meeting table with meeting times and add meeting links for sig-economics meeting 15 chore: add video link Signed-off-by: Drinkwater --- sig-economics/README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/sig-economics/README.md b/sig-economics/README.md index 9630ac03..11ebb393 100644 --- a/sig-economics/README.md +++ b/sig-economics/README.md @@ -26,8 +26,8 @@ Meetings happen every [First Wednesday of the Month](https://calendar.google.com | #12| Wednesday, January 10, 2024 10:00 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-economics/meetings/012-2024-01-10.md) | [Link](https://github.com/akash-network/community/blob/main/sig-economics/meetings/012-2024-01-10.md#transcript) | [Link](https://gbxszp7zaubg3dskphdcgwpqkjtz3mb3zgtq46ka2yyzzkfij7na.arweave.net/MG8sv_kFAm2OSnnGI1nwUmedsDvJpw55QNYxnKioT9o) | #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, 2024 10:00 AM PT (Pacific Time) | | | -| #16| May, 2024 10:00 AM PT (Pacific Time) | | | +| #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) | | | | #18| July, 2024 10:00 AM PT (Pacific Time) | | | | #19| August, 2024 10:00 AM PT (Pacific Time) | | | From 5db60621711570323046b9974ccaa2d852c74be2 Mon Sep 17 00:00:00 2001 From: Drinkwater Date: Thu, 2 May 2024 09:42:48 -0400 Subject: [PATCH 03/55] Update and rename 014-2024-03-27.md to 014-2024-03-28.md rename the meeting and update meeting notes Signed-off-by: Drinkwater --- .../meetings/{014-2024-03-27.md => 014-2024-03-28.md} | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) rename committee-steering/meetings/{014-2024-03-27.md => 014-2024-03-28.md} (99%) diff --git a/committee-steering/meetings/014-2024-03-27.md b/committee-steering/meetings/014-2024-03-28.md similarity index 99% rename from committee-steering/meetings/014-2024-03-27.md rename to committee-steering/meetings/014-2024-03-28.md index e4f18bfa..690aa49a 100644 --- a/committee-steering/meetings/014-2024-03-27.md +++ b/committee-steering/meetings/014-2024-03-28.md @@ -10,9 +10,9 @@ ## Meeting Details -- Date: Thursday, March 27th, 2024 +- Date: Thursday, March 28th, 2024 - Time: 11:00 AM PT (Pacific Time) -- [Recording](https://aqjulyegruxs4xdwltfkkxqieagkmqc7dcbewovdw2wk7tj72hka.arweave.net/BBNF4IaNLy5cdlzKpV4IIAymQF8Ygks6o7asr80_0dQ) +- [Recording]() - [Transcript](#transcript) ## Committee From 0685681a32aa9a3eb4315085fb802d756c78749c Mon Sep 17 00:00:00 2001 From: Drinkwater Date: Thu, 2 May 2024 09:46:14 -0400 Subject: [PATCH 04/55] steering committee Update README.md update readme table Signed-off-by: Drinkwater --- committee-steering/README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/committee-steering/README.md b/committee-steering/README.md index 9496edfa..c7eb35e3 100644 --- a/committee-steering/README.md +++ b/committee-steering/README.md @@ -27,9 +27,9 @@ The Steering Committee is a special SIG that periodically evaluates the list of | Thursday, December 07, 2023 11:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/011-2023-12-07.md) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/011-2023-12-07.md#transcript) |[Link](https://k6mud4r2ua6xarj6c5zqtkxw6fzjrvzjzu6eotsyhsmotles2gaq.arweave.net/V5lB8jqgPXBFPhdzCar28XKY1ynNPEdOWDyY6ayS0YE) | 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) | | | -| Thursday, April 25, 2024 11:00 AM PT (Pacific Time) | | | -| Thursday, May 30, 2024 11:00 AM PT (Pacific Time) | | | +| 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)|Coming Soon +| Thursday, May 02, 2024 11:00 AM PT (Pacific Time) | | | +| 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) | | | | Thursday, August 29, 2024 11:00 AM PT (Pacific Time) | | | From 7dcd3ecf96b08b069230eda0bb3292a8cd4c64e2 Mon Sep 17 00:00:00 2001 From: Drinkwater Date: Wed, 15 May 2024 14:52:49 -0400 Subject: [PATCH 05/55] sig-design Update README.md update meeting table Signed-off-by: Drinkwater --- sig-design/README.md | 19 +++++++++---------- 1 file changed, 9 insertions(+), 10 deletions(-) diff --git a/sig-design/README.md b/sig-design/README.md index 68a1274d..145cd180 100644 --- a/sig-design/README.md +++ b/sig-design/README.md @@ -30,16 +30,15 @@ date: 2023-1-09T00:19:20-08:00 | #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| April, 2024 08:00 AM PT (Pacific Time) | | | -| #17| May, 2024 08:00 AM PT (Pacific Time) | | | -| #18| June, 2024 08:00 AM PT (Pacific Time) | | | -| #19| July, 2024 08:00 AM PT (Pacific Time) | | | -| #20| August, 2024 08:00 AM PT (Pacific Time) | | | -| #21| September, 2024 08:00 AM PT (Pacific Time) | | | -| #22| October 2024 08:00 AM PT (Pacific Time) | | | -| #23| November, 2024 08:00 AM PT (Pacific Time) | | | -| #24| December, 2024 08:00 AM PT (Pacific Time) | | | -| #25| January, 2025 08:00 AM PT (Pacific Time) | | | +| #16| May, 2024 08:00 AM PT (Pacific Time) | | | +| #17| June, 2024 08:00 AM PT (Pacific Time) | | | +| #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) | | | +| #21| October 2024 08:00 AM PT (Pacific Time) | | | +| #22| November, 2024 08:00 AM PT (Pacific Time) | | | +| #23| December, 2024 08:00 AM PT (Pacific Time) | | | +| #24| January, 2025 08:00 AM PT (Pacific Time) | | | ## Leadership From 511182273fb74417c6240ca2428248efacd0533e Mon Sep 17 00:00:00 2001 From: Drinkwater Date: Fri, 17 May 2024 11:13:09 -0400 Subject: [PATCH 06/55] steering committee Update 014-2024-03-28.md update copy and title Signed-off-by: Drinkwater --- committee-steering/meetings/014-2024-03-28.md | 4 ---- 1 file changed, 4 deletions(-) diff --git a/committee-steering/meetings/014-2024-03-28.md b/committee-steering/meetings/014-2024-03-28.md index 690aa49a..2e6a5e13 100644 --- a/committee-steering/meetings/014-2024-03-28.md +++ b/committee-steering/meetings/014-2024-03-28.md @@ -141,10 +141,6 @@ Discussions: - Community to participate in open discussions on Github. - - -# **Transcript** - # **Transcript** _This editable transcript was computer generated and might contain errors. People can also change the text after it was created._ From f29951c7970a1de2d758a1cf2280fbda2e26973a Mon Sep 17 00:00:00 2001 From: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Date: Fri, 24 May 2024 11:13:41 +0000 Subject: [PATCH 07/55] Create meeting notes for sig-chain #14 (#585) * Create meeting notes for sig-chain #14 Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> * sig-chain Update 014-2024-03-12.md add recording and transcript Signed-off-by: Drinkwater --------- Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Signed-off-by: Drinkwater Co-authored-by: Drinkwater --- sig-chain/meetings/014-2024-03-12.md | 173 +++++++++++++++++++++++++++ 1 file changed, 173 insertions(+) create mode 100644 sig-chain/meetings/014-2024-03-12.md diff --git a/sig-chain/meetings/014-2024-03-12.md b/sig-chain/meetings/014-2024-03-12.md new file mode 100644 index 00000000..f74545f4 --- /dev/null +++ b/sig-chain/meetings/014-2024-03-12.md @@ -0,0 +1,173 @@ +# Akash Network - Chain Special Interest Group (SIG) - Meeting #14 + +## Agenda + +- Overview of recent and current governance proposals +- Discussion of recent proposal on minimum deposits +- Update on mainnet network upgrade proposal +- Scheduling of planned network upgrade + +## Meeting Details + +- Date: Tuesday, March 12th, 2024 +- Time: 08:00 AM PT (Pacific Time) +- [Recording](https://bwp7ef3o435ht3azllxhma3vbj4u4x4zgtlx3tfc44gjnjkanyqa.arweave.net/DZ_yF27m-nnsGVrudgN1CnlOX5k0133MoucMlqVAbiA) +- [Transcript](#transcript) + + +## Participants +- Artur Troian +- Joao Luna +- Maxime Beauchamp +- Rodrigo Rochin +- Scott Carruthers +- Tyler Wright + +## Meeting Notes +### Introduction and Updates +#### Tyler Wright +- Tyler Wright welcomed everyone to the Sig Chain monthly meeting #14. +- The meeting focuses on the Akash blockchain, Cosmos SDK, governance proposals, and network upgrades. +- Validators and community members are encouraged to join and participate. +- Tyler acknowledged the efforts of validators in voting on proposals. +- Currently, there are three active proposals onchain. +- A recently passed proposal concerns decreasing minimum deposits for deployments and transactions on the tenant and provider sides. +- This change has been tested and is functioning correctly. +##### Active Proposals: + - Highlighted the community and spheron team's contributions to recent discussions leading to parameter changes. + - Specifically mentioned an important active proposal regarding the main upgrade to version 0.332.0. + - Voting for this proposal is ending soon, within the next few hours. + - If passed, a network upgrade is scheduled for tomorrow at 12:37 Eastern Time (UTC conversion to be provided). +- **Network Upgrade Discussion** + - **Tyler Wright** + - Core engineering team led by Artur Troian. + - Messaging about the upgrade will be shared on various channels. + - Documentation updated and available on the docs site. + - Information will be disseminated through Discord and other platforms. + - **Artur Troian** + - Upgrade expected to be quick and easy, minimal downtime. + - Reminder about the US daylight savings time shift; upgrade at 1pm EST. + - First network upgrade of the year, a minor but important change. + - Anticipation for more upgrades later in the year. + - Plan to present and discuss future proposals and enhancements. + - Encouragement for feedback on blockchain improvements. +- **Network Upgrade Discussion (Continued)** + - **Rodrigo Rochin** + - Asked about the lowering of provider AP requirements. + - Queried if it is now cheaper to deploy and have providers. + - **Tyler Wright** + - Confirmed the parameter change from 5 AKT to 0.5 AKT for both provider and deployer sides. + - Proposal 248 outlines the changes. + - Clarified that the parameter change has been tested but defaults to 5 AKT and needs manual adjustment. + - **Scott Carruthers** + - In the process of testing the provider side for the bid minimum deposit. + - Deployment creation using 0.5 AKT is working perfectly. + - Mentioned the need to use a deposit switch when creating deployments via Akash CLI, which defaults to 5 AKT. + - Cloudmos team can set the default to 0.5 AKT on their platform. + - Announcements will be made once provider side testing is complete. +- **Core Engineering Team and Contributions** + - **Tyler Wright** + - The core engineering team is growing with significant community contributions. + - Focus on managing more engineering tasks related to the core product. + - Network upgrades and Sig Chain projects to be included in the product and engineering roadmap. + - Items will be tagged in the backlog section for easy access. + - Aim for transparency and communication through roadmap discussions. +- **Network Upgrade Clarifications** + - **Scott Carruthers** + - Clarified the adjustment lowering provider attribute update prices as part of the network upgrade scheduled for tomorrow. + - Lowering of minimum bid and deployment deposits (already in effect due to a proposal passed yesterday) is separate from the provider attribute update fee reduction. + - **Artur Troian** + - Will release a new CLI version after the network upgrade to include updated default values. + - Historically, the CLI used hardcoded default parameters, but the new release will query the current default bid and deployment deposits if not set manually. + - **Maxime Beauchamp** + - Cloudmos updated to query on-chain parameters, setting the default to 0.5 AKT. + +## Action Items +- Validators and participants are reminded to vote on the active proposal if they haven't already. +- Group to prepare for the planned network upgrade scheduled for tomorrow if the proposal passes. +- Tyler to attach Proposal 248 for Rodrigo. +- Scott to complete provider side testing and communicate the results. +- Cloudmos team to potentially adjust the default deployment parameter to 0.5 AKT. + +# **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. It's a Sig chain monthly meeting number 14. During these blockchain related special interest groups the community goes over anything related to the cost blockchain Cosmos SDK specific governance proposals Network upgrades. So anybody again interested in any of those kinds of topics? This is something that we always invite validators to even though it's recorded and transcribed again folks can manage their identities and just join these meetings and just that they have any specific questions about anything related to Network upgrades validating on the cost or just the cost blockchain. This is a special interest group to join and participate in + +Tyler Wright: I know there's been a number of proposals that have gone on change. So thank you to all the validators that have been voting on those proposals believe there's three active proposals on chain right now and one that recently passed yesterday related to decreasing the minimum deposits around deployment and in transactions on the tenant side in the provider side, so I know that's been checked and tested by the core team and it's working properly so much appreciate the efforts. + +Tyler Wright: Four team and some folks with the community that helped to bring that conversation to light during previous special interest groups for providers clients Etc that led to again that parameter change, but I know there's a couple of active proposals on chain one that I want to specifically talk about that. I hope that folks have voted on is around the main upgrade to version zero that 332.0 again. This proposal is still on chain for boat in the boat is scheduled to end very shortly over the next couple of hours if it is scheduled to pass right now and if it passes there is a planned Network upgrade for tomorrow that plan Network upgrade is for 1237 + +Tyler Wright: Eastern time I'll transfer that over to UTC for folks, but it's a little bit over a day from right now. So again that proposal is still on chain. It folks have not voted on that proposal. You have a little bit of time to do so and if it passes which is on schedule to pass right now, there is a plan Network upgrade plant for tomorrow. Archer so I know is + +Tyler Wright: leading the core engineering team. I don't know if you have anything that you want to add specifically about that may not upgrade again. We'll put some messaging out in various channels documentation has been updated and that will be shared. It's available in the docs site right now, but I will be shared and Discord and Elsewhere for folks to have easy access to but our try and up with anything that you specifically want to talk about about the network upgrade that's planned to schedule for tomorrow. + +Artur Troian: Thanks, I thank you card everything. We're going to spend the upgrade should be quite quick. It's quite a easy change. So I don't expect any long down times. Just the only reminder that you to the daylight savings time shift for folks in the US. It's supposed to be non-face EST but not is going to be like 1pm EST. + +Artur Troian: And yeah so it's a little bit shift, but you Expected time in UTC should be good. Wouldn't that but yeah, that's gonna be the first network of great for this year. It's a little bit minor and sort of not one that we have planned, but I'm glad that we are executing that. + +Artur Troian: I really hope that later down this quarter. We will be able to execute others that we have planned. At the end of the year for the expected proposals and for the least titles and so forth. So we have a lot of things in our table. At this moment, which we are sorting cleaning up and actually priorities. Hopefully by sometimes of these months you will be able to present it to everyone and maybe open some discussions might be gonna have some feedback on things that people want to have on blockchain. But other than that, I think you're all good. + +00:05:00 + +Tyler Wright: Arctic just mentioned as the core engineering team continues to grow a little bit and there's been a great deal contribution from a number of members of the community some of which are on this call. + +Tyler Wright: There's going to be a concerted effort to again handle a lot more on the engineering side with the core product. So again, very exciting time for head anything that's related to Sig chain, some of the network upgrades that we've talked about in the past that previous Big Chain monthly meetings. Those things will all be tagged inside of a product and Engineering roadmap. I said change so if you look in the backlog section again, maybe in the next month or so you'll look at it. You'll see a number of items. I'll be added to just that roadmap and again anything that maybe Network upgrade related will be tagged with big chain. So that easily accessible for validators or other folks that maybe focus on anything just chain related. + +Tyler Wright: But again the core team and again, we do this as a part of steering committee as well will continue to make as many things available as part of the roadmap just for discussion and communication transparency. + +Tyler Wright: Of course. Is there anything else that anybody wants to talk about related to blockchain Rodrigo hand up. Go ahead. + +Rodrigo Rochin: as a quick question at the beginning you said all the lowering provider AP requirements tests and I believe you said the parameter over to place so now it's cheaper to Deploy in and have the providers and if so how much it was it okay, I mean drinking tea. + +Tyler Wright: Yeah, so, I will attach a proposal for you, but the parameter change was from five akt to 0.5 akt on for both provider side and the deployer side again attach that the proposal 248. + +Rodrigo Rochin: That things I did vote in it, but I forgot if it was going to be three or something. + +Tyler Wright: Yes, so it's 0.5. Scott correct me if I'm wrong, but we know that the parameter change when the effect and it's been tested but I believe by default. It's still at five akt and has to be manually switched for some folks. Maybe not on the deployer side because I know the cloud most team also made some changes their product to That affected the parameter change, but Scott. Do you want to chime in here real fast? + +Scott Carruthers: yeah, so if you're creating a so, I'm actually in the middle of doing the provider side testing of the bid minimum deposit that I've done full testing from the deployment creation. Perspective and it's working perfectly. So this morning I created deployments using point five akt and no issues at all. As Tyler was alluding to if you created deployment from the Akash CLI currently the default is still five. Akt. So if you're creating a deployment you would have to use they deposit switch and then using the deposit switch. You could decrease it all the way down to 0.5. Akt but the minimum always at this point from the CLI is still + +Scott Carruthers: five akt and then from the cloud most side. Obviously, they can control that and Max. I don't know if you have any thoughts on this but obviously on the almost side if they wanted to make the defaults 0.5 and I think it would be able to do that within their code. + +Scott Carruthers: So that there will be a number of announcements about this as So I'm almost there. They provider side testing. Of the minimum bid deposit. So as soon as've done I'm done validating that which I should be able to do in the next half hour. There will definitely be communication and these regards + +Rodrigo Rochin: Awesome things. Yeah, I was basically asking because I wanted to update my provider and in my provider from attributes I have been waiting for this to test to that's been more than I needed to. evaluated announcements + +00:10:00 + +Scott Carruthers: Rather Rodrigo,… + +Tyler Wright: Go ahead. + +Scott Carruthers: let me just make sure there's Clarity on. the Adjustment that we're making that is going to lower the prices of Provider attribute updates. That's part of the network upgrade tomorrow. So we have that that will be solved by the network upgrade what we're currently talking about is. Just lowering of the minimum bid deposits and the minimum deployment deposits. So those are two separate things. Those are already in effect because of the network proposal that passed yesterday, and then they lowering of the gas and the fees for Provider attribute updates will go in effect with the network upgrade tomorrow. + +Tyler Wright: Thank you, Scott. Go ahead. Our turn then Max following. + +Artur Troian: He just real quick on the default and deposit value I'm going to cut releases CLI tomorrow after Network rate, so it's gonna include values because what happens is the historically did not quite old parameter. From the network. We just use the Assumption the one that is default hardcoded and then we put in Genesis, but you've been pretty much changing that. and so what I'm gonna do is we got the CLI will query default beat and deployment deposits if they are not sad manually. + +Artur Troian: they're gonna have it right for tomorrow. + +Tyler Wright: Perfect. Thank you Archer. Go ahead. + +Maxime Beauchamp: Yeah, just wanted to mention that we updated the cloudnos so that it queries from the parameteron chain. So the default is based on the Unchained parameter. So it's 0.5 a kitty. + +Maxime Beauchamp: That's it. + +Tyler Wright: Thank you Excellent. So as Artur mentioned some of those changes will be reflected in the CLI after the network upgrade tomorrow, but Scott also mentioned it can be done currently via CLI just with a little bit extra code. So it is working. + +Tyler Wright: I know again we have a little bit over an hour and a half until that mainnet upgrade proposal passes and then again as Scott had mentioned and I mentioned as well. There'll be a number of announcements that'll be shared in Discord and Elsewhere for folks in the community validators Etc. + +Tyler Wright: So, please look out for those announcements and then anybody's on the Insiders or vanguards, I'll continue to share those announcements so that everybody is up to date and ready for the upgrade schedule for tomorrow. I'll make sure to Highlights the time difference and then again reference a time in UTC for the upgrade announcement and for the upgrade timing and then I'll also update any other meetings on the Discord side that may be showing the wrong time currently. Is there any other questions that anyone has related to the cost blockchain or anything else Sig chain related that they want to discuss today? + +Tyler Wright: it's not much appreciate everyone's time today. Again, please look out for a number of announcements that will be shared on Discord and elsewhere in the coming hours. Again, if you haven't voted on any of the proposals on chain right now, please feel free to do so if thank you very much and much appreciate everyone's time here today. I hope everyone has a great rest of their day. Feel free to reach out to me if you need anything, but thank you all. See many of you tomorrow for the upgrade. + +Maxime Beauchamp: Think so + +Scott Carruthers: concern + +Rodrigo Rochin: Thank you. + +Meeting ended after 00:14:53 👋 + From b2b8e73db0bd0df7ee63505982a592e07011dce0 Mon Sep 17 00:00:00 2001 From: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Date: Fri, 24 May 2024 11:16:48 +0000 Subject: [PATCH 08/55] Create meeting notes for Sig-Chain #15 (#586) * Create meeting notes for Sig-Chain #15 Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> * Update 015-2024-04-09.md add transcript for meeting 15 Signed-off-by: Drinkwater * Update 015-2024-04-09.md add recording Signed-off-by: Drinkwater --------- Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Signed-off-by: Drinkwater Co-authored-by: Drinkwater --- sig-chain/meetings/015-2024-04-09.md | 148 +++++++++++++++++++++++++++ 1 file changed, 148 insertions(+) create mode 100644 sig-chain/meetings/015-2024-04-09.md diff --git a/sig-chain/meetings/015-2024-04-09.md b/sig-chain/meetings/015-2024-04-09.md new file mode 100644 index 00000000..59285c4c --- /dev/null +++ b/sig-chain/meetings/015-2024-04-09.md @@ -0,0 +1,148 @@ +# Akash Network - Chain Special Interest Group (SIG) - Meeting #15 + +## Agenda +- Review of Previous Meeting +- Discussion of network upgrade +- Proposals on chain for vote. +- Open discussion + +## Meeting Details + +- Date: Tuesday, April 9th, 2024 +- Time: 08:00 AM PT (Pacific Time) +- [Recording](https://qv5qbltorrogit5i3qvsihngxzevuweduyauwodu5rk3yhysu3xq.arweave.net/hXsArm6MXGRPqNwrJB2mvklaWIOmAUs4dOxVvB8Spu8) +- [Transcript](#transcript) + + +## Participants +- Artur Troian +- B S +- Massv +- Maxime Beauchamp +- Rodrigo Rochin +- Scott Carruthers +- Trigs _ +- Tyler Wright + + +## Meeting Notes +#### Tyler Wright: + - Tyler Wright welcomed everyone to the 15th SIG Chain monthly meeting. + - Meetings cover Akash blockchain network upgrades and validator-related issues. + - Tyler thanked those participating in the validators channel and SIG chain. + - Special thanks to those preparing for network upgrades. +### Network Upgrade Discussion +#### Tyler Wright + - The Akash Mainnet 10 upgrade occurred on March 13th. + - Upgrade was smooth and fast with minimal issues. + - Thanks extended to the core team and validators for their efforts and voting. + - Everyone was prepared for the upgrade on March 13th. +### Tyler Wright Update + - Mentioned several proposals that have gone on-chain and either passed or failed in the last month. + - Encouraged validators for their voting participation. + - Highlighted proposal 255 for community funding for Praetor acquisition, which is currently up for vote. + - Directed questions about proposal 255 to the GitHub discussion forum. + - Noted there are about three days left to vote on proposal 255. + - Successfully completed the mainnet 10 upgrade. + - Recognized the active participation of validators and the general community in voting on various proposals. +#### Future Network Upgrades + - Mentioned upcoming network upgrades and past discussions about the Sig chain. + - Noted the small size of the core team and their focus on multiple projects. + - Anticipated more updates on network upgrades soon. + +### Artur Troian's Updates + - **Cosmos SDK 47 Upgrade:** + - Preparation has begun for upgrading to Cosmos SDK 47, planned since last year. + - Currently gathering necessary information and planning the upgrade approach. + - The upgrade will be extensive, requiring thorough planning and testing. + - Previous successful upgrades attributed to thorough testing; the same will apply to this upgrade. + - Cosmos SDK 47 introduces significant changes from version 45, impacting the blockchain and associated projects. + - Identification of necessary updates and migrations is ongoing, with a detailed plan to be developed. + - Estimated timeline for completion is a couple of months. + - **Interchain Accounts (ICA) Proposal:** + - A recent PR regarding Interchain Accounts was not accepted due to current priorities. + - Need for ICA should be discussed and requested first. + - **Importance of Cosmos SDK Upgrade:** + - Current SDK version is deprecated, limiting functionality and compatibility, particularly with IBC versions. + - Upgrade necessary to avoid compatibility issues and support newer IBC versions. + - Extensive client updates will be required. + ### Network Upgrades and Cosmos SDK 47 + #### Tyler Wright: + - Strategies for upcoming network upgrades and the larger project of upgrading to Cosmos SDK 47 are being finalized. + - Plans and updates will be added to the public roadmap. + - Support tickets with the tag "sick chain" will be created for tracking purposes. + - At least one network upgrade is planned before the larger Cosmos SDK 47 upgrade. + - Validators and community members are encouraged to stay involved via Discord. + - Validators can opt into an email list for updates on votes, network upgrades, etc. + - Contact Tyler Wright or another core team member to be added to the email list. +### Validator Communication + - Validators are encouraged to stay active on Discord for updates and announcements. + - Contact information for validators is essential for emergencies and updates. + - Validators can reach out to Tyler Wright or core team members to ensure they have the correct roles on Discord or to provide an email if they prefer not to use Discord. +### Closing Remarks + - Appreciation for participants' time and efforts. + - Look out for upcoming announcements regarding network upgrades. + - Meeting adjourned with thanks from Tyler Wright, Rodrigo Rochin, and Maxime Beauchamp. +## Action Items +- Core Team to continue monitoring the network post-upgrade for any arising issues. +- Validators to provide feedback and report any issues encountered post-upgrade. +- Tyler Wright to add finalized plans for network upgrades to the roadmap and create support tickets with the "sig chain" tag. +- Tyler Wright to ensure validators are added to the email list and have proper roles on Discord. +- Artur Troian to continue planning and gathering information for the Cosmos SDK 47 upgrade and communicate progress and updates to the community. + +# **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 seg chain monthly meeting number 15. During the chain special interest group monthly meetings the cash community and all participants in this Specialist Group come together to discuss all things related to the Akash blockchain Network upgrades anything validated related. So again much appreciate the participation from those that are reach out in the validators channel as well as sick chain and thank you to all those that's getting those ready for all the network upgrades and of our last monthly meeting which was March 12th. That was one day prior to the most recent Network upgrade that network of great happened on March 13th to a class main 10. + +Tyler Wright: thanks in part to the core team as well as all the validators that Network upgrade was quite smooth and very fast and again have seen not too many issues since that upgrade has become So again much appreciated everybody that helped vote on the upgrade. We're ready for the upgrade when it happened on March 13th. in addition there have been a number of + +Tyler Wright: Proposals that have gone on chain and have passed or failed over the last month. Thank you all to all those who have been voting. There's one proposal 255 for Community funding for prayer requisition that is up for vote right now. If you have any questions about that, there is a GitHub discussion where you can get involved and asking any questions, but again much appreciate the validators for voting and their active participation may pass Network. Believe it's about three days left to vote there. + +Tyler Wright: So again out of the last month and meeting the group is focused on getting ready for the mainnet 10 upgrade which is since happened successfully as As a number of items on chain related to proposals and votes that again the validators have been very active as well as the general community and voting and participating in the vote. that's getting us caught up to speed. I know there's a couple of network upgrades that I've been talked about in past the Sig chain, but with the core team quite small and working on a number of different things. I'm sure that there will be more updates on upcoming Network upgrades happening soon. I do want to hand it over to Artur to see if there's anything that he wants to add about. + +Tyler Wright: The cost blockchain upcoming upgrades if there's any details to share here today. Otherwise, we can talk async and people can look at the roadmap as well as safe change to score Channel. But again without further Ado, I'll hand it over to Archer to see if there's anything that he wants to talk about related to a Specialist Group chain. + +Artur Troian: Things are more than everyone. yeah, so to start recovered everything in great details. The only thing I would like to add is have started preparation for upgrading to cosmosis Decay 47 so it's been planned since last year that we going to executed some time during this year. The planning means we are just Gathering all the information we need. For us to start work on this upgrade is gonna be rather big and heavy we need to come up with the approach has to be really thorough. + +Artur Troian: Third band for all the aspects and including testing. So the pasta graze that we had during the last year actually over here have been pretty much solid in one of the reasons it was that way because of the testing there's gonna be no exception obviously for the upcoming because as the care grade, but let's say the customer is okay undergo quite drastic changes from 45 to 47 and those changes need to be reflected in all the Blockchain as well as the project things including clients and so forth. So the plan for now is next. We got our identify all the things that needs to be on dated all the migrations gonna have quite thorough. a plan written down + +00:05:00 + +Artur Troian: on that as soon as we confident That we have changes during upgrade and required. Then you're gonna start working on the actual upgrade itself. So it's gonna take some time. I think my maybe couple months But yeah, I'm glad that we officially getting to the stage. and so any questions to this announcement. + +Artur Troian: Okay, so there was a one PR to the note repo in regards to Interchange accounts. So if that person is here listening, we are not going to accept that at this stage. Simply because it's not just a priority and the question is why the ICA needs to be enabled? + +Artur Troian: before going on that has to be discussion first. There has to be, request first, but just like there is pretty much about my only miscrap. Is that using correct great name, but that's easy to fix. But other than that. We won't be able to take it at the stage and just doesn't make sense. Right? So. + +Artur Troian: that person is listening? Yeah, let us know you can reach out and we can discuss through those steps if the ICA I actually required by some other projects. soon so your question about what Christmas Decay brings. It's not pretty much for the cosmosis Decay brings. It's rather the current version we use is in deprecated all the year ago and there are no that's issued. That limits us for example what IBC version we can use we still may be see before which currently is the I think six seven version. So at some point we might be + +Artur Troian: In compatible with some chains and I'm not saying it's gonna actually happen but you just limits what we can do it puts the burden on the relayers as well to keep support for old versions of the IBC. You just probably not a good thing and in overall this SDK just brings also importance also also this poems actually I should say but We just have to make it unfortunately, so there's no way for us to holding ourselves from this change and they're gonna be quite a lot of actually client updates. So that's why the first of all they're gonna be playing price quite thorough all followed by the preparation of the brain cell. + +Artur Troian: All There's no more questions. Tell her about you. + +Tyler Wright: excellent thank you very much Artur again as + +Tyler Wright: Strategies around upcoming Network upgrades as well as this bigger project around upgrading to kazos SDK 47 as plans get more finalized. They will be added to the facing roadmap as well as there will be support tickets made with the tag sick chain. So that in this group as well as folks in the community community can track those various tickets again, I believe there's a plan to have at least one network upgrade apply prior to this bigger Cosmo sdk47 upgrade, but please stay involved in Discord. If anybody here is a validator and wants to be added to an email list that goes out to folks that opt into that email so that they can get update. + +Tyler Wright: Of Discord or anything related to votes Network upgrades Etc. Feel free to reach out to me or another member of the core team so you can be added to that email list. But again, as items continue to be more defined if anybody has any specific questions about next steps how it will impact anything from clients to the general cash Network. Feel free to drop those in again. Look out for updates in the roadmap and the product and Engineering roadmap as well as in the support repo with a tags under sick chain. + +00:10:00 + +Tyler Wright: Does anyone else have any topics that they want to discuss related to the Akash blockchain? or validator relations + +Tyler Wright: then again what continue to work together online? And again, please please if you are not actively and Discord, it's also people listening in later. Please make sure that you add yourself to the email list for all validators and active sets. it's required that there's a way to contact you. We have a way to contact almost everybody. But again just in case of emergency just in case in any issue, please make sure to check Discord frequently. There's a number of items that go into valid or announcements as well as the If anybody from your technical team that is a part of their validator. It doesn't have the proper role again reach out to myself for somebody from the core team or we'll get that rectified. But if you prefer to stay out of Discord for whatever reason, please share an email with me just so we have again an up-to-date contact just in case we need you for any short-term or long-term efforts. + +Tyler Wright: But there's nothing else then again much appreciate everyone's time and effort today will continue to talk async and again look out for announcements related to a number of upgrades potentially on the horizon that are being planned and we'll be finalized soon. But thanks again for everybody taking the time up today to meet very quickly, and I hope everyone has a great day and week. Thank you all. + +Rodrigo Rochin: And kills you. + +Maxime Beauchamp: Yeah. Thanks Tyler. + +Tyler Wright: Goodbye. + +Rodrigo Rochin: Bye. + +Meeting ended after 00:12:13 👋 + From c04b2edc46151efc1fc05418e570cf141f21b135 Mon Sep 17 00:00:00 2001 From: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Date: Fri, 24 May 2024 11:24:28 +0000 Subject: [PATCH 09/55] Create meeting notes for sig-economics #16 (#578) * Create meeting notes for sig-economics #16 Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> * sig-economics Update 016-2024-05-01.md add transcript for meeting 2024-05-01 chore: add video Signed-off-by: Drinkwater * Update 016-2024-05-01.md add recording link Signed-off-by: Drinkwater --------- Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Signed-off-by: Drinkwater Co-authored-by: Drinkwater --- sig-economics/meetings/016-2024-05-01.md | 487 +++++++++++++++++++++++ 1 file changed, 487 insertions(+) create mode 100644 sig-economics/meetings/016-2024-05-01.md diff --git a/sig-economics/meetings/016-2024-05-01.md b/sig-economics/meetings/016-2024-05-01.md new file mode 100644 index 00000000..08454aca --- /dev/null +++ b/sig-economics/meetings/016-2024-05-01.md @@ -0,0 +1,487 @@ +# Akash Network - Economics Special Interest Group (SIG) - Meeting #16 + +## Agenda +- Updates since last monthly sig-economics meeting. +- Updates on provider incentives. +- Open discussions on recent proposals and events +- Open up to community for ideas or concerns. + +## Meeting Details +- Date: Wednesday, May 01, 2024 +- Time: 10:00 AM PT (Pacific Time) +- [Recording](https://w6djeix4uozea7pt7fdzqmhenlvt6jf72c4x26cz3brkuboazjsa.arweave.net/t4aSIvyjskB98_lHmDDkaus_JL_QuX14WdhiqgXAymQ) +- [Transcript](#transcript) + +## Participants + +- Adam Wozney +- Cheng Wang +- Joe Deng +- Nick Merrill +- Scott Hewitson +- Tyler Wright +- Zach Horn +- Zeke E + +## Meeting Notes +### Introduction and Updates +#### Scott Hewitson +- Opening remarks, welcoming everyone to the meeting. +- Mentioned the longevity of the meetings, reaching double digits, and the usual format of covering previous discussions, proposals, updates, and open discussion. +- Invites participants to share any proposals or updates since the last meeting. +- Updates on community pool spend, specifically mentioning praetor Acquisitions and their commitment to open sourcing their code. +- Indicates no significant funding requests or discussions, mostly early stage talks. +- Asks Tyler for any pertinent discussions or funding requests related to sig economics. +- Transition to reviewing discussions and proposals from the last month's call. + +### Recap from Last Meeting +#### Scott Hewitson +- Clarifies that note-taking responsibilities have been delegated to community members as part of bounties. +- Provides updates from last month's meeting, mentioning discussions on provider incentives, GPU capacity fluctuations, scheduled maintenance, praetor acquisition, and Coinbase learn and earn program. +- Reports 500,000 activations for the Coinbase learn and earn program. +- Mentions a large governance proposal discussed during the meeting. +- Encourages attendees to check out meeting notes on GitHub for detailed information. +- Passes the floor to Cheng for any updates before addressing his own agenda item. + +### Updates from Cheng +- Provides updates on Coinbase Learn program, mentioning that approximately 98% of the 500,000 users who completed the Akash quest were new to AKT. +- Reports on the first pilot for provider incentives, stating that approximately $1.5 million of the allocated budget has been spent, with the remaining balance between four and a half to five million dollars. +- Mentions upcoming staking quest integration and plans for the next campaign, which will include deeper engagement with Akash tools like Chat or SCXology. +- Indicates that the first campaign will continue for continuity before transitioning to the second campaign. +### Discussions on Community Pool Spending and Provider Incentives +- Scott Hewitson: Discusses transparency regarding community pool spending and provider incentives. +- Cheng Wang: Reports approximately $3.5 million spent from the original pool, with over a million dollars remaining for phase one of the incentives. +- Scott Hewitson: Plans to introduce a dashboard or tracker for provider incentives to enhance transparency. +- Cheng Wang: Provides details on GPU provider diversity and ongoing conversations. +- Tyler Wright: Shares a discussion from the forum about engaging a content writer to promote finance listings, seeks input for Sig Design meeting. +- Zach Horn: Offers to review the proposal and suggests further action once more information is available. +- Scott Hewitson: Acknowledges the potential for exposure to retail investors through community initiatives like "akt to the moon" on CoinGecko. +- Scott Hewitson: Thanks Tyler for bringing attention to the discussion. +### Proposed Tenant Incentives Program +- Scott Hewitson: Introduces his idea for tenant incentives, inspired by two-sided marketplaces like Uber, and proposes utilizing the upcoming network upgrade to implement the program. +- Zach Horn: Offers insights on the proposed tenant incentives program, suggesting a crawl-walk-run approach and emphasizing the importance of quick implementation and testing. +- Scott Hewitson: Acknowledges Zach's input and agrees on the importance of moving quickly with the implementation. +- Zach Horn: Expands on the idea of integrating the tenant incentives program into the Akash website as a user-friendly option for newcomers. +- Cheng Wang: Comments on the technical challenges and the efforts of the engineering team in enabling features like authz within the Akash network. +- Nick: Raises a point regarding the technical considerations and expresses appreciation for the engineering team's efforts. + +### CosmosWasm for Potential Implementation of Tenant Incentives +- Nick Merrill: Suggests considering CosmosWasm for potential implementation of tenant incentives and highlights its benefits in terms of ease of use and auditing. +- Scott Hewitson: Confirms the absence of cosmoswasm or smart contract functionality in Akash and discusses Greg's stance on increasing the attack surface of the network's codebase. +- Cheng Wang: Agrees with Greg's approach and emphasizes the importance of a well-proven and bulletproof use case before considering integration of smart contracts. +- Nick Merrill: Advocates for CosmosWasm, highlighting its battle-tested nature and cost-effectiveness in smart contract auditing. +- Scott Hewitson: Reflects on the evolution of CosmosWasm and acknowledges the initial concerns around smart contracts in the ecosystem. +- Nick Merrill: Discusses the stigma associated with smart contracts and emphasizes the need for cautious consideration in their implementation. +- Scott Hewitson: Encourages Nick to share any further ideas or suggestions on GitHub discussions for broader community input. + +### Akash console 2.0 +- Cheng Wang: Discusses the ongoing discussions within the core team regarding the development of Akash console 2.0, focusing on the integration of cloudmos back into the platform and the implementation of features such as payment via credit card. +- Scott Hewitson: Provides context on the upcoming authZ fix and its implications for console 2.0, explaining how it will streamline transactions and facilitate credit card payments. +- Cheng Wang: Expands on the potential workflows enabled by the authZ fix, emphasizing its role in removing barriers to transactions and improving user experience. +- Scott Hewitson: Highlights the significance of the authZ fix in preventing issues such as unused funds in leases, expressing excitement for its implementation. +### Other Matters Discussed +- Nick Merrill introduces DAO tooling for the Cosmos ecosystem, highlighting cross-chain functionality and sub-DAOs. +- Scott Hewitson discusses challenges with community spend props and explores the concept of vesting schedules for props. +- Nick Merrill shares information about Polytonic as a potential solution for implementing vesting schedules without requiring a Cosmos SDK upgrade. +- The team expresses interest in exploring Polytonic further and discusses its potential integration into the Akash network. +- Scott Hewitson emphasizes the importance of open and collaborative discussions within the community. +- The meeting concludes with appreciation for Nick's insights and a reminder to continue exploring potential collaborations and innovations. +## Action Items +- Tyler Wright: Follow up with the content writer found on Discord regarding participation in the Sig Design meeting. +- Zach Horn: Review the proposal shared by Tyler and provide feedback or further action as necessary. +- Scott Hewitson: Explore potential collaboration with community initiatives such as "akt to the moon" on CoinGecko for retail exposure. +- Scott Hewitson and Zach Horn: Collaborate on creating a type form for tenant incentives using authz and consider integration into the website as a deployment option. +- Scott Hewitson & Cheng Wang: Initiate discussion with the engineering team regarding the technical feasibility and implementation of the tenant incentives program. +- Nick Merrill: Collaborate on putting forth a proposal in the discussion forum regarding the implementation of vesting schedules. +# **Transcript** + +_This editable transcript was computer generated and might contain errors. People can also change the text after it was created._ + +Scott Hewitson: All right, GM everybody those that are here and those that may be listening have another time today is another installment of big economics. I know we're in a double digits now, we've been having these for quite a while so It's been fun. Usually how we go with. These are cover a little bit from the last meeting and then go to any discussions any live proposals and talk about any of those kind of things and then you usually have a few agenda items usually some things to update folks on some of the programs we got going on and then we usually open it up to trick questions or ideas or basically anything goes for anyone that wants to bring up Has any great ideas so with that? + +Scott Hewitson: Let's go some proposals since the last call. I think the only School community pool spend was for the pretor Acquisitions just a FY FYI on that one. Pray tower all their code and everything's gonna be open source similar to how the cloud most one happened as well. If anyone has any questions on that we can dive it more into that. From the discussion side. It's quite a few I haven't seen anything really like anyone looking for funds. It's kind of just like early discussions. So I don't think we have anything we want to touch on their Thai. Let me know if there's any discussions that you think would be pertinent to talking about instigate economics. And then let's go to last months. + +Scott Hewitson: call Actually, so I was doing the notes for these we just started last month. Where I'm not gonna be doing a community members can be doing that as part of bounties may not be up yet from last call. Yeah, okay it is yeah, so we talked a little bit about provider incentives a little bit updates there, Andrew G our favorite question guys asking about the fluctuations in GPU capacity and there's a small complaint about that. I was just like some scheduled maintenance. So no issues. We talked about the traitor acquisition and a little bit about the coinbase learn and earn. I want to say up to this point. There's been about 500,000 activations meaning 500,000 people have used the Earth done the learn so it's just getting more exposure out there. + +Scott Hewitson: That was quite a large governance proposal that came up. And yeah, I mean nothing you need. Those are high level points anyone's welcome to check out the meeting notes in GitHub. We record and have transcripts of all these meetings in case you missed one. So feel free with that. I think I'm gonna pass it over to Cheng if there's any updates that you'd like to talk about and then I know I have something I wanted to bring out after. + +Cheng Wang: Yeah, for We can keep it fairly Dynamic. Thank you Huey for the great introduction as always in recap. The first thing is with what you mentioned previously and Zach feel free to timing. If you'd like for coinbase urn of the 500 or so thousand folks who have completed. I think one of the biggest Community questions has been how many new wallets or users And when we say users it's kind of a proxy for wallets, right because on chain, you can really track walls to users not necessarily it's not yet. It's fairly Anonymous there but the proxy there on coinbase at least is over. I would say approximately 98% of those 500,000 wallets that have completed the earn Quest had not held akt in their wallets before so with an indicates is that the vast majority of folks who have completed the earn Quest at least a cautious are in quest. We're not at least + +Cheng Wang: Years of akt previously and now we do have people who are at least a lot more familiar with who we are in a sensibly a little bit wiser about what Akash does who we are and our place in the decentralized marketplace as well as independ. So there's that primary thing as far as provider incentives go a quick report on that which is We did. What? Is it the first pilot for provider incentives and thus far to date we avoid approximately. Let me put a pin in there real quick for coinbase learner and we've spent approximately 1.5 million of the original allocated budget as far as dollar terms. Of course that's kind of cemented now, right because those have been spent and the remaining akt currently sitting there because of the broad Market just + +00:05:00 + +Cheng Wang: Oopsia, shall we say over the last couple days and week or so that the remaining balance is approximately between four and a half and five million dollars that remains as far as the budget goes. So thus far has been pretty good what's coming online next is going to be staking Quest as soon as that gets completed for caution thing that ETA should be relatively soon. The requisite teams are currently working on that technical integration. And so of course, we'll make an announcement when that what's taking goes live. We expect to keep the first campaign running for a little bit just to have some continuity and then we pull things down and revamp for phase two or second Campaign which will include a little bit more, deeper diving into a cost tools like a chat or scxology probably chat. So that's kind of where we are today with coimbase earn with regards to provider incentives. We've thus far your marks. Not your Market, excuse me, but committed + +Scott Hewitson: Awesome. Thank you for that update. There's definitely a lot of things going on from the provider incentives and you in I think we had said anything we do with the community pool. + +Cheng Wang: approximately 3.5 million dollars of the original pool… + +Scott Hewitson: We want as much transparency as we legally can give so I anticipate before the next call. + +Cheng Wang: thus far with a little over a million dollars remaining for phase one of the incentives… + +Scott Hewitson: We'll have some kind of dashboard or… + +Cheng Wang: where reserved the committed side of the pool and… + +Scott Hewitson: some just kind of tracker for the provider incident inside. So people can see they can look on chain stuff and… + +Cheng Wang: that's brought on I think close to a hundred forty nineties over I think 60 H 100s… + +Scott Hewitson: then see where we're at and provide all the information that we can as we should be because this is all public goods funding. + +Cheng Wang: same amount of a 100 I think some a6000s as well in addition to some requisite support around that + +Scott Hewitson: So I think at this point, is there anyone before I go into this little idea that I've had does anyone want to bring up any ideas any thoughts literally anything goes as long as it's related to economics. + +Cheng Wang: High-end storage. So those are kind of where the funds thus far have gone to and they've gone to predominantly two or two providers and were of course trying to find more to diversify the offering and… + +Scott Hewitson: I know Andrew's not here to ask his good one question,… + +Cheng Wang: those conversations are ongoing and… + +Scott Hewitson: but hi,… + +Cheng Wang: as they kind of emerge and… + +Scott Hewitson: we'll give it to you. + +Cheng Wang: as additional spend gets allocated will be reporting on that and… + +Tyler Wright: Hey, real quick. And sorry if you can't hear me that clearly… + +Cheng Wang: in the coming weeks. + +Tyler Wright: but there is a discussion on that. + +Cheng Wang: So all that stuff is coming together and obviously as the resources are committed you see the Wednesday resources as the spend is committed you'll see the gpus counts as well as the specific models that we talked about in The Proposal come online. + +Tyler Wright: I just want to shout out and I responded already Forum. It seems like a Content writer that's coming from the angle of trying to get Finance listing and all that kind of stuff. So I've tried to reach out to him privately and see if they would join this meeting or… + +Cheng Wang: back to you in The Newsroom, Erie + +Tyler Wright: join the Sig design meeting, but I just want to share that strategy that somebody put in discussions around basically, trying to get towards so I just want to put that out there and see if anybody here wants to contribute to discussion or presentation to sick design because they're more of a Content writer. + +Scott Hewitson: Yeah. + +Zach Horn: I'll take a look Ty have you spoken to them directly. Do you have any direct contact outside of the discussion or is that the first thing we've heard from them at this point? + +Tyler Wright: I found a Discord and I ping them and I have not heard back yet. But I also put that message in the public GitHub. So when I hear something I will connect you. + +Zach Horn: Sounds good. I'll take a look at the proposal in the meantime. And let's go from there. + +Scott Hewitson: Yeah, so some I'll say I saw. It two hours ago. So, I don't know if I use coin gecko usually but I'm coin market cap. I think coin gecko has a two there, on the right hand side. They're trying to do community stuff or it's like akt to the moon or this that or the other so I mean, it does seem a little bit more on the retail side, which is fine. we need to exposure retail and actual users deployers providers. So yeah, we'll see what comes of it but Thanks for thank you for calling that out time. Appreciate it. + +00:10:00 + +Scott Hewitson: All Does anyone else have anything else they'd like to Got some Joe thanks for joining Nick. I know your camera off don't feel like you need to say anything or whatever, but if you'd like to feel free, it's a very open forum. All right. It's a human. + +Scott Hewitson: Yeah, no, that's great. thank you for coming and if there's something you want to ask, feel free and Discord or here we try to make all these calls as open as possible. Make sure that everybody feels welcome and feels like their voice can be heard. So appreciate you coming in. All right, I think. + +Scott Hewitson: Yeah, so if no one has anything else they'd like to bring up. I've kind of had this idea for a little while. Now we've talked about provider incentives a two-sided Marketplace. So, we haven't support incentivizing the provider side but I also think we should look at the tenant side if you look at Uber or any other two-sided Marketplace and web they're to get drivers on board, they incentivize it but then to get your first ride get 20 bucks off. I think that's something that we should go after a little bit. + +Scott Hewitson: Especially when if we can make it easier for people to pay with akt or they don't have to get akt. So this network upgrade that I believe is tomorrow. It passed on chain is it a part of it is it fixes off Z, which is a mechanism to basically you can authorize funds from a large wallet for someone to use as deployment funds rather than sending them for funds. + +Scott Hewitson: In the past from overclock side. We've done some campaigns in the past using oxy with also done some tenant style campaigns. The reason I like autzee is because you authorize someone's wallet to deploy but they don't actually have the funds so it's not like hey, here's a hundred bucks and then they go to osmosets and dump it right away. That's always been kind of a little bit of a point that we are something that we have to be aware of so. + +Scott Hewitson: My idea for tenant incentives is once the fixed happens. Basically we say hey, all right, we want to put up, 50 hundred k, whatever the number is. I probably start small and then it would all be through autzee. We could have an easy type form where people say, here's my address. Here's what I'm deploying catch a little bit of information and then we can regularly. on Z folks to deploy I think that. Zeke what's up? + +Scott Hewitson: No, I think that could definitely be a better case. I mean I tend to like the crawl walk run models where it's like, being able to do stuff that doesn't scale is easier to the start. Yeah. I know I'll see faucet that'd be awesome. So how I Envision it is basically, once a week go into a type form from whoever owns the wallet and then just copy paste all the addresses and I'll see them, whatever the number 1,000 bucks or… + +00:15:00 + +Cheng Wang: I'll go ahead Zach. + +Scott Hewitson: … + +Zach Horn: The Hot Potato everyone wanted to jump in right away. + +Scott Hewitson: you can obviously any amount and then just weekly any new ads and… + +Scott Hewitson: the other one. So everyone gets a reality of 1000 bucks every month or whatever and the program ends when all the money is gone. So, you… + +Zach Horn: Here's my thought just based on hearing that I think it's a great idea so essentially it's a free tier like it's the way other large Cloud providers. + +Zach Horn: When you come in you set up an account you get some amount of credit to test,… + +Scott Hewitson: there's I thought about a few ways to gain this and whatnot anticipate to put a little + +Zach Horn: on another ones without naming names. I know it's like 300 dollars I think is the standard. + +Scott Hewitson: Discussion and… + +Scott Hewitson: GitHub to kind of collate all the thoughts and… + +Zach Horn: We could do something like that. + +Zach Horn: And I also agree on just moving quickly. + +Scott Hewitson: everything I'm thinking about… + +Zach Horn: So it's like what's the lightest easiest way that we can just get this up and… + +Scott Hewitson: but yeah, I definitely think we should be hitting it from both sides though. + +Zach Horn: running and test it and just see what the response is. + +Zach Horn: I think the way you described it is probably right. It's like type form, we publicize it get people want to use… + +Scott Hewitson: There's my Huey Alpha for the day Zeke. + +Scott Hewitson: Thanks for that input. + +Zach Horn: if they do they can come in and… + +Scott Hewitson: Does anyone else have anything they'd like to add or… + +Zach Horn: fill out the form we all see and then we can get a sense of… + +Scott Hewitson: any ideas or… + +Zach Horn: what people are deploying and what the usages. + +Scott Hewitson: Also open to hey,… + +Zach Horn: long term something that we might want to think about is Yes,… + +Scott Hewitson: that's a stupid idea. You should be doing it like this. go ahead and + +Zach Horn: Zeke's Comment. You're down the road. Yeah, or maybe even sooner because my thought is if it works and we like the mechanism what we could do is essentially integrated into the website. So it's one of your options to get started. So it's essentially like you land on the website. You say you want to deploy you go and you can see deployments that you can do on the network. You can set up your own deployment with your own akt, if you're ready to really jump in or you can use what would essentially be this free tier to test it out really quickly because that's one of the big pain points. I think with using a caution generals you see it. + +Cheng Wang: Was not originally envisaged with it doesn't come standard within the cosmos SDK. So there had to be, a brand new workaround that the core team specifically Archer had to work on to Really enable this particular feature because I don't think we not see was created. It had in mind right with deployments and everything like that on a caution network is more so around staking and enabling other defy things which are a lot more. Deterministic, I guess and simple it's like hey, you do this action this thing occurs and it's a lot more financially undoing the thing. So I just want to say that and Shout out engineering team. I'll put a pin in and go for Nick. + +Nick Merrill: Yeah, so I'm not to be overly self-serving but I'm a doubt-out developer. And we've had our own kind of ought Z struggles. Let's say and I think this is the kind of use case. I think that this makes a lot of sense. This is the kind of use case. I feel like it may be easier to do in contracts with cosmosem. And you I don't remember if Akash has cosmosom deployed. But if that's a route you want to go down we can definitely talk about that in a separate doubt out conversation for Implement and implementation standpoint because I find mucking around with the cosmos SDK can be often more pain than it's + +Cheng Wang: yeah, that's + +Scott Hewitson: Yeah, I know we do not have cosmosem or any smart contract functionality. So the mother folks have asked for that kind of functionality for other various things. But yeah, I know I'd be interesting to see that implementation and how difficult that would be or I know Greg in the past I think in one steering committee. He said that he doesn't want smart contracts on Akash,… + +Cheng Wang: Yes. Specifically there and… + +Scott Hewitson: but I mean, everything's evolving. + +Cheng Wang: think I agree with Greg's point is it's not that no smart contracts on a cost. But if we're going to increase the attack surface on a cost Network's code base. It's got to be very definitive when we can't just be a single use case or something like that. It's got to be something well proven and anyways, open discussion or so anybody can chime in and pitch in with ideas there and it's not to say we wouldn't integrate laws and more or other smart contracts and into cost Network code base, but it's got to be pretty Rock Solid and bulletproof use case for us to definitely consider that especially just give in the development and trajectory, right? + +00:20:00 + +Cheng Wang: Training models fine tuning Etc and just all the workloads are currently being hosting We're really moving towards right higher-end workloads more Mission critical stuff and high production value workloads, right? That's so Insurance security decreasing not expanding attack surface on necessarily all super important for the network overall. + +Nick Merrill: Yeah, that makes a lot of sense. I totally agree, from the attack surface point of view. It's one of these things where depending on what changes if any you need to make to the SDK. Sometimes we find Smart contracts are easier and cheaper to audit, + +Cheng Wang: Yeah. + +Nick Merrill: whatever changes you maybe the goed but it just depends on the use case, and also the other thing about this too is from a cost perspective, Oak doing a smart contract audit is way cheaper, often then doing a bunch of go code Audits and if you're just talking about a vanilla cosmoism, and then a permission smart contract deploy where the contracts have been audited, Cosmos is pretty battle tested at this point. There's a lot of pvl and in just vanilla cause them and endowed out contracts and whatever so it's like I hear you I do think that there's a legit security trade off there, but I can advocate for Cosmos. + +Nick Merrill: despite my own skepticism. I can advocate for Cosmos itself being fine, + +Scott Hewitson: That's great context and I know as a cosmosom came up like it's been around for what two years now year and a half. I know at the beginning people were kind of worried about it or causing laws on the Hub and all this stuff. But yeah to your point. I think it's getting to a point where it's kind of battle tested. + +Nick Merrill: Yeah, I mean I think people hear smart contracts and they think this is gonna be permissionless. Anyone can upload a smart contract scenario and… + +Scott Hewitson: Yeah. + +Nick Merrill: I think that that is often like… + +Cheng Wang: exactly + +Nick Merrill: where a lot of the hesitation comes around. people stargaze + +Cheng Wang: the same ethereum + +Scott Hewitson: For Just too much PTSD from all these rug pulls on ethereum,… + +Nick Merrill: Yeah, exactly, + +Scott Hewitson: . + +Scott Hewitson: So no, that's a great point. honestly if you have any ideas or feel free to bring it up in discussion. So Nick if you're not aware kind of we do redirect folks to or GitHub discussions, they kind of bring up ideas or ideas for gov props when they want to see funding or just ideas in general. So I would encourage you if you have any ideas like that to drop it in there. Alright Cheng beat me to it. + +Nick Merrill: Awesome on it. Thanks. + +Scott Hewitson: awesome Yeah, so anything else anyone wants to bring up? + +Cheng Wang: yeah, sorry I've not the idea but we put a pin in. So the core team has been kind of discussing what console 2.0 ultimately, cost console 2.0 would look like and of course now that when we say console 2.0 that incorporates the + +Cheng Wang: merging of cloud most back into a cost console and having the deployment natively, of course via Kepler and all that stuff is always going to be there the permissionless side. But of course, there's going to be the free tier stuff that we have to consider the stateful interface where people have to create a login and all that kind of stuff and all that is to enable ultimately at some point in time. Hopefully in the near future payment right credit card payments things like that. So the authy that's been pushed through today can help facilitate pave the way to that and make credit card payments a bit easier. So you can imagine a world where someone comes in let's say right let's say everyone here's is familiar with cryptocurrency changes. You go into an exchange you set up an account, Your account is automatically associated with potentially a bunch of different addresses of assets that the platform support right? So let's say you want to + +00:25:00 + +Cheng Wang: Create an akt deposit address and generous and KT deposit address Associated to your account ID in the cases where memos are needed. I guess Memo's kind of serve similar purpose. And once that's done you can then transact and deposit akt as you wish So you can imagine a case where you create a login if you wish to go through the kind of managed route that login then automatically spins up an akt address on the background and whenever you purchase credits, akt gets all the Z right or us economics gets all these to your account to health facilitate transactions very quickly and that + +Cheng Wang: Is one of the potential workflows that it doesn't enable and of course with the push that's being with the fix that is being pushed through and what just about a day from today will enable kind of remove the issue of when you kind of bring in deployment down for whatever reason,… + +Scott Hewitson: Yep, and just for anyone who is unaware of how opsy the fix that is happening. So basically the scenario is I ought to zaching a hundred akt he sets up a lease with you… + +Cheng Wang: right, you can't find a suitable lease the funds get returned to your account. So you don't kind of have to continue to auth Z. + +Scott Hewitson: and the hundred of that it goes into the escrow account. + +Cheng Wang: So that'll really help pave the way for one of the aspects of constant 2.0 as far as enabling beyond our credit card payments. + +Scott Hewitson: He makes a mistake or he wants to change something or change providers. So he closes at least after spending five. Akt instead of having 95 akd left over he has zero akt so that's the fix. So yeah, I'm excited for it just… + +Nick Merrill: Yeah, sure. That's + +Scott Hewitson: because we did campaigns with it a long time ago, and it was a pain But yeah,… + +Nick Merrill: Yeah, I can feel the collaborative space. Yeah, so I'm a core developer of data. + +Scott Hewitson: no, I… + +Nick Merrill: We make a dow tooling for the cosmos ecosystem. + +Scott Hewitson: A great discussion. Does anyone else want to bring up anything? + +Nick Merrill: We're built on top of cosmosem. All of our smart contracts are written in rest and… + +Scott Hewitson: And if not Nick… + +Nick Merrill: we provide interchange doubt tooling. + +Scott Hewitson: if you don't mind,… + +Nick Merrill: So we make Dows… + +Scott Hewitson: I know you said you work for or… + +Nick Merrill: where those dowels can execute arbitrary actions on any other chain that supports Cosmos,… + +Scott Hewitson: you're doing some dowdow if you wanted to don't feel like you could give everyone a 30 second to a minute on … + +Nick Merrill: that down on one chain and… + +Scott Hewitson: what you're doing. We're always open to seeing… + +Nick Merrill: it can do stuff on another chain and you can use IBC to send the assets all around and… + +Scott Hewitson: what folks are working on and it's a very,… + +Nick Merrill: it creates,… + +Scott Hewitson: … + +Nick Merrill: this cool kind of like cross chain down kind of effect. + +Scott Hewitson: collaborative space. So always interested. I know Dao so I mean,… + +Nick Merrill: You… + +Scott Hewitson: it's pretty sweet that you're here. Just out of the blue. + +Nick Merrill: we're on a bunch of chains already, we power kind of a dow ogp Juno was governance runs on us and we kind of fancy ourselves like an ex go replacement. yeah, I think that that's kind of probably the 30 second elevator pitch on doubt. + +Nick Merrill: Yes, we have that. That's the core feature. that we implemented that for a variety of other people. + +Scott Hewitson: I appreciate that and I'm thinking about smart contract and… + +Nick Merrill: We also do core vests with veto flows so you can cancel the vest at any future time through governance or… + +Scott Hewitson: thinking about doubt something that is kind of a pain is when we do have Community spend props,… + +Nick Merrill: one and we also have this notion of sub Dow so you can have … + +Scott Hewitson: right you… + +Nick Merrill: main governance that can have a committee that committee can be revoked and… + +Scott Hewitson: you put up a prop for 50,000 akt and… + +Nick Merrill: you can auth Z authorizations to that committee canvests stuff and… + +Scott Hewitson: then you get it right away. a lot of folks, depending on their jurisdictions,… + +Nick Merrill: then the parent out and… + +Scott Hewitson: they don't want to get that big chunk right away. + +Nick Merrill: cancel the vest or remove that capacity in the future,… + +Scott Hewitson: They want to invested over, you… + +Nick Merrill: whatever we do that stuff all + +Scott Hewitson: a year or something. are you aware of anyone doing any kind of vesting schedules for props? + +Scott Hewitson: If hell, yeah. + +Scott Hewitson: Awesome. I think that's I mean for me personally,… + +Nick Merrill: Have this other solution called polytone. + +Scott Hewitson: that is something that is very interesting. + +Nick Merrill: It doesn't require any Cosmos SDK upgrade or… + +Scott Hewitson: Do we need to'd imagine I don't think I see entertain accounts… + +Nick Merrill: to integrate. + +Cheng Wang: Do you have any documentation we could check on me? + +Nick Merrill: I see. yeah,… + +Cheng Wang: This is super cool, man. + +Nick Merrill: totally. Let me link to that. Just take me. + +Scott Hewitson: because we don't have packet forwarding at the moment. + +Cheng Wang: alright + +Scott Hewitson: I believe that that's something that would need to be. + +00:30:00 + +Tyler Wright: And the packet forward and stuff as well. We have that as a part of the roadmap. So if you have any thoughts there, that would be greatly appreciated. + +Nick Merrill: Yeah, that's right so you can check out I put in the chat our docs on polytone so you can have a look at… + +Scott Hewitson: yeah, if you put up something in discussions about, vesting off of community spend personally I would support that and… + +Nick Merrill: how that works. + +Nick Merrill: Yeah, it only requires IBC. + +Scott Hewitson: three seconds but + +Cheng Wang: That is pretty sick. Thank you, Nick. + +Nick Merrill: Yeah, I'll definitely put something in the chat in the sorry, Scott. + +Scott Hewitson: I think he was saying that it's not necessary. what they've built doesn't require ICA or packet forwarding to get the job done. Is that correct name? + +Scott Hewitson: Nice,… + +Nick Merrill: Absolutely, Innovations all about ecosystems for sure. + +Scott Hewitson: I will definitely be reading over that for sure. + +Nick Merrill: We'll put a prop up on the discussion super soon. + +Scott Hewitson: Okay. awesome + +Scott Hewitson: Yeah, you never know who joins the calls. Yeah, no. No, I'll just say hey this is great. You never know who joins the chat and that's lovely try to be as open and welcoming as possible because clearly what you're working on. Did you know there could be some mutual beneficial relationships going on so + +Scott Hewitson: Hell, yeah. + +Scott Hewitson: That'd be great. That would be great. + +Nick Merrill: Thanks, everyone. + +Cheng Wang: Thanks, Harry. + +Zach Horn: Thanks guys. + +Cheng Wang: Thanks ever. + +Zach Horn: Thank you. + +Cheng Wang: Thanks, Nick. + +Scott Hewitson: awesome All righty. I don't have anything else. Does anyone have any last remarks or ideas or things they'd like to talk about? + +Scott Hewitson: All with that I think I'm gonna stop the recording. Appreciate everyone coming. Thanks again, Nick for giving us all your insights from downtown looking forward to some of that stuff coming forward and we'll be in touch and Good to see everybody. Take care. + +Meeting ended after 00:32:03 👋 + From 0538cd359e6fc7a835574fe5d62074338a10fbcd Mon Sep 17 00:00:00 2001 From: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Date: Fri, 24 May 2024 11:26:21 +0000 Subject: [PATCH 10/55] Create meeting notes for sig docs #15 (#564) * Create meeting notes for sig docs #15 Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> * Update 015-2024-03-26.md add transcript for march 2024 monthly meeting Chore: add recording Signed-off-by: Drinkwater * Update 015-2024-03-26.md add recording link for meeting 15 Signed-off-by: Drinkwater --------- Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Signed-off-by: Drinkwater Co-authored-by: Drinkwater --- sig-documentation/meetings/015-2024-03-26.md | 278 +++++++++++++++++++ 1 file changed, 278 insertions(+) create mode 100644 sig-documentation/meetings/015-2024-03-26.md diff --git a/sig-documentation/meetings/015-2024-03-26.md b/sig-documentation/meetings/015-2024-03-26.md new file mode 100644 index 00000000..3c6ca95f --- /dev/null +++ b/sig-documentation/meetings/015-2024-03-26.md @@ -0,0 +1,278 @@ +# Akash Network - Docs Special Interest Group - Meeting #15 + +## Agenda +- Welcome and Introduction +- Review of Documentation Updates +- Community Contributions and Collaboration +- Addressing Documentation Issues +- Discuss the migration of documentation from old URL to Akash.network/docs. +- Future Plans and Initiatives + +## Meeting Details +- Date: Tuesday, March 26, 2024 +- Time: 7:00 AM PT (Pacific Time) +- [Recording](https://7lvvy6qbe6wq3tzg3zl2vbxvamshk5ibb3bi32m6fbt5vwdlonpa.arweave.net/-utcegEnrQ3PJt5Xqob1AyR1dQEOwo3pnihn2thrc14) +- [Transcript](#transcript) + +## Participants +- Andrey Arapov +- B S, +- Denis Lelic +- Joao Luna +- Scott Carruthers +- Piyush Choudhary +- Thomas Greco +- Tyler Wright +- Zeke E + +## Meeting Notes +### Tyler wright +- Tyler Wright welcomed attendees and outlined the meeting's focus on Akash Network documentation. +- Noted the previous hosting of documentation on docs.datacos.network. +- Highlighted the recent migration efforts led by Scott Andre and others to move documentation to Akash.network/docs. +- Mentioned the URL change and switch from /docs to /docs leading up to the last meeting. +- Acknowledged the decision to consolidate all docs onto Akash.network/docs, with Andre's assistance. +- Identified ongoing issues related to migration. +- Emphasized the need for clarity in phase one of the migration. +- Thomas is Working on CLI documentation, adding 11 labs and creating a series of videos. +- Thomas has already been involved in contributing to documentation. +- Bounty available for community members willing to review and audit documentation on Akash.network/docs. +- Task involves identifying redundant or outdated documentation, addressing spelling issues, and aligning the structure with the new format decided by the group. +- Review documentation comprehensively for redundancy and outdated content. +- Address any structural changes needed to match the new. +### Bounty Assignment Process +- Thomas has already begun reviewing and opening issues for documentation revisions. +- Acknowledges the value of a second set of eyes for confirming changes and avoiding oversight. +- Tyler will create the bounty and share it in the SIG documentation channel. +- Thomas will comment on the bounty with hours and an hourly rate to get started. +- Fixes may vary from simple spelling corrections to more complex formatting discussions. +### Piyush Choudhary's Update +- Raises an issue regarding Cloudmos documentation and the transition to Akash console. +- Shares a link for further discussion and mentions plans to create a PR. +- Tyler acknowledges ongoing discussions and invites Scott to provide input. +- Explains that the rebranding process for Cloudmos console is still in progress. +- Mentions the recommendation from Sig design to merge documentation into Akash Network/docs until the rebranding is complete. +- Thomas asks if Tyler is referring to his PR, which renamed mentions of Cloudmos to Akash console. +- Piyush confirms they are discussing a different topic, unrelated to Thomas's PR. +### Documentation Migration Status +- Scott and Andrey have identified items not yet migrated from the old documentation hosted on GitBook to Akash.network/docs. +- Recent discovery that Cloudmos documentation was missing from the new documentation +- Tyler suggests merging the staging link provided by Piyush to ensure Cloudmos documentation is live on Akash.network/docs. +- Plan to update the documentation further once the Cloudmos rebranding is complete. +### Discussion on Website Redirects +- Piyush raises concerns about the website directing users to Akash console instead of Cloudmos. +- Scott expresses confusion about the redirection and questions the status of Akash console. +- Tyler acknowledges the issue and mentions previous direction to update the deploy Now button. +- Tyler emphasizes the importance of focusing on completing the rebranding process. +- Scott explains the complexity of the situation, emphasizing the need to maintain Cloudmos deploy documentation until a clear transition to Akash console is announced. +- Highlights the need for new documentation sets for Akash console, as the existing documentation is based on the previous iteration of Akash console. +- Piyush agrees with the explanations provided and plans to make a PR to push Cloudmos content to the main site. +### Agreement on Removing Akash Console Documentation +- Tyler acknowledges Zeke's suggestion in the chat and expresses agreement. +- Scott confirms that there have been discussions about removing Akash console documentation. +- Explains that a header was added to the documentation indicating that Akash console was no longer being developed. +- Scott plans to submit a PR to completely remove Akash console documentation after Piyush's PR reintroducing Cloudmos deploy is merged. +- Thomas indicates that his questions have been answered and expresses thanks to Scott. +- All concerns and questions regarding the removal of Akash console documentation have been addressed, and the plan for action is clear. +### Thomas's Feedback on Docs Site Content +- Thomas mentions some small issues with the website content that he wanted to address. +- Specifically points out clarity needed around the placement of technical content within the "Getting Started" section. +- Highlights the section titled "Transactions" within the "Bids and Leases" subsection as being too technical compared to the rest of the beginner-friendly content. +- Tyler asks for comments on the placement of technical content within the "Getting Started" section. +- Encourages asynchronous feedback if anyone needs more time to provide input. +- Tyler appreciates Thomas bringing up the issue and encourages further discussion or feedback from the team. +### Discussion on Video Documentation +- Thomas inquires about the placement of video format documentation. +- Piyush suggests hosting videos on YouTube and embedding them within the documentation if they are highly official. Otherwise, they can be showcased on Akash education with limited minutes. +- Thomas agrees with the proposal and mentions having a dedicated Akash branch for hosting videos. +- They discuss the possibility of adding watermarks or branding to the videos, with Piyush sharing branding guidelines. +- Tyler mentions Denis from the working group volunteering to help with graphics and editing. +- Thomas appreciates the support and mentions using Scott's resources and potentially reaching out to Denis if needed. +### Issue with Documentation Discrepancies +- Scott raises concern about discrepancies in the documentation, specifically mentioning missing steps in certain sections. +- Scott provides an example where a step for changing the default persistent storage class is missing in the inventory operator section. +- Scott suggests running a new diff to identify missing documentation updates from the period preceding the migration to the new documentation site. +- Piyush agrees to conduct a thorough check to identify missing updates and push the necessary updates. +- Tyler acknowledges the issue and marks it down as an action item, thanking Scott for bringing it up. +### Discussions on Docs migration process, and audit process. + - Tyler mentioned the need for further discussions on Akash.Network/docs, migration process, and audit process before moving to other agenda items. + - Initiated phase one of the Bounty for the documentation audit. + - Tyler encouraged participation in documentation contributions, emphasizing the need for spelling changes, identifying outdated information, and making PRs. + - Thomas shared progress on videos intended for the documentation site, aiming for consistency in voice and structure. + - Scott addressed issues with dark mode rendering, resolved by fixing HTML tags in the code block. + - Scott highlighted an issue with copy-pasting from code blocks in Brave browser, noting it works in Chrome but not in Brave. + - Piyush agreed to investigate the issue with copy-pasting in Brave browser to find a solution. + +### Clarification on the use of Akash console versus Cloudmos deploy. +- Andrey raised a question about the use of Akash console versus Cloudmos deploy, regarding a pull request to the awesome Akash repository. +- Scott clarified that the old Akash console is no longer being developed, and Cloudmos deploy will eventually become the new Akash console through rebranding efforts. +- Andrey acknowledged the clarification and expressed intent to forward users to Cloudmos deploy. +### Discussion on the introductory Section of the Documentation Site. +- Scott Carruthers shared his screen to discuss an area needing urgent attention in the documentation, particularly the intro to Akash section. +- He emphasized that the issue is not technical but related to content. +- Scott suggested that the intro to Akash section could be enhanced to provide a powerful and effective introduction for new users. +- He praised existing sections such as the overview of the Akash topology and descriptions of validator and provider nodes. +- Scott expressed concern about including technical details like desex, G6, and transaction types in the intro section, suggesting they are better suited for deeper sections. +- He recommended revising the intro to focus more on providing a clear and user-friendly introduction to Akash for new users. +### Bounties for Documentation Improvement +- Tyler announced three bounties emerging from the discussion: + 1. General audit of documentation. + 2. Akash console documentation update. + 3. Rewriting the intro to Akash section. +- He encouraged participants to provide estimates for time and hourly rates for contributing to the bounties. +- Thomas expressed difficulty in estimating the time needed for the documentation audit but offered to dedicate five to ten hours per week. +- Tyler suggested monitoring progress weekly and breaking down the audit into manageable sections. +- Thomas anticipated that smaller bounties might emerge from the larger audit. +- Tyler expressed appreciation for everyone's contributions and encouraged continued involvement in improving documentation. +- The meeting concluded with thanks from Tyler, Scott, Andrey, Thomas, and Piyush. +- Meeting ended after 00:57:59. +## Action Items +- Tyler and Thomas to discuss watermark placement with Denis offline for uniformity in future videos. +- Piyush to investigate and potentially implement a solution for the copy-pasting issue in Brave browser. +- Piyush will conduct a fresh diff to identify missing documentation updates. +- Scott to submit a PR to completely remove Akash console documentation after Piyush's PR reintroducing Cloudmos deploy is merged. +- Tyler to create a bounty for documentation review and share it in the SIG documentation channel. +- Group to merge the staging link provided by Piyush to incorporate Cloudmos documentation into Akash.network/docs. + +# **Transcript** + +_This editable transcript was computer generated and might contain errors. People can also change the text after it was created._ + +Tyler Wright: Excellence this group for documentation is a monthly meeting where the group goes over any thing related to a cost documentation. This is certainly a special interest group where Community contributions are very much welcomed and very much needed. I know there's a couple of folks that have been contributing here already. A couple of high-level announcements before we get into the agenda. One if anybody is creating any issues which again documentation now lives in the website, so if anybody wants to contribute to documentation you go into the website repo. I'll share my screen. + +Tyler Wright: He was on the call human HQ have an outline clear instructions on how folks can interact with the docs and contribute beyond that when you go to the issues Any issue that's related to documentation. I see that Thomas already put a dox tag here. I'll also label anything with documentation just so we clearly know is related to the docs and the docs page as opposed to again other parts of the Akash website. For the pull requests. I'll make sure those are labeled too so we can do the same thing there. But as you can see Thomas is already done some labeling. So we'll talk about that a little bit later but much appreciated everybody that's looking to participate for following that structure. + +Tyler Wright: cool In it,… + +Thomas Greco: Yeah, no. Problem Ty happy to help set the standard. + +Tyler Wright: go ahead. + +Tyler Wright: right A couple other things to note on a high level there is a mainnet upgrade planned for next week with that. There will be some documentation that will be added to the website members of the core engineering team will continue to handle those upgrades because they'll be testing upgrades making sure that everything is working sleep seamlessly and so again can update documentation. But once that documentation is experimental. I'm sure I'll just get shared with folks for sanity check. But again, that's something that will continue to be handled by the core team. + +Tyler Wright: Cool outside of that. I know that at a last couple of meetings we've talked about. contributions from the community of just General I know peers was going to do another version of just checking to making sure that the old documentation sites that was docs at a cost.network That's all the docs and now reflected that we're on the dark side of caution Network are now reflected on network slash docs. So I know it's something that piyush has been doing. I know that there's other members of the team some folks here and some folks are not here that have been asked to help audit various pages of the website just to make sure that again the user experience is optimized as possible, especially because there's so many documents that have been migrated. So I think we'll talk about that a little bit later. + +Tyler Wright: In addition, I know that Andrey and some other folks in the community had a request to work on the search for the documentation because it was increasingly hard for folks that were searching for basic keywords to find the documentation that we're looking for. I believe there was a PR that was merged that should help to solve that problem. So, Thank you for those contributions as well. We can talk About a little bit. But again if there's anything else that anybody wants to bring up outside of those subjects. + +Tyler Wright: There's also some documentation that needs to get done for the Akash console. Once that. Brand has been transferred from cloud those two console. There will be an updates. They'll be shared. I think a couple of people have reached out about being able to help with that contribution help with that documentation. Once there's a staging site available. I'll give folks access that staging site so that they can pull more recent screenshots to update that documentation. So again, I'll follow up with folks and you think documentation Discord Channel. + +00:05:00 + +Tyler Wright: One last thing that I believe Scott brought up maybe even that last week last month, was around just a couple of hierarchy pages. I think Thomas brought up a good point that some of the content on the docs page might be a little bit too detailed for some users and can be read classified and there might be a need for some hierarchy pages that just talk at a high level about what some content is. do I know that's something that it's been worked on and talked about go ahead Thomas. I see your hand up. + +Thomas Greco: Yeah, so I piyush was nice enough to take time with me. before this meeting + +Thomas Greco: and that was one of the things that we discussed. I'm happy to kind of publish the feet the feedback he gave me the information he gave me during that conversation. But basically I wasn't sure about the best way. to go forward with getting issues such as that addressed and I think that piyush helped me with kind of figuring out a flow for that which is really opening up issues and getting those addressed accordingly whether I'm the person to work on it or whether the issue creators the person to work on or somebody else. They can kind of be decided. But yeah, I just wanted to + +Thomas Greco: mention that because I did bring it up and there hasn't really been any progression I think on that and just so for the reason. + +Tyler Wright: So just add a little bit of clarity there again, if anybody here sees any documentation issues, inside of the website repo inside of the issues area, you can create an issue we'll look to discuss those issues at these calls or in between these calls and then again anybody that wants to participate in solving that issue can leave a comment. + +Tyler Wright: There are rewards available for State documentation because our core engineering team is working on so many other things that again contributions for documentation for most everything besides again a couple things that upgrades and some other small items is certainly needed and welcome. And so again after creating an issue and we can tag a documentation, then we can talk about it or we could do an async to assign that issue to somebody with it a lot of amount of time and Once the issue is the time that person can work on interlocks continue to track it. And then what's the pr is in there? Then again piyush can work on merging and if he has any questions or if anybody needs to be involved whether it be from the core engineering team to validate any of the documentation Etc and we can do it at that time. + +Tyler Wright: Go ahead. + +Piyush Choudhary: So I would like to ask some questions to Andrey. So we escaped some issues related to updating some of the content on some of the pages of the docs. So it would be great if you can provide some information around those issues. So I had a child with Thomas Wells a shorts and invest in updating those videos special issues sleeping. And so yeah, we play some more information about what they mean when I say move and you say something like that. + +Andrey Arapov: Do you mean you need more information for the issues that I created under website Repository? + +Andrey Arapov: there are only a few send I think they're pretty much descriptive there. So there's stuff like missing your eyes in one step and then there should be some directions to mentioned in on the commentation and the other one should be just removed all the information from Predator. It's basically as what it says there and if you need any additional information, please feel free to and any questions under this issues directly in form of comments. And usually I'm trying to look at them. Sometimes just being me on track or Discord and even if you don't want to directly the questions there for whatever reason just like again me somewhere on slack or in the common chat. There is a website external in slack. So feel free to ask any additional questions because the reason why I created those because at least for my eyes they seem to be fully descriptive. + +00:10:00 + +Piyush Choudhary: So basically we have to extend the descriptions as presentation. + +Andrey Arapov: Sorry, I couldn't hear you. + +Piyush Choudhary: So I'm saying basically have to remove some of the things as for this elections and also expend the descriptions specialization to recommendations, right? + +Andrey Arapov: Sorry, I think I have either connection problem or something. I'll try to change to my headset or what my better just to ask me to the better. It will save more time. Thanks. + +Tyler Wright: Yeah. Maybe Pierce. I don't think it's you Andrey. I know piyush is getting a new mic very soon. + +Tyler Wright: if you want to drop a specific issue or specific questions inside these issues again, I think I can follow. What Andy's looking for in each of these again? I think he's structure them pretty clean. But Thomas if you are going to take on some of these issues or anybody here, if you have any specific questions on the ask just drop them specifically in this comment, that would be best so we can just track it and then once those questions are answered and we can have somebody like I'll take this because I think we want to get these kinds of things updated quickly. + +Piyush Choudhary: yep, I think it's on Scott. + +Tyler Wright: For whatever. You did pierces must clear now. + +Piyush Choudhary: Yeah, I think hiroyuki has some questions regarding how to get rewarding the dogs. So I would say I think you to see R Scott accepted into the docs. So I just said I suggested to basically bring in a program basically very reward accepted pios, whoever creates a PR and the plates update we can have some rewards for the things. So this is something I also suggested in the city dogs channel. and I think it makes sense for all the uses. + +Tyler Wright: Yeah those already and a amount of money for documentation. via the community support + +Tyler Wright: it's like a prop that went through earlier in the year. ic Heroku is someone that I have been actually talking to on that. It's looking big looking to get involved in a number of different ways. And yes for accepted PRS we will for certain items be paying out rewards and I'm going to talk to heroically about those rewards for him because we would love for them to get more involved in this. + +Tyler Wright: Special interest group I think we can have a structure maybe over time. But as we continue to get contributors involved again, please feel free to put how many hours and a rate if you want to inside the comments. Otherwise again folks know how to get in contact with me and we can work offline to figure out like a structure for now. + +Piyush Choudhary: I think it's transferred. + +Tyler Wright: Go ahead Scott. + +Scott Carruthers: yes, so some of this is interesting and I think it's just a sign that we're kind of going through a evolution of how documentation is added and edited and how were the community is involved and where the core team is involved. so where you brought up one issue that was created by Andy that had I believe a cloud most screenshot. Is that the doc audit RPC on No, that was actually created by time. Yeah, go into. I messed it. Yeah that one. I'm just using this as an example, so I guess a couple of questions and these regards as issues are. + +Scott Carruthers: created in the support repository we go through weekly. meeting for assignment of open issues. I'm wondering how that happens in the website repository now, so Andy creates this issue. and how do we have management and I guess he'd like even the expectation when Andy creates this issue is the expectation that piyush or someone from the community is going to take it or is it possible that Andy creates this issue and then he still takes it himself or one of the core team members takes that I guess this is just kind of interesting because I'm not sure that we've ever really gotten into this and I'm also kind of interested because + +00:15:00 + +Scott Carruthers: just based on history. It would be my natural inclination that if I see something in documentation the needs update in that a lot of times I would just go in and do it and now I'm wondering does that process and flow need to change? + +Scott Carruthers: on anything that comes up and we should be creating issues and I shouldn't just be going in and Updating documentation myself, but I should give the community the opportunity to do it. So long, wait a way of I guess specifically what I'm asking is how do we guarantee the issues that are created are assigned properly and should an issue be opened for any documentation update and we first give the community the opportunity to update. + +Tyler Wright: I have thoughts on all about but I'm Jaco first because his hand was up. + +Andrey Arapov: Yeah, I just want to say that for my personal point of view. Yeah, I do agree that the best one you have something to fix or just go and fix save time for you and the others but in my particular case, I was either busy with something else on the provider side or you had time for that or maybe even had mood for that. So I just found the issue and I just filed it up and for anyone to take it whoever wants to take. It's very easy to create a little PR just while the new screenshot create a PR and the issue is basically solved making. + +Tyler Wright: Excellent I love tears go first, but then I'll speak after that. + +Piyush Choudhary: So someone onto that validation is being created for the dogs updated it's a major updated writing some new documentation celebrating the power of new proper text or additions of commands and all and I think it should be done by the core team to make sure that the things that are being updated on the dogs are up to the mall as to the standards and whenever the updates about the places of things already reading some things like fixing some final things and I think it can be done by anyone. So yeah, that's not yeah and + +Piyush Choudhary: It is. + +Piyush Choudhary: Yeah, sounds good. + +Tyler Wright: Yeah, I would agree with many of those points Scott, I guess to answer your number of questions in order from a structural standpoint. And again, this is very much like an evolution process. So as I see it, if a member of the core team, he's some documentation that they have the ability to change or it's urgent enough that they think it needs to be changed. I would say that they continue to move forward changing that documentation, especially if it's a quick effort and then go through the pr process but again the pr can easily and quickly be merged. if there's an issue that is something that + +Tyler Wright: Either an entree's case. He doesn't have time for and it can be changed. It's all right for anybody to make an issue and then put it for somebody else to assign. I think it's a part of this docs. We are going to as a part of the agenda take any issues similar to how we do in six support which reaction those issues and talk about it in the open issues and see If anybody on the call wants to be assigned to them if they aren't already taken by somebody async between meetings because people again to leave comments on any of the open issues. If somebody from the core team is working then they should just assign themselves the issue and again that will just show that nobody else from the community needs to get involved. + +Tyler Wright: I don't think we have to worry about giving Community contributors the opportunity to get all issues that I think there's enough issues to go around. And I would leave it up to the Judgment for Scott's and Andre whether it be new documentation or what else do you are on the ground floor in the testing phases if you all think it's something that the community can help and you don't have the bandwidth. it's really all about helping to manage your bandwidth because as I said on many calls like a lion share + +00:20:00 + +Tyler Wright: With documentation has been Rewritten over years by Scott and with support from Andre and I know that's been very taxing on Scott amongst all the other things. So again getting other people from the community Steve documentation that our Technical and can help this isn't the wrong place. this can be improved to make it clear for users. there are rewards for those kinds of contributions and we would ask people go from through the flow of making an issue getting authorization from this sig that this is a worthy issue that needs to be changed. And then from there just either assigning that to themselves or somebody else from the community can be assign the issue and look to solve it in a timely fashion. + +Tyler Wright: We'll track any of these open issues on a meeting by meeting basis so that if an issues like sitting there long and somebody was supposed to take it then we can reassign it but God as your talking about six supports something I was thinking about earlier today, especially as we get more Community contributions is maybe change the Cadence of this meeting to happen more often the working group for the website six support happens every two weeks because there's just so much happening in those six and it may be + +Tyler Wright: Especially as we continue to grow a good thing to have Sig documentation more frequently. So that contributors can talk about the status of the things that they're working on or we could talk about any open issues. But again that we'll see how I'll keep it for one month monthly for now, but we'll see how issues evolve and over the next couple of weeks and we can work async to again continue to say that hey I got this issue. If somebody has an issue as an example if I create an issue and I want to solve it myself. I would create that issue and I would say that I think this is an issue that I would drop it and say documentation tag, everybody and we can talk async about This makes sense. This is something that you should move forward with and then we can work on the side and if we don't want to wait a month to work on some of these issues + +Scott Carruthers: All… + +Tyler Wright: notice a long-winded answer. + +Scott Carruthers: Yeah, I think that. + +Scott Carruthers: I think that all makes sense. Yeah, I would think that. I'm fine with 11 ago sometime and see how it goes. But if we're going to use this call to do triang of issues just as we do in the sport called that. + +Scott Carruthers: Being on the side. I mean we can definitely give it a month and maybe that proves not to be an issue because piyushen others are kind of on top of this and It's just not necessary to go through that life triage. But if we have a high volume of issues and we want to make sure of timeline assignment and that nothing is going. On triage, then. Yeah, I would seem like we probably have to consider going to every two weeks. + +Tyler Wright: Yeah, but again, I have no problem with because I think a lively group is being built up. I know there's a couple of people that reach out to me privately talking about getting involved in documentation outside of the folks have even on this call that I've already contributed. So I don't have a problem. But I know that many folks are quite busy so we can talk about offline and figure out the best action. Go ahead Thomas. + +Thomas Greco: yeah, I was just gonna say in the event that there is a high priority issue from somebody from overclock kind of spots and nobody can get to it. I definitely feel free to have being me about it. And if I have the ability to the type priority and I have the opportunity to get to it quickly. than that will otherwise, I'd just say now I'm unavailable. But yeah, I just wanted it seems like there's some issues that there's some instances where this might come up so. + +00:25:00 + +Scott Carruthers: Yeah, so I wasn't raised my hand because of anything that Thomas just said specifically so if anybody has a response to that what he just said makes sense to me and appreciate that. He's reading his hand to take on any virgin issues. I was going to cover a different topic as Any other thoughts on that before we move on? + +Thomas Greco: God. + +Scott Carruthers: Okay, so I was also just kind of curious as we're looking at issues Tower. Can you go back to the list of issues + +Scott Carruthers: so I just I guess want a little Clarity and this might just be like a one-off question possibly this is maybe something that we need greater understanding of but I'm a little bit confused on it seems like we intentionally labeled the GPU pricing explanation or GPU pricing explainer that we intentionally labeled that Some good just kind of curious and like I said, maybe this will be clarifying to some other future assignments as well. So that the GPU pricing page exists on they network. So why would a GPU pricing page explainer B classified as docs our way? are we thinking that while the GP pricing page exists on a cost.network there would be an explainer in the documentation site or yeah, just some further Clarity on why that's label Docs. + +Thomas Greco: So I open up that issue. I can kind of speak to it. I think that So the reason my apologies I think for maybe incorrectly tagging that. as docs I think it's just the reason why it was tagged as docs is because I am primarily working on documentation issues, so that was why I think it was maybe a mixture of that and then the mixture of just the whole. + +Thomas Greco: idea behind it. documenting. what the different chipsets are and kind of differentiating between them. but yeah, sorry for any confusion there and feel so yeah, this was something that I personally + +Thomas Greco: as someone who has a minor amount of knowledge around the different GPU chipsets I thought + +Meeting ended after 00:52:40 👋 + From be9b154d3250f4f0df55bb7dbd8bce7a36f44445 Mon Sep 17 00:00:00 2001 From: Drinkwater Date: Fri, 24 May 2024 07:36:40 -0400 Subject: [PATCH 11/55] steering committee Update README.md added video link for meeting 05/02 chore: add recording link for march 28th and notes + transcript link for meeting 05/02 Signed-off-by: Drinkwater --- committee-steering/README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/committee-steering/README.md b/committee-steering/README.md index c7eb35e3..39f1d9ce 100644 --- a/committee-steering/README.md +++ b/committee-steering/README.md @@ -27,8 +27,8 @@ The Steering Committee is a special SIG that periodically evaluates the list of | Thursday, December 07, 2023 11:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/011-2023-12-07.md) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/011-2023-12-07.md#transcript) |[Link](https://k6mud4r2ua6xarj6c5zqtkxw6fzjrvzjzu6eotsyhsmotles2gaq.arweave.net/V5lB8jqgPXBFPhdzCar28XKY1ynNPEdOWDyY6ayS0YE) | 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)|Coming Soon -| Thursday, May 02, 2024 11:00 AM PT (Pacific Time) | | | +| 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]( +| 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, 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) | | | From e71a20f982cc15b23e31348927e5cc0ccc051d18 Mon Sep 17 00:00:00 2001 From: Drinkwater Date: Fri, 24 May 2024 07:37:24 -0400 Subject: [PATCH 12/55] Update README.md add link for meeting 03/28 Signed-off-by: Drinkwater --- committee-steering/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/committee-steering/README.md b/committee-steering/README.md index 39f1d9ce..9c97b688 100644 --- a/committee-steering/README.md +++ b/committee-steering/README.md @@ -27,7 +27,7 @@ The Steering Committee is a special SIG that periodically evaluates the list of | Thursday, December 07, 2023 11:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/011-2023-12-07.md) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/011-2023-12-07.md#transcript) |[Link](https://k6mud4r2ua6xarj6c5zqtkxw6fzjrvzjzu6eotsyhsmotles2gaq.arweave.net/V5lB8jqgPXBFPhdzCar28XKY1ynNPEdOWDyY6ayS0YE) | 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]( +| 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, June 06, 2024 11:00 AM PT (Pacific Time) | | | | Thursday, June 27, 2024 11:00 AM PT (Pacific Time) | | | From 75d5e93c5298755f3479bab390e7145dccfa8bb3 Mon Sep 17 00:00:00 2001 From: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Date: Fri, 24 May 2024 11:39:39 +0000 Subject: [PATCH 13/55] Create meeting notes for sig-support #33 (#588) * Create meeting notes for sig-support #33 Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> * Update 033-2024-05-15.md add meeting recording link Signed-off-by: Drinkwater * Update 033-2024-05-15.md Signed-off-by: Drinkwater --------- Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Signed-off-by: Drinkwater Co-authored-by: Drinkwater --- sig-support/meetings/033-2024-05-15.md | 380 +++++++++++++++++++++++++ 1 file changed, 380 insertions(+) create mode 100644 sig-support/meetings/033-2024-05-15.md diff --git a/sig-support/meetings/033-2024-05-15.md b/sig-support/meetings/033-2024-05-15.md new file mode 100644 index 00000000..f68c4355 --- /dev/null +++ b/sig-support/meetings/033-2024-05-15.md @@ -0,0 +1,380 @@ +# Akash Network - Support Special Interest Group (SIG) - Meeting #33 + +## Agenda +- Participants will look at issues in [Akash Support Repo](https://github.com/akash-network/support/issues). +- Scott Carruthers will lead triaging issues, and discussion of implementation for issue fixes. +- Scott will discuss Support from the community and ask for any community feedback. +- Participants can have an open discussion of any other issues or support related items on Akash Network. +- Mainnet 11 Upgrade Follow-up + +## Meeting Details +- Date: Wednesday, March 20th, 2024 +- Time: 07:00 AM PT (Pacific Time) +- [Recording](https://qc3gxtikakjsqoqohkver467q5u675nuwy7ovtc6j4ajicy7vwna.arweave.net/gLZrzQoCkyg6DjqqSPPfh2nv9bS2PurMXk8AlAsfrZo) +- [Transcript](#transcript) + +## Participants +- Andrew Hare +- B S +- Luna +- Maxime Beauchamp +- Rodrigo Rochin +- Scott Carruthers +- Tyler Wright + +## Meeting Notes + **Introduction and Updates** + - Tyler Wright opened the meeting, highlighting the focus on engineering issues within the support repo. + - The meeting commenced with triaging issues awaiting triage. + - Max and his team maintain communication on issues and fixes via the specific repo and Discord's Cloudmos channel. + - Tyler invited input from Insiders and Vanguards on any relevant discussions or issues noticed in Discord or other channels. + - Suggestions for documentation improvements and specific issues needing escalation were encouraged. + - Tyler acknowledged the seamless Mainnet 11 upgrade and thanked all validators for their contributions. + - Mentioned backend issues related to clients and the ongoing improvement plan. + - Emphasized operations improvements for future upgrades. + - Tyler noted recent announcements regarding provider versions. + - Andrew was recognized for resolving a significant support ticket. +#### Triaging and Open Discussion: +- Scott Carruthers shared his screen to go over issues awaiting triage. +- Discussion on the focus of the current period on upgrading to the new Cosmos SDK. +- Identified key takeaways from the Mainnet 11 upgrade, noting that the Akash network is now in a different phase. +- Scott addressed various issues, including those related to Akash API changes and authorized spend grants. +- Emphasized the importance of keeping clients using the Akash API informed about changes. +- Discussed specific issues, assigning priorities (P1, P2) and responsibilities for testing and resolution. + +#### Akash API and SDK Updates: +- Luna raised concerns about visibility and communication of releases and compatibility for the Akash API and SDK. +- Suggested the creation of an announcements channel for SDK release versions to help users keep track of updates. +- Scott agreed on the importance of clear communication and regular updates, particularly for developers using the SDK. + + **Cloudmos Console Updates:** + - Max provided updates on the Cloudmos console product team. + - Max's team maintains communication on issues and fixes via the specific repo and Discord's Cloudmos channel. + +**Insights from Insiders and Vanguards:** + - Tyler invited input from Insiders and Vanguards on any relevant discussions or issues noticed in Discord or other channels. + - Discussion on recent provider upgrades and the ongoing Mainnet 11 upgrade. + - Hackathon support request for Insiders and Vanguards. + - Rodrigo mentioned increased activity from scammers on Discord. + - BS inquired about the development team on Juno, with Tyler providing information on DAO DAO's involvement and open discussions on GitHub. + + **Conclusion:** + - Tyler encouraged continued support from Insiders and Vanguards, especially during the ongoing hackathon. + - Appreciation expressed for Andrew's contributions and encouragement for staying involved in support activities. + +**Actions Items:** +- Group to follow up on new roadmap and backlog items. +- Max to continue updating and communicating Cloudmos console issues. +- Insiders and Vanguards to provide feedback on Discord observations. +- Group to implement an announcements channel for SDK release versions. +- Continue support for the ongoing hackathon, especially from Insiders and Vanguards. + +# **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 seek support to biweekly. I believe this is number 30 or 31 this support biweekly has been going on since open framework has started. This is a biweekly meeting where the core team and members of the community go over any issues and the support repo inside the accost Network organization that are waiting triage if there's anybody specifically from the community that is brought any issues forward and wants to discuss an issue. This is the biweekly meeting to join where you can meet with members of the core team discuss the issues and again, they can be prioritized and look to be solved. + +Tyler Wright: I know Scott who's been leading us through really the last couple especially in my absence will be leading us today. after we go through the issues awaiting triage usually be looked to members of the community to share any feedback that they've gotten and Discord Telegram and other channels. I know usually we have a number of insiders that join us, but there are a few conferences that insiders members of the core team Etc at so I was expecting a lighter week than usual. With that said the six support meetings transcripts notes and recordings should be up to date out of the last couple of Sig meetings. I know that again Scott lettuce through triaging any issues. He talked about the mainnet pen upgrade which happened last. + +Tyler Wright: Wednesday, March 13th. So week from today last week around this time. There was a plans Network upgrade that took less than five minutes and required again. Now, they upgrade their nodes and then providers have to upgrade their RPC notes. So again, thank you to all about data set participated and all the providers and have since upgraded their nodes and obviously thank you to members of core team here that help with documentation testing Etc. + +Tyler Wright: In addition to the main Net10 upgrade there was a parameter change that what didn't require Network upgrade but did go on chain for boat that's lowered the big deposit amounts for both the tenant side and the provider side believe it changes from five akt to 0.5. Akt. So again that went into effect. I believe March 11th or 12th and has been tested and seems to be Working properly end of the documentation has since been updated. So let's just say recap of some of the things that have been happening over the past a couple of weeks since the last six support meeting and even a little bit prior to that. But without further Ado, I'll hand it over to Scott to triage any issues of waiting triage on just be taking some notes in the background. but Scott's feel free to + +Scott Carruthers: All right. Thanks Tyler. Let me share my screen. + +Scott Carruthers: Okay, is everyone able to see my screen? + +Scott Carruthers: thumbs up it sounds good. So I will. Go into the lakash network support repo and take a look at the open issues. I looked at this a little bit before our call and it does look like there's a couple that don't have assignment or prioritization so we can go through those. first one that we come across that has been created since our last six Port is a review of our provider auditing requirements and Andy has already assigned himself to that. So I'll just progress down to the first unassigned issue. So this was open by Andy so Andy may have a comment and yell rely on you for a little bit of review, but this is + +Scott Carruthers: An issue where we are seeing some amount of memory issues. in certain queries on archival nodes. I Andy would you like to give some more thoughts on this? + +00:05:00 + +Scott Carruthers: Okay. + +Scott Carruthers: Yeah. + +Andrey Arapov: you can see there in the screenshot 140 gig of memory or 157 gig so it means you just needs more memory for its operations,… + +Scott Carruthers: Yeah, I'm just gonna Put a note in that we're leaving this open despite the fact that it… + +Andrey Arapov: but for one hand,… + +Scott Carruthers: carried by increase Ram allocation + +Andrey Arapov: I will think to maybe close it but another hand I'm thinking to leave it for Arthur to take a look and decide if that's expected because if it's not expected then it probably needs to be addressed. I mean the fact that it uses that whole amount of memory for this queries because maybe it's not supposed to use that much of memory And just maybe tie garter just to take a look and decide if he's okay to close it as it is, I would like him just like to go through just understand what happened and decides if it's something that we should really take care. I mean they closer look or not. + +Andrey Arapov: + +Scott Carruthers: Yeah, I tagged him there with that comment share. + +Andrey Arapov: maybe it's growing this time. We don't know so it's definitely not like you wanted to it's the lowest score in terms of priority,… + +Scott Carruthers: And also assign them. + +Andrey Arapov: but that's my five sense. + +Andrey Arapov: Maybe it's worth to change the title of this issue or maybe just leave it because it's not running out of memory anymore since he increased the memory, but it's rather consumes lots of memory, basically. More of a question. + +Scott Carruthers: Yeah. + +Andrey Arapov: Maybe I think it's even belongs more to but you can converse it into a discussion rather than the issue I believe. + +Andrey Arapov: I don't think that there is a possibility to convert it like, the issues into discussion, but I can do it later. + +Scott Carruthers: Okay. + +Andrey Arapov: Yeah, I think it was just a great probably discussion and based on this issues and just leave it in under discussion and close this issue. + +Scott Carruthers: you want me to quote you want me to close the issue and you can just create just Okay. + +Andrey Arapov: No, no just leave it so that I don't forget it. and then I'll create a discussion and refer to this issue because it's not an issue. + +Scott Carruthers: okay, I'll sign you on this as well just for Is a visible there? Okay. Sure. + +Andrey Arapov: Yeah things. + +Scott Carruthers: Okay, so I was actually reviewing this issue earlier today. So this was opened by a Community member. I am going to go back to people that are currently on call. I don't believe that this person is currently on the call. but I okay. + +Maxime Beauchamp: It's narrow. + +Maxime Beauchamp: the new team member + +Scott Carruthers: Okay. + +Scott Carruthers: So yeah, so I just was briefly coming through this before. Her call as you can see There's no reliable Per test and local developments and so I thought I don't know if any so max. Maybe you have some context for this but he's staying in those currently no reliable blockchain for tests and local development for instance tests local environments prior to either download and important DB or uses unreliable sandbox, so I guess there's two then I could write this in the comments and possibly get some further feedback, but the two obvious thoughts that come to mind is so we have the ability to spin up local development environments, which is well documented within our engineering documentation, and I'm also + +Scott Carruthers: Not entirely clear on the comment of unreliable sandbox. So I don't know if anyone else might have some further thoughts on the kind of the Genesis for this. + +Maxime Beauchamp: Yeah, so what he's talking about is to run Cloud those locally. and this is sort of like the indexer and we + +00:10:00 + +Maxime Beauchamp: apparently run the indexer since Genesis and there's a few reasons why we need to have the whole. Database locally as well for the API to run properly or the indexer to run property. So it's a bit tricky for new developers to start working on that locally on Carlos. So yeah, that was the issues that we had with yarrow as a new team members start working on combos. And we discussed it a few times I can see that this issue is created last week. and I think it's a bit dated as we + +Maxime Beauchamp: We were taking it new Solutions. there's another issue I think for tracking this on cloud will austerity so I'm not sure… + +Scott Carruthers: Okay. + +Maxime Beauchamp: if that issues needs to be there. + +Maxime Beauchamp: entirely + +Scott Carruthers: How about would this be a good Next Step Max? I could assign you to this issue and then you could do a review of the issues that's opened in. The cloud must repository and then determine if it's appropriate to close this issues. + +Maxime Beauchamp: Yeah. + +Scott Carruthers: Okay. + +Scott Carruthers: All Yeah Max obviously as a progresses if you need our support. On this in any way, I'm sorry. I have a better understanding of the issue and based on the indexer. It's if not necessary to work with the full may not database. So yeah, obviously as you review that other issue or if you need a support on this, just let us know. + +Scott Carruthers: so I believe that leaves us with two remaining unassigned issues. So the next one is provider should release resources immediately after. Not accepted or the deployment was closed. So I'm rather familiar with this issues. Andy you open this so you may have some thoughts as well. I'll probably assign this to Archer for initial triage and he can triage it further from there, but I know that I was looking at this I think. you and I were looking at this on the same provider and seeing that in my experience the inventory operator when a bid was closed. There was a lag possibly. And this is a very rough approximation but in my testing maybe a lag of two to five minutes between + +Scott Carruthers: when the bid is closed and when those resources are made available again via the inventory operator, so I believe that's generally the issues that were talking about any for their thoughts or clarifications any + +Andrey Arapov: yeah, sometimes it was taking even up to 35 minutes depending on which provider and which condition so it's kind of + +Andrey Arapov: It's not too deterministic to really reproduce in terms of time. But yeah, so, whenever there are all the requests in the network and providers are bidding on them. And even if they did not need lost a bit those resources on some providers in some cases not all they are getting locked up for longer than they should because normally if rather didn't beat on it or if it did but it lost that beat supposed to immediately release this resources. I'll never it's okay to log them up well with this open because it can accept it. But if it wasn't accepted and supposed to release and that can create problem and provider will be just getting running out of resources in case if somebody will be generating lots of requests every 15 minutes and sort of attack sort of + +00:15:00 + +Andrey Arapov: And yeah, I think it's important to look at this closer and I think it started happening since the upgrade to the provider From 0.0.4. So yeah, but at least it doesn't happen across all the providers and only specific cases. + +Scott Carruthers: yeah, so in my experimentation with this, so I was closely looking at the status of the bid on chain and if they was created via another provider or just the bid was closed from the loy. So the deployment was closed. I witnessed that they've close immediately on chain in the inventory operator would take about three to five minutes to recognize and release those resources. I was never able to reproduce the Scenario of the 30 to 45 minutes and I was even testing it on the provider that reported it. So we were somewhat of the belief that there was something else in play. So Andy, have you actually observed or you able to replicate a 30 to 45 minute? Failure to release the resources because I've never seen anything. That extreme I know. + +Andrey Arapov: Yeah, the day that I've tried it I reproduced it and that's what the sticker describes and can you try to scroll down? Maybe there was some update. Maybe to the bottom of it. + +Andrey Arapov: And slightly up if it speaks something about this time delays or something. + +Scott Carruthers: So this says after six minutes, it's still locked. And I did. + +Andrey Arapov: Yeah, so yeah, it was just additional test that I checked if there is something about this five, I mean the mid timeout which is the old value so it was locked for longer than six minutes and then I just didn't want to wait longer. I just realize that probably it will be there for longer time because I run several tests on this problem one of this providers and this one particularly. And yeah, I mean, of course I can run more tests to see if I can still reproduce it. But I believe it's still there and don't think it will be just gone by itself. + +Scott Carruthers: No, I don't think it would be gone by itself either and I think it's very easy to reproduce. So there's a several minute delay. So I was just curious that if we were able to reproduce that extreme delay of 30 to 45 minutes, but here you have an example of six minutes, which is obviously abnormally a long time. So, that's fine. + +Andrey Arapov: Yeah, in the beginning in the top of the ticket. I think I wrote there is Christian to 25 minutes as well. Yeah, yeah,… + +Scott Carruthers: Yeah, okay. + +Andrey Arapov: because I didn't just put the numbers randomly. So it's essentially run some tests on my own. + +Scott Carruthers: Yeah, I'm just saying that the most I could reproduce was three to five minutes but it looks like you were able to reproduce something much greater. So okay, it's fine. + +Andrey Arapov: Yeah. + +Scott Carruthers: the thoughts are comments on this issue. + +Andrey Arapov: not really but I think maybe it's related to the inventory operator the way how it pulled the data because normally what I know, it pulls every 15 minutes and there are some issues if you look at the next ticket 192 why the reports successfully High multiplic in order to operate his hair, yeah this one. so I think it's kind of connected slightly upper one into + +Andrey Arapov: and I will + +Andrey Arapov: about online to have + +Andrey Arapov: So you can open it up. + +Scott Carruthers: yeah, yes so this is actually an issues that this provider ping me yesterday as well. + +Andrey Arapov: So I think + +Scott Carruthers: So yeah, he goes through a period of time where so the provider I'm talking about is + +Scott Carruthers: deathless This is just and… + +Andrey Arapov: yeah. + +Scott Carruthers: then yeah, he's showing so I've seen this issue where we have abnormally and I know that Max has seen this issue before as well. We get abnormally large GPU alcatable. statistics I have never seen this with anything outside of gpus but yeah deathless is definitely currently experiencing this with a Ram allocatable + +00:20:00 + +Andrey Arapov: Yeah what I think is that when we upgraded the internet operator on the provider to all point, five four, I mean, so when we jumped from 0.4, I think even before in this older version of Provider, sometimes when the media device plug-in is getting stopped or restart or just being in the beginning of the insertation. It has in impacts on the amount of the GPU provider sees and when you restarted or when you wait a little bit and then it kind of picks itself, at least it was back then with 0.4 but with 0.5 when you were one + +Andrey Arapov: Because there is entirely changed the way how we winterize things from understood. I think it doesn't self recover. So it needs to be manually restarted as soon as you see this high of excessive amount of Resources and the last command one before the last one. I've just updated five hours ago. Yeah, because I was reporting on the North quite often recently. I was testing these growth AI seeing you so I had to was looking up the GPU in some conditions and I need to restart an old quite often and after it was about it up and I've noticed that issues was always coming back again. So I needed to restart the interior operator. Sometimes it was even reporting zeros. + +Andrey Arapov: So kind of interesting stuff, but they definitely needs to be getting the soft recovered from this issues. + +Scott Carruthers: I was just reading through your comments from five hours ago as well. So yeah, I've Actually reclassified this as a p zero, I think this needs some urgent attention. and it's already assigned to Archer. So + +Andrey Arapov: I think so. But another hand I was thinking when it doesn't show that amount of available resources is unusable like zero or something. So it shows that you have way too many resources one hand and why I'm saying it maybe not be zero, but maybe if you want because providers are able to offer the resources, they just able to offer to much of the resource. So then they have so well another hand. Yeah. It's probably zero. + +Scott Carruthers: yeah, so deathless actually reported yesterday that for some reason when he's getting a high memory El capable stats. so this is a strange issue. understand exactly where the correlation in this is but deathless yesterday was reporting that so he only had a certain node that was reporting incredibly High memory allocate allocatable statistics and whenever was in play and whenever that issue is current he was unable to rent out GPU or he wasn't deployers were not getting bids from his provider if + +Scott Carruthers: The sdl and so again this is kind of strange because you want to think there's any correlation here, but he was reporting and was able to reproduce it. When those memory lkdable stats are very high. If a sdl is requesting a GPU and it has a wild card for the model his provider won't bid if you specify RTX 30 90 or whatever. He has a specific model it will bid. But if he's using a wild card for the GPU, it doesn't bid during so I guess that's still debatable if it's a P0 or P1, but it definitely is having other ramifications. I think it's something that we need pretty urgent attention on. + +Andrey Arapov: The other Handler I think it should really be zero and also hurricane provider. I noticed today. also the comment to the second last one, but European provider is experiencing this issues now persistently,… + +Scott Carruthers: Yeah. + +Andrey Arapov: even if I restart the inventory operator, it's still keeps reporting with the worker now,… + +Scott Carruthers: Yes. All right. + +Andrey Arapov: so it's persistent issues. definitely + +Scott Carruthers: I would actually say this may be one of the most severe issues going on in the network right now. + +Andrey Arapov: no. + +Scott Carruthers: So yeah, we'll definitely try to get some urgent attention on up. + +Andrey Arapov: Okay. Thanks. + +Scott Carruthers: and then + +00:25:00 + +Scott Carruthers: Yeah, no, probably. Yeah,'s Zeke can death was just joined. So yeah, we were just going through the discussion of Resource the inventory operator is given abnormally allocatable amounts at where we are previously just seen on gpus but now we're starting to see it on memory as well. So the case is the issues fully up to date and I requested it from a P1 to a P0 because we understand this is probably the most urgent issue that we have on the network right now. So requested to a P0 to try to get some attention. + +Scott Carruthers: Okay, and then that leaves are very last unassigned issue. Andy do you want to so this was open some two weeks ago do you want to is this + +Scott Carruthers: so the provider stops responding to the status endpoint are you saying that they provide ourselves responding both to the rest API 8443 status endpoint and the grpc part of a44 simultaneously here + +Andrey Arapov: Yeah, it's the most important honestly and it's when the paper writer was enabled. Actually, I have not tested it back again because there are some other issues on the hurricane provider such as the abnormal reports of the resources, And whatever there no restarts. No issues. Okay. I am that's my last command that I said that I want to enable the appealing back again to see if I can still reproduce it, but I haven't got back time to do that issue because those focusing on the other issues and that other issues also. Boiled up with the abnormal report of the resources of thinking maybe that's one of the reasons for that for this issue. I will need to get back to it. + +Scott Carruthers: Okay. + +Andrey Arapov: But I think it's not. + +Andrey Arapov: Be zero of no nor P1 because I didn't have anyone reporting this issue. + +Scott Carruthers: Yeah, I have it as P2 and I'll just put in the comment that waiting for their testing by yourself. + +Zeke E: And I saw someone on Discord this morning put in. + +Andrey Arapov: Yeah. + +Zeke E: A basically saying that it happened to them. It's in the providers Channel. + +Zeke E: + +Scott Carruthers: So just for clarity what exactly did they experience? + +Zeke E: There so they said that Port 8443 isn't reachable. But April 4 is 844 is so + +Scott Carruthers: Okay. + +Andrey Arapov: That must be another thing. It must be that they need to update the engine X Ingress operator config to allow the port 844 because this one is the new part that was enabled since we upgraded the providers to version 0.5. So Yeah,… + +Zeke E: Katrina that's probably up. + +Andrey Arapov: so Zeke if you can just bring me the link to this conversation. I will reply to the person. + +Scott Carruthers: Wait, so just for clarity. I thought Zeke were reporting the opposite. So I thought you were saying that a44 they grpc. Is working… + +Zeke E: The grpc is working. Correct. + +Scott Carruthers: but a four for three is not okay. + +Andrey Arapov: There's the opposite. Okay. just let me know. + +Zeke E: Yeah, I'm sending it to. + +Andrey Arapov: Yeah, yeah. I'll take a look. + +Scott Carruthers: so that concludes our review of unassigned issues are there any For the discussions on any of the issues that we talked about or issues that we haven't talked about this morning that anyone would like to review further. + +Scott Carruthers: Okay. + +Zeke E: I might have missed this but is there a timeline for shm enablement over SEL? + +Scott Carruthers: so as you are probably aware Zeke a number of the cash core team are a kubecon today. So yesterday we got the update that Arthur has so basically Adam about an edge was the primary engineer working on this so it's code complete and we're now just waiting they release I've actually already staged to documentation update so that as soon as this is release, we'll have sdl examples and also, Guys who are providers adding necessary attributes to their provider config for shm supports or ready to go and the code is completed. We're now just waiting for the release that will unlock as shm with team members at kubecon. + +00:30:00 + +Scott Carruthers: I'm not sure when that's going to happen and what exactly we're waiting for. But yeah, that's basically the update that I have. Is this Coco complete and we're just waiting for the release to be cut that will support sham. And as I said, once that happens all the documentation and other bits are updated, so I actually was wondering if we might actually see that release this morning. That didn't happen if you want to. Maybe reach out to Arthur when he's available. Maybe you could get a ETA on when we think that release was going to become available. But that's all the information I currently have. + +Zeke E: Okay, sweetie. It's perfect. Now we can actually Deploy srock on the cost. + +Scott Carruthers: yeah, without the provider having to go in and yeah. + +Zeke E: And manually a bit. Yes. + +Scott Carruthers: Okay, so yeah great question Zeke for because there may be other people that are wondering that because there's been some chatter about this system native support and like I said is code complete so we should be releasing that good update on that and if there's not anything else that concludes our issues review, so I'll hand it back to you Tyler. + +Tyler Wright: Thank you very much, Scott Andre and others. Again, if anybody has any issues that they see over the next couple of weeks, please feel free to add comments any open issues already or if you see any new issues go through the proper mechanisms to again Ask insiders vanguards another members of the community and then if it gets escalated from there, then it'll be added to the support repo. As Max kind of covered they're also is a cloud most repo where any issues related to Cloud most live. I know the cloud most team does a great job of if anybody has any issues that they see in Discord and ecosystem Cloud most Channel or again elsewhere Cloud must team great issues for those and then continues to update those issues so you can monitor + +Tyler Wright: The Cardinals repo as well as roadmap and the support repo to see all the things that are being worked on. + +Tyler Wright: cool, At next part of the agenda. We usually see if any community members are here to give any updates on. Behaviors or themes I've seen and Discord or other channels related to support real quick. I know that the last couple of insiders meetings. There's been a real effort to improve issues around spam and Discord server. There's been a number of keywords that have been added to a list for the block lists and it seems like there's been some significant less spam. We'll continue to monitor that and talk about that during the support repo as well. As this is something that Akash insiders are actively talking about during The Insider office hours. + +Tyler Wright: But again, if anybody has any issue related to spam feel free to reach out to an Insider or myself and will continue to monitor that very closely. Is there any other issues I see Zeke here who has recently been made a Vanguard. So again, shout out to all that Zeke does Zeke have you seen anything in Discord? I know that you just shared some stuff with Andrey related to Port issues. But is anything else thematically that you've seen over the last couple of weeks and Discord that might be worth sharing with the Core team and the other members of the community. + +Zeke E: I mean right off the bat out in the auto model has been very very helpful. And catching spans. So I really like that. + +Zeke E: In terms of schemes. I think that's kind of just been the main one. I mean, yeah, nothing. I can really think about the top of my head. Other than that. + +Tyler Wright: I know that again deathless and some other members of the community have brought for some issues in provider Channel deployment channel so much appreciate content participation obviously deathless giving a number of people feedback sharing opinions thoughts and helping people with the class. So again much appreciate those efforts if anybody sees any glaring themes or issues related to whether it be use of product any of the tool documentation anything that could use update to make the user experience better for a cost users again, feel free to drop something and big support or feel free to attend another special interest group whether it be docs otherwise, + +00:35:00 + +Tyler Wright: Is there anything that anybody wants to discuss that's support or core code related that hasn't been discussed already? + +Tyler Wright: Real quick just for the consensus of this group. The Sig chain issues. It relates to the main Net 10 is still open. I know that has again passed on vote and then the upgrade is successfully happened last Wednesday. Is it fine if I close that issue? For repo just want to get thumbs down from this group. On closing the sigchainish cool. + +Tyler Wright: I will close that issue. I know there's a number of issues that will be followed upon, specifically 195 related to the memory of our archival node. I know that Max will follow up on issues number 194 and figure out where that should go and then issues 193 and 192 which are quite high priority as well as 190 will be major focuses over the next couple of weeks. So we'll look to follow up with those certainly at the next six support meeting if not sooner. + +Tyler Wright: Is there anything else that anybody wants to discuss before I'll let you all go. ahead Scott + +Scott Carruthers: It's just one thing to mention to this group to help us support the community and just make sure that everyone is aware I believe is over this past weekend. We migrated to the new documentation site. So definitely. if you see any chatter in the community, like any missing documentation or any formatting issues or anything of that nature and just so that you're aware in general if you go to akash dot Network, which is right now redirects to network with the path of Docs. So you can visit either of those paths or it's all also the documentation site that is linked off of the network home site. + +Scott Carruthers: So yeah, just make sure the entire group is aware so it should be very clean. they developers of the new documentation site did a diff on the old documentation site. and so hopefully there should be complete parody and there's not any documentation missing so this group is aware. We went through that migration and please let us know if you see any anomalies or any missing information + +Tyler Wright: Yes, great call out If you all see any missing information or anomalies or formatting issues, please drop a message and Sig docs with the specific documentation linked that would be extremely helpful and again will continue to push to have that as clean as possible. But do want to shout out the efforts of Scott and Andre who were very Hands-On and making sure that the documentation matched up as much as possible. I know that push and his team, we're very busy and we're trying their best but much appreciate Scott and Andre's oversight on making sure that documentation is clean and ready to be used by the community because I know a lot of time effort and work put into. + +Tyler Wright: Both like updating the developer documentation. Also the engineering documentation that's been added more recently. So again, thank you very much for bringing that up Scott and all the efforts here. + +Tyler Wright: if there's nothing else then again much appreciated everyone's time and efforts today during this call again. Feel free to drop any comments inside any specific issues. Please stay involved in Discord. And if you see anything worth calling out, please call it on the six support Channel Sig docs or any other respective channel that makes sense and again much appreciate everyone's time and energy today. me, + +00:40:00 + +Tyler Wright: he does not have to speak but I will call out that again the overclock Labs core team. Obviously Max and Andre is a part of that have also added another senior software engineer and Andrew who is on this call and will continue to join these calls in the future. He's working on a number of things behind the scenes and getting his feet wet. But he's a very very cease and go developer that again has gone for the rigorous process of bedding amongst the team and he's been enjoyed to work with the thus far so I'm sure many folks here and listening in we'll get to know him more as time goes on but just want to shout out does not have to say anything at this time. + +Tyler Wright: I hope everyone has a great rest of their day. Thank you very much. For participation today. There's a number of sigs again a couple of sigs got moved from this week to next week because of all the travel, but please add to your calendar Sig clients and Sig providers. I'm sure we'll do some talking about provider auditing some other stuff related to Future Discovery, and I know a couple of client related things. So again Market calendars for next week, because it'll be a basic week next week, but much appreciate everyone's time and energy today. Hope everyone has a great rest of your day. Thank you very much. + +Scott Carruthers: it's + +Andrey Arapov: Thank you. + +Meeting ended after 00:41:46 👋 + + From 7d1cbc290c234e31a4478340100a232389767d7d Mon Sep 17 00:00:00 2001 From: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Date: Fri, 24 May 2024 20:14:33 +0000 Subject: [PATCH 14/55] Create meeting notes for Sig-Design #15 (#566) * Create meeting notes for Sig-Design #15 Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> * Update 015-2024-03-13.md add transcript for meeting 2024-03-13 chore: add recording Signed-off-by: Drinkwater * Update 015-2024-03-13.md add recording link Signed-off-by: Drinkwater --------- Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Signed-off-by: Drinkwater Co-authored-by: Drinkwater --- sig-design/meetings/015-2024-03-13.md | 141 ++++++++++++++++++++++++++ 1 file changed, 141 insertions(+) create mode 100644 sig-design/meetings/015-2024-03-13.md diff --git a/sig-design/meetings/015-2024-03-13.md b/sig-design/meetings/015-2024-03-13.md new file mode 100644 index 00000000..2805e766 --- /dev/null +++ b/sig-design/meetings/015-2024-03-13.md @@ -0,0 +1,141 @@ +# Akash Network - Design Special Interest Group (SIG) - Meeting #15 + +## Agenda +- Welcome and Introduction +- Open discussion on design-related topics +- Review of Recent Events +- Discussion on Brand Assets and Guidelines +- Website Update + +## Meeting details +- Date: Wednesday, March 13, 2024 +- Time: 08:00 AM PT (Pacific Time) +- [Recording](https://nnq3ufkztaw2lqjhzhftmlaxw3rt7c3x6hotvsz7gjm2pf7jbgtq.arweave.net/a2G6FVmYLaXBJ8nLNiwXtuM_i3fx3TrLPzJZp5fpCac) +- [Transcript](#transcript) + +## Participants +- Denis Lelic +- Tyler Wright +- Zach Horn + + +## Meeting Notes +### Denis Lelic: +- Denis acknowledges the participation of Tyler and Zach and provides an overview of the meeting's purpose and frequency. +- Recent events from Q1 (EthDenver, KubeCon, GTC) were successfully conducted with swag and merchandise. More events are scheduled, necessitating an increase in design-related tasks. +- Tasks include designing stickers, t-shirts, hoodies, videos, and booth designs for upcoming events. +- Denis mentions ongoing work on the Akash.Network website, acknowledging the need for improvement and planning to review GitHub for updates. +- Denis discusses ongoing website improvements, highlighting the creation of issues on the Akash revamp repository for contributors. +- Encourages interested parties to explore easy tasks in the issue section for contribution opportunities. +- Emphasizes the continuous effort to enhance the website experience and related features. +- Mentions plans for revamping statistics display with more detailed graphs and dynamic elements. +- Announces the addition of GPU pricing, addressing a missing feature on the current website. +- Explains that GPU pricing will be included in the pricing section, allowing users to calculate. + +### Discussion on video contributions + - Tom, a community member, is willing to contribute video content. + - Emphasis on starting with a CLI video, aiming to establish a benchmark for future contributions. + - Zach highlights the iterative process for the first video, focusing on structure, recording methods, pacing, and more. + - Denis plans to assist Tom and mentions challenges with finding a suitable screen recorder for HD resolution. + - Zach recommends OBS (Open Broadcaster Software), an open-source and free screen recorder. + - Tyler emphasizes the importance of brand guidelines and assets, highlighting the availability of Dennis Zach and others for assistance. + - Tyler invited to share any additional thoughts or updates. +### Closing Remarks +- Tyler acknowledges the comprehensive coverage of topics by Denis and expresses satisfaction with the progress. +- Highlights the positive reception of Akash swag at EthDenver, with attendees expressing excitement and appreciation for the designs. +- Commends SIG Design for delivering assets and deliverables for ETHDenver and mentions readiness for upcoming events. +- Denis mentions ongoing discussions and brainstorming for future initiatives, promising to share tangible updates in the next meeting. +- Shares swag designs in the SIG Design Discord channel for community members interested in printing their own merchandise. +- Tyler notes a steady increase in people accessing the Akash swag shop, indicating a positive trend. +- Denis mentions a recent contribution from Andrea, designing a flyer for KubeCon, showcasing community initiatives in utilizing Akash branding assets. +- Denis concludes the meeting, expressing gratitude to participants and noting ongoing work in the background. + +## Action Items +- Denis to contact Tom to offer assistance with video production. +- Denis to explore OBS for screen recording. +- Continuation of ongoing efforts with video contributions and website improvements. +- Group to prrepare design materials for upcoming events. +- Denis to share tangible updates on ongoing initiatives in the next meeting. +- Adam to coordinate printing and delivery of the flyer designed by Andrea for KubeCon. +# **Transcript** + +_This editable transcript was computer generated and might contain errors. People can also change the text after it was created._ + +Tyler Wright: Of brand guidelines and brand assets. I know that Dennis Zach and others make themselves very available and a great representation of the Sig design to help. + +Tyler Wright: Make sure that all brand assets are of the highest quality. + +Denis Lelic: Hey everybody. Welcome to today's sick design meeting. Thanks Thai and Zach for participating today for joining this meeting. So for all of those who might have a look at the recording these meetings happen on a monthly basis. So I believe every first Wednesday of the month, so I'll just start off with a couple of things we've managed to do in the last couple of weeks or months, so we got first events from + +Denis Lelic: Q1 under our belts so East Denver kubecon and GTC with a lot of swag stuff a lot of merchandise Booth designs for those events and they're like a couple of them happening and actually two of them are happening next week. And there's more in the pipeline a lot of events happening this year which means we are going to have to do. A lot more everything event related from design perspective. So stickers t-shirts hoodies both videos and so on. + +Denis Lelic: Other than that, there's a bunch of + +Denis Lelic: cash dot Network our website a lot of work to do on that. part, so I'm just second just opening the GitHub. + +Denis Lelic: Okay, great. + +Denis Lelic: Ness so as we talked in the website meetings, there's a lot of stuff going on as well on the website. I've created Tyler created and Zach Tom as well created a bunch of issues here And the issue section on the website. Dash revamp Repos so anyone who's interesting contributing. Please have a look at the easy tasks here. + +Denis Lelic: and there's a lot more happening and in the pipeline, so we're constantly will try to improve the experience of the website and everything around the website, which means another thing which is in the pipeline is the stats revamped or we're planning to do a lot of more detailed + +Denis Lelic: displaying of stats like different graphs adding new stuff. Just providing a little bit of more of dynamic there. There's another new thing happening, which is the GPU pricing. Something that's been missing on the current website and it's also missing in the section. + +Denis Lelic: Under a batakash and pricing at the moment. We just have pricing coming soon for the gpus and when a user applies to calculate their pricing on a cash network based on their preferences and resources. They want to lease. They just get an estimate based on the CPU memory and storage so gpus coming soon. + +Denis Lelic: on another point we always talk about but I hope we're going to move. soon is the videos. We just talked about it briefly. We got one Community member Tom is his name. + +Denis Lelic: He's willing to do some of the video content contributions and their commutation contribution. So we just have to get started for the first one and we could take it from there. + +Denis Lelic: just hopefully iterate that version until it's something that everyone satisfied with and it's going to create some sort of a benchmark for all the future video contributions and Yeah. + +00:05:00 + +Denis Lelic: and that's + +Zach Horn: So for the video contributions, the one that Tom is working on currently I believe is going to be a CLI video that he's working on with Huey directly. I think for this first one as he said that we're going to try to just get it to a point where It's something that we can use as a reference point for all videos going forward. So, this first one's gonna be very iterative as we dial in all the different pieces. We wanted to have how it's structured how it's recorded pacing, screen recordings using 11 Labs all these different points. As soon as we get this first one done that we have a benchmark one that we can both have Tom continue to do more videos. But also if anybody else wants to participate they'll have a way to do that and I'm sure to ties point from earlier do some light weight Internal Documentation on how that's created and guides for making videos. So the goal in my mind is get a first video done. + +Zach Horn: To a point that everybody is aligned with and then we can go from there and grow our video contributions significantly because we do need videos. It's definitely a top of Mind thing. + +Denis Lelic: Yeah, I think I'll just Tom and see if I can help him in any way. I know when I tried doing some of these videos there was a challenge of finding a good screen recorder. There are great + +Denis Lelic: Apps which you have to download but of course any other product which is good you have to pay for it. but just to have HD Resolution going on and just to avoid anything pixily and stuff like that. But yeah,… + +Zach Horn: I've heard really good things about OBS open broadcaster software. + +Denis Lelic: go ahead. + +Zach Horn: It's open source. It's free to my knowledge. Lots of people use it. Yeah, it's just free and open source. That maybe what time is using already? I'm not sure but yeah, just something I've heard from lots of contributors. + +Denis Lelic: Cool, I wrote it down. I'm gonna try it. + +Denis Lelic: Okay tie you I do have maybe anything you would like to add we could keep this meeting quite short. We pretty much covered everything that's going on some stuff that's been done some stuff. That's still in the pipeline to be dealt with but you have anything on your side. Feel free. speak + +Tyler Wright: No, I think you did a great job of covering it. The only thing that I want to shout out is I know at eat Denver. there was a number of folks that were very excited about the Akash swag, the beanies, I have people still reaching out to me and Discord saying they're gonna wear it every day and people really like the number of the graphics and everything kind of turned out. so just from a events 2024 standpoint, Sig design delivered on all the assets and all the deliverables in terms of Swag for eat them for and I know that everything's on his way for the next couple of events so much appreciate the efforts of this sig there and we'll just continue to work on everything related to the website and elsewhere as well. + +Denis Lelic: Yeah, there's a lot of stuff still going on in the background background. Some of this is still kind of being discussed and brainstorm and as soon as it's Something tangible. I'll share it probably in the next meeting. + +00:10:00 + +Denis Lelic: Yeah, actually asks for some of the swag designs in the sick design Discord channel, so I just shared some of the + +Denis Lelic: We already talked about during Sikh design meetings and the last year I believe. So yeah, he's just trying to print some And produce some of that stuff on his own. But yeah, I'm happy to support anyone who has any design needs. My DMs are open. + +Tyler Wright: Yeah, there's also been a steady uptick of folks that are accessing the Akash swag shop and buying things. trending the right direction as well there. + +Denis Lelic: Yeah, that's good to know. we had a contribution last week Andrea. she is part of Luna's team the cross search. So she designed a flyer for? kubecon so that's something she coordinated with Adam and I think Adam's going to take care of that print that thing and delivered to kubecon. So yeah good to see some Community initiatives going on and people like playing around with Akash branding assets and producing stuff which is cool. + +Denis Lelic: Okay, cool, so We can make it short for today there's a lot of stuff. Of course. We are doing in the background. + +Denis Lelic: But thanks again as I can type for joining and we'll see each other soon. + +Zach Horn: Sounds good. Thanks guys. + +Denis Lelic: Have a good day, bye-bye. + +Tyler Wright: It's above. + +Zach Horn: Thank you. + +Meeting ended after 00:12:32 👋 + From 9d34bfba11bac77b7f24f6235b94a4b383708be4 Mon Sep 17 00:00:00 2001 From: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Date: Fri, 24 May 2024 20:16:05 +0000 Subject: [PATCH 15/55] Create meeting notes for Sig-Design #16 (#587) * Create meeting notes for Sig-Design #16 Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> * Update 016-2024-05-08.md add transcript Signed-off-by: Drinkwater * Update 016-2024-05-08.md add recording link Signed-off-by: Drinkwater --------- Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Signed-off-by: Drinkwater Co-authored-by: Drinkwater --- sig-design/meetings/016-2024-05-08.md | 404 ++++++++++++++++++++++++++ 1 file changed, 404 insertions(+) create mode 100644 sig-design/meetings/016-2024-05-08.md diff --git a/sig-design/meetings/016-2024-05-08.md b/sig-design/meetings/016-2024-05-08.md new file mode 100644 index 00000000..0d0cb261 --- /dev/null +++ b/sig-design/meetings/016-2024-05-08.md @@ -0,0 +1,404 @@ +# Akash Network - Design Special Interest Group (SIG) - Meeting #16 + +## Agenda +- Merchandise updates for Accelerate 2024 +- Open floor for contributions and hackathon discussion +- PR and marketing collaboration policies +- Future design and UX/UI improvements + +## Meeting details +- Date: Wednesday, May 08, 2024 +- Time: 08:00 AM PT (Pacific Time) +- [Recording](https://utgdid3tyicjsjmgvznzalfhes33oqqzoytow53oaqvlgg6nbmlq.arweave.net/pMw0D3PCBJklhq5bkCynJLe3Qhl2Jut3bgQqsxvNCxc) +- [Transcript](#transcript) + +## Participants +- Ansh Saxena +- B S +- Denis Lelic +- Fenil Modi +- Poroburu +- Tyler Wright +- Zach Horn + +## Meeting Notes +- **Merchandise Design Review** + - Denis reviewed various merchandise items for Accelerate 2024, including AirPods cases, backpacks, tote bags, notebooks, pins, wearables, socks, business cards, wristbands, gift cards, and stickers. + - Confirmed designs and production quantities. + - Discussed alternatives for an unavailable backpack model. + - Emphasized finalizing quantities and sizes for AirPods cases. + +- **Production and Logistics** + - Most items are in production or ready to be produced. + - Continued vendor communication for quality and timely delivery. + - Emphasized future merchandise reorganization and enhancement. + +- **Future UX/UI Improvements** + - Denis announced upcoming rebranding of the Cloudmos console, including a switch from Material UI to Tailwind CSS. + - Addressing friction points around payment and wallet connections to create a frictionless Web3 experience. + - Plans to integrate private repositories from GitHub and other improvements. + +- **Hackathon and New Contributions** + - Ansh Saxena discussed his project on the Cloudmos console, focusing on tokenizing AI model deployments. + - Sought assistance with running the Cloudmos console locally and expressed interest in ongoing projects. + - Denis and Tyler encouraged Ansh to connect with them and other team members on Discord for support and collaboration. + +- **Community and Support** + - Denis recommended Ansh connect with Piyush (bold Panther on Discord) for assistance with integrating private containers from Docker and other technical challenges. + - Highlighted the community's ongoing efforts to improve the Akash website and backend. + +- **PR and Marketing Collaboration Policy** + - Tyler clarified Akash's stance on PR and communications partnerships, emphasizing that Akash does not engage in empty PR announcements. + - Partnerships must involve demonstrated integration and proof of concept before any co-marketing efforts. + - Zach reiterated this policy, stating that marketing collaborations should reflect real, tested integrations that drive demand on the network. + +- **Akash Accelerate 2024** + - Denis provided details about the upcoming Akash Accelerate event, emphasizing the importance of contributions and collaboration. + - Ansh expressed interest in participating in the program post-hackathon. +**Conclusion:** +- The meeting concluded with positive feedback on the current merchandise designs. +- Encouragement for continuous collaboration and participation in upcoming meetings and events. + +**Action Items** + +- **Denis:** Confirm AirPods case quantities and sizes, find a replacement for the unavailable backpack, and ensure all merchandise items are produced on time. +- **Zach:** Continue looking for contributors and coordinate with interested parties. +- **Ansh:** Connect with Tyler and Piyush (bold Panther) on Discord for further assistance with his hackathon project and discuss the marketplace idea with Max. +- **Tyler:** Assist Ansh with any technical difficulties and ensure he is well-integrated into the community. + +# **Transcript** + +_This editable transcript was computer generated and might contain errors. People can also change the text after it was created._ + +Denis Lelic: Hey everybody and welcome to today's syndesign meeting today and not so much crowded. Me and Zach here only. So We're gonna look back on the stuff. We did in the previous month. A lot of work was done around Accelerate 2024. It's happening in Austin, Texas. So I believe it's on 28th 29th. + +Denis Lelic: So I'm just gonna get us started. With merge design, so just to have a look. What was done on that front? So we had plenty of options to choose from. + +Denis Lelic: so I'm just going to present a trimmed down version where we taught it makes sense to produce these items. So starting with airpods case something wrong community members can grab a hold of and speakers attendees and so on could have this item to pack their airpods and Then we had ideas for a backpacks. A cash branded and some other Graphics were involved. Tote bags. And there was different designs for Notebooks like a letter one. then we had + +Denis Lelic: an alternative version and we're actually producing both so the leather one and the Heart cover. + +Denis Lelic: in a bigger size and red, so I think When we asked the core team members, what are their thoughts on these which one should be produced? So we're going with number five here and number nine for red. So there are different designs here then we had pins. We're producing a three pins, I believe it's Greg's head Akash. + +Denis Lelic: Sign so a logo and just like a small Texas state. So it's like a map of Texas and we replaced the star with Akash sign here. + +Denis Lelic: So we got some. wearables merch and so on and so here's an example of vest. Then we have some Akash accelerate branded jerseys from a 14 members. and a different color and have some light packable jacket with the same theme. And a lot of different t-shirts, so I think we're producing all of them. Just not in. Crazy amount of quantity here. Just I think it's 50 each. + +Denis Lelic: So something that's gonna serve different purposes. It could be more. + +Denis Lelic: Corporate depends on the events. So yeah, just to mention some team members are gonna wear these and different events in the future and some of these t-shirts these here are only akashic ce branded, so we're gonna use them in Austin probably but of course, it's + +Denis Lelic: everyone who receives this t-shirt is going to bring it home. So it's going to be some sort of a small reminder as well on the first Akash accelerated event. We got socks. So a lot of these items here are already pushed to production. I believe the socks. I know I talked with + +Denis Lelic: Amanda who's working closely, but Adam wozny on the event side and I think this one is already out in production. Then we talked a lot about business cards. So there's + +Denis Lelic: Options here as I know we mentioned but you need the more designs maybe with a QR code involved on one side and something just the members could just hand out in different events and we can provide a crucial information how to reach someone from Akash or overclock on different platforms like X okay Twitter and so on an email. Then we have a wristband. for the Akash accelerated event We were talking about gift cards. So + +00:05:00 + +Denis Lelic: one thing I know Chang and Huey and some other folks from 14 would like to have is the gift cards where we would offer. I don't know. Let's say 10 bucks or free amount of compute resources. And that's just an idea where still have the kind of evolve and we're exploring different options how to implement this and to make it useful and Right just to make it easy for new users to access these funds and try out probably a cash Council. We have a bunch of stickers. So one of the ideas was. to produce + +Denis Lelic: lots of different designs that are kind of related to different events. So yeah, we have East Denver which is happening in Colorado. We got gosh accelerate which is happening Austin and we have some more mentioning New York here some California and others are more like just + +Denis Lelic: Akash branded like a car supercloud and so on and then we have Three set of three here, which are just carrying A conflict accelerate brand we've kind of established it it was kind of tricky. We still have to communicate a cache, but personally I had a feeling we have to have Something that's going to be memorable and it's kind of brand this event. So this forward sign and AA CC it's kind of hopefully a memorable thing for this event. And then we have this idea where the suitcase or a briefcase. + +Denis Lelic: With all these stickers applied there and we have a one cool GPU unit pack inside. Going on. We have a welcome note from Greg for Just an idea of how we could. + +Denis Lelic: Design different dashboards for this event. So that's one of them. We can have also our cards or stuff like that and napkins archive branded crash accelerate branded. + +Denis Lelic: cups so for drinks and so on with Akash accelerate branding there. + +Denis Lelic: then the next thing would be the Branded venue where the cash accelerate theme so we explored different. things here like + +Denis Lelic: branding the venue, so just putting a big sign up there. on different animations for screens so it could be a cash branded or Akash accelerated branded. back walls different banners like horizontal vertical hanging standing a cache brand of Akash accelerate branded so it's like a mix. of all of them + +Denis Lelic: which is going to go through them all. quickly Yeah, Roll-Ups as well. So that's one thing we were cooking in the last month or so. So a lot of these items are already out and production. Hopefully we'll get them all on time for the event. so that's it on the acoustic fellow rate sign. So sync design is kind of like + +00:10:00 + +Denis Lelic: also covers up one part of the marketing side. So Zach is here as well. So Zach if you want to just share anything there. + +Denis Lelic: Yeah. + +Denis Lelic: And I think for the airport's case, there's a minimum amount is hundred pieces. So it's just a matter of budgeting here yes or no, so, I know Amanda Huey and the rest of the crew are talking about this and unfortunately this backpack is not available. So I've asked Amanda to try to find something that's + +Denis Lelic: at least kind of looks the same and feels the same. So from the quality perspective. I hope it's gonna work. So yeah, otherwise like T-shirts, books this kind of stuff. I believe everything is + +Denis Lelic: as the Polly and who's like taking care of the contacting different vendors and making sure everything is + +Denis Lelic: Produced on time and so I am from my understanding everything is fine all the print files and everything is done. So the only thing was as I said we need to find a replacement for the backpack, so Maybe later today. I'm gonna try to find some. As well and just see what can we receive. In two weeks. Yeah. + +Zach Horn: Yeah makes sense. + +Zach Horn: for the airpods cases What sizes that is Because that was the one thing we're talking about is … + +Denis Lelic: I think it's the Prolia. Yeah. + +Zach Horn: what size do we do if we do airpods cases? I think that's fine. not everyone has Pros, but I think it's okay to have either way. Did we go with multiple sizes or just the pros? + +Denis Lelic: I think it's just a prose just one size,… + +Zach Horn: Okay. + +Denis Lelic: but I can check with Amanda if we could do 50 Pros 50 or the regulars. + +Zach Horn: Yeah, because I have a pair of the regular ones. It's a similar case shape, but I think it's a little bit smaller if we can and it doesn't throw any wrenches in the gears or anything like that. It might be good to do/ you were saying 50 Pros 50 regulars, but pretty small thing. I mean at this point, I think there's higher priority merch things on the table. for the soccer jerseys, which ones did we end up going with it was the stripe ones Nike strike three, I think. + +Denis Lelic: We're doing both here. Yeah. So we have the white and… + +Zach Horn: I see. hang on. + +Denis Lelic: this Coral version. + +Zach Horn: I mean the actual Jersey itself because of the link here is dry fit, but I think we ended up going with a real Jersey. I think it was the strike three. I mean Google that real quick. + +Denis Lelic: I think so. Yeah. Yeah, but from the look, it's kind of pretty much the same just probably there's a difference in materials. yeah, but just from the look, I think we're pretty much there. + +Zach Horn: Gotcha, I think we're well on track there and it sounds like we're gonna have some ongoing merch kind of reorganization and up leveling for lack of a better word. + +Denis Lelic: Yeah. + +Zach Horn: So we can carry some of this stuff through to the other merch designs that we'll have which I'm looking forward to for the official thumbs up from TY + +Denis Lelic: And I don't try looking forward to that. So. + +Denis Lelic: Yeah, that's just something we can. discuss after we've wrap up the whole accelerate stuff and see how items are being produced and so on but just important part from here is we have the designs that we can either find vendors or the just use our shop, basically, so Yeah. + +00:15:00 + +Zach Horn: Welcome if you haven't joined before. Hey. + +Ansh Saxena: Any yeah, just looking on what's Happening. + +Zach Horn: Yeah, of course happy to have you these calls sometimes they're a little more built out. We have more design things on the table, but we have a couple different initiatives going on across the board and everything's running pretty smoothly. So there's not a toned update On the marketing side one thing that I will just as a general. Announcement if you will because we're recording I'm looking for a number of contributors across the board. So these are people that can do written content that can do video. There's a potential growth role that's in the work. So this is my official statement for the record in case anyone's listening later. If you're interested, or you can do any of those things reach out to me because we're looking to bring on I'd say about five people. + +Ansh Saxena: Okay, I'm looking to there's recent hackathon around I've been working on the cloud most console and trying to make it. It's a better thing. I'm more of a deaf person,… + +Zach Horn: amazing + +Ansh Saxena: Yeah. I mean looking around what's happening in a car and what you guys been doing what is happening in design? I'm just curious about everything. Yeah, yeah and… + +Zach Horn: Yeah, of course. Are you participating in the hackathon that's going on right now? + +Ansh Saxena: participating in the heart goes on. I'm just trying to build up something users can deploy their AI models on a cash blockchain? they can also do it right now with the cloud most but more focusing on tokenizing those models that they have deployed. So that other users can have those models after the first one actually sells out to him the deployment actually transfers from one person to other person working on building something like this. + +Zach Horn: Fantastic, that's amazing. + +Ansh Saxena: If I'm able to tokenize it, I'll be able to build a Marketplace have Dows going around them and a lot more utility everything that a smartphone and providing if it's just I'm able to tokenize those deployments. I'm trying on that. + +Zach Horn: That sounds great. Definitely. Thanks for joining today. are you in the Discord by chance? + +Ansh Saxena: Yeah. Yeah, I'm on the Discord. I'm totally connected with Max for resolving of my errors matters helping me out for this thing. + +Zach Horn: very cool Thai who's on the call as well, he's our head of operations. You should connect with him as well. He's obviously big on Discord and can help you navigate the community if you need to connect with anyone else. This is a Tyler Wright on the call with us. + +Ansh Saxena: this person told me + +Ansh Saxena: Okay Okay, Tyler. I can also see you on Discord now. Yeah. + +Tyler Wright: Yeah, but as Zach meant you'll feel free to meet out to me like Tyler core team if you have any other questions or need any help with anything, but it sounds like you're already moving the right direction. So appreciate having you. + +Ansh Saxena: Yeah, I'm mostly like having troubles with having the cloud most console running on my local machine actually been working on this for the past five to six days all day. I've been working and trying out to make this thing work yet. I'm still having some issues. I have to learn a lot things databases Docker and a lot more technical things. Running on this journey is creating exciting for me to learn how Akash is actually working out and what more possibilities I can have that Akash. + +Tyler Wright: Excellent again, feel free to reach out to me if you have anything. + +Ansh Saxena: For the chance. I'm just dming you I guess your event offline on Discord wait so that we can stay connected. + +Tyler Wright: Okay. Yeah, yeah. + +Denis Lelic: So yeah, thanks for Happy to see you here happy that you're involved already in the hackathon and in the community. You're welcome. Also to join different meetings. Either client related or we have one meeting that's happening next week. It's for nakash website. + +Ansh Saxena: I mean + +Denis Lelic: So there's been a lot of work done there by different community members as well. But if you need anything design related. Feel free to reach out on this chord me and I'll help you out as much as I can but I happy to see you're already talking to Max. So that's the right guy to talk to for everything Cloud nose console related and I know Max had an idea a while ago for creating some sort of Marketplace for templates, so I think + +00:20:00 + +Ansh Saxena: This sounds great. I actually didn't discuss a lot about this Market listing. I would definitely love to discuss with them further if you already have an idea about this thing. + +Denis Lelic: Yeah a while ago. I talked to him and I think it's just an idea and nothing tangible at the… + +Ansh Saxena: Mm-hmm + +Denis Lelic: but feel free to talk to him again and just share Your idea and so on. I think he'll be happy to help you out if you need anything that and + +Ansh Saxena: I'll do it. By the way. + +Denis Lelic: cool What… + +Ansh Saxena: This is what you do. + +Denis Lelic: what do I do? + +Ansh Saxena: Yeah, yes. I'm so new. + +Denis Lelic: I do. + +Ansh Saxena: I'm like + +Denis Lelic: I do a lot of design stuff. So everything design related on their cash side, so One day's videos. The other day is something on the product side the third day something else. + +Ansh Saxena: I understand their highness and basically designing everything related to the product. + +Denis Lelic: Yeah, + +Tyler Wright: Yeah, everybody,… + +Denis Lelic: Yeah. + +Tyler Wright: branding products, marketing. + +Ansh Saxena: mmm + +Tyler Wright: Across the entire Gambit for all things. with the parking other member + +Ansh Saxena: Yeah. Yeah. I totally get this. + +Tyler Wright: But if you have any design questions, whereas you're building out like a ux and you need some design support. I need some assets, he would talk. + +Ansh Saxena: Okay, so I don't know who took anything that the moment I've been doing some assets. Yeah. + +Denis Lelic: Yeah, just let me know me on Discord and I could help you out. + +Ansh Saxena: Yeah, okay. Sure. + +Tyler Wright: climate I make a quick announcement that maybe Zach would like and back off of. + +Zach Horn: Absolutely. + +Tyler Wright: All right, there have been a couple of folks. This is more like marketing side, but there have been a couple of teams and individuals that have been reaching out as of recently looking to partner with Akash, and the way that they want to partner with the cost is by doing a Communications or a PR partnership, which means they just want to have a shout them out on Twitter or something and then do the inverse. I just want to make it clear and again Zach can feel free to get his own thoughts on this but from a high level strategy, that's not something that a cost does the community and Zach who leads many of the marketing efforts at Akash have made the concerted and I think proper strategy to not just do announcements everything that it's announces already been integrated and been tested and works and so + +Tyler Wright: if anybody is trying to reach out whether it be a discussions or just in the general Community looking for a announcement without putting any + +Tyler Wright: Integration working or without showing a proof of concept at the very least. I just want to let you know just what's on the record that probably is not something that Akash is interested in again. We love folks that are creating content that shows like development work that shows like a process and shows like something that can drive Demand on the network. But if somebody's just trying has a project and they're just trying to latch on to the coattails of Akash for quote unquote a PR announcement. That is kind of empty that's not something + +00:25:00 + +Zach Horn: Yeah, now you have to hit the nail on the head. I appreciate you putting that on the record, by the way. I'm going to clip that audio and anytime I get one of 10 million. Are you interested in a marketing collaboration thing? I'm just gonna link them your audio. but yeah, I mean that's generally the right direction and entreer context Because these calls recorded sometimes we just stuff for the record, it's very formal in that way. + +Ansh Saxena: Yeah. Yeah I get this thing. + +Zach Horn: Yeah, totally. + +Zach Horn: but yeah, that's generally the idea I mean from + +Ansh Saxena: I don't think This is a good thing. We can't actually move forward just with the ideation thing. You must be actually putting in some efforts that are visible to everyone. + +Zach Horn: So generally the way that the marketing works at a high level. For cash which obviously is this relatively unique open structure. We just want to see integration. So at the point that we're going to talk about co-marketing, we just need to see that your deploying on the network you're using, the resources in some way you're gonna build a tool and then we can get into those conversations over time. But yeah Ty said it perfectly. + +Zach Horn: That's my statement for the record. + +Denis Lelic: Right. Thanks. + +Zach Horn: Yeah. + +Denis Lelic: Okay, so that's I guess off on the marketing side. for the rest of the guys that and join in later. We talked about Akash accelerated which is happening in but three weeks so we just went through different touch points from swag and when you and everything that Needs to be designed there and a lot of these touch points already in production. So + +Denis Lelic: let me just a couple of thoughts on what's happening in the future and there's going to be Bonsall rebranding of console is happening, so + +Denis Lelic: There's gonna be some new additions to the ux UI. We are trying to solve a couple of friction points around payment and connecting wallets and so on so I'm pretty much what? All of the web 3 world is trying to solve so great and creating a frictionless web 3 experience. So + +Denis Lelic: yeah, and I think that's gonna take some time as well in the future just to + +Denis Lelic: Do our best on that front? and of course + +Ansh Saxena: Accelerating something interesting. Can you give me some more details on this? if I'm able to implement something for this hackathon? I'll definitely want to get into this program after working after the hackathon. + +Denis Lelic: yeah, the thing I think is guys from console cloudmos are trying to or they already actually did a big part of switching to a different library from material to tailwind and share cnui Library. So that's one bigger part that they're going to do and on the other and we still have to design a bunch of the stuff I've mentioned on the payment stuff and we're trying to + +Denis Lelic: also connect private repos from GitHub. And so there's going to be a lot of Explorations done in the beginning. And as soon as there's something tangible will share it. you're happy. I'll be happy if you joined one of these calls so we can discuss. What's working? What's not and so on and so on so + +Ansh Saxena: Yeah, would love to join these scores. also one more thing. Is that our guys also working on looking to integrate that private containers thing from a Docker that is like something I'm very much interested in to working on. + +Denis Lelic: Yeah, I'm not sure if Pierce. So his handle on Discord is bold Panther. He's been working on that front. So just trying to connect. Private GitHub repos to the console. + +00:30:00 + +Denis Lelic: So maybe + +Ansh Saxena: Can you write it even a chance as well? + +Denis Lelic: His handle is pulled Panther. + +Ansh Saxena: Thank you. + +Denis Lelic: Yep, so she's also a Community member often joins these calls and he did a lot of work on the Akash website. So we're basically revamped the whole website added a lot of new stuff there. We changed the back end and this was done. I believe in the beginning of the year but yeah. Also someone who I think would be happy to help you out with different related things. + +Ansh Saxena: Yeah, yeah anything with him. + +Denis Lelic: + +Zach Horn: Hey harsh question for you slightly selfishly promote from a marketing perspective and I don't mean to put you on the spot so you don't have to share if you don't want to but how'd you hear about Akash first? + +Ansh Saxena: I already knew about the guys because I've been working initially with strong as well. I've been working on their sdks and with their Integrations on a few of my hackathons very much involved into helicals last year. I went 10 of them. So I have already used this Channel and I remember initially used to leverage a car for their compute things and got to learn about Akash from there in my initial days and from then I had this clue about that the cautious something like some sort of a cheap unit that actually provides Run 10 deployments on the instance,… + +Zach Horn: Amazing. Love to hear it. + +Ansh Saxena: pay for the time that you want the resources not like this a monthly subscription thing and… + +Denis Lelic: Yeah,… + +Ansh Saxena: I love this model. + +Denis Lelic: we're kind of thought it off slow only me and… + +Ansh Saxena: I thought they can be a lot more things revolving around this particular model that you only need to pay for the time you are using the resources and… + +Denis Lelic: Zach. I'm happy this meeting is ending on a good note. So + +Ansh Saxena: not the monthly subscription or something like that. So yeah that got + +Ansh Saxena: Very much interested for parts spending in the hackathon and… + +Denis Lelic: Of course, all of you are welcome to join. all of our next meetings and… + +Ansh Saxena: building or something as well. + +Denis Lelic: if you're interesting interested in design related stuff, me on Discord or you can join the next meeting where we talk a lot of about design stuff is also the Akash website meeting which is happening next week. So I'll be happy to see you there as well. Okay, any questions anything you guys want to talk about while we're here? + +Zach Horn: Not for my side. I think we covered most of the things we had to talk about. Anything else from the design side Denis? + +Denis Lelic: No, I think we pretty much covered everything so. + +Denis Lelic: A product looked really cool. I've been okay. Which product are you referring to? Sorry. + +Zach Horn: All the products Denis they all look amazing things to you. + +Denis Lelic: Okay. + +Tyler Wright: but + +Zach Horn: every Yeah. + +Denis Lelic: Okay. + +Zach Horn: Yeah, I think the merch looks great too. I mean we've done so many iterations of merch over the years, but I really like this current set that we are working on now. I'm a soccer jerseys. + +Denis Lelic: Yeah. + +Zach Horn: I'm really looking forward to I think those are gonna be super cool. + +Denis Lelic: yeah, especially nobody's gonna play soccer and + +Zach Horn: now we have to start the costly. + +Denis Lelic: Yeah, yeah exactly web 3 League. + +Zach Horn: Yeah, that's right. + +Denis Lelic: Go. + +Denis Lelic: Yeah, so thanks For the compliment, I guess on the product side. So we'll do a complete overhaul of the Akash shop where we're gonna present new products new designs and so on and so stay cool so I think we are pretty much. Done for today also On the time side. It looks like we're approaching the end of this meeting. So thanks everyone for joining today. Feel free to DM me as I said many many times for everything design related on Discord. Otherwise, we'll see each other here next month. + +00:35:00 + +Denis Lelic: Thank you. + +Zach Horn: Sounds great. Thanks guys. Take care. + +Denis Lelic: Thank you. Have a good day. Bye. + +Ansh Saxena: And my mind is being very helpful to me as well. + +Meeting ended after 00:36:22 👋 + From 577a71a0320e1540ea2ede0995c8d8b422fd5490 Mon Sep 17 00:00:00 2001 From: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Date: Fri, 24 May 2024 20:20:50 +0000 Subject: [PATCH 16/55] Create meeting notes for sig-support #32 (#579) * Create meeting notes for sig-support #32 Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> * Update 032-2024-05-01.md add meeting transcript chore: add video recording. Signed-off-by: Drinkwater * Update 032-2024-05-01.md add video recording Signed-off-by: Drinkwater --------- Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Signed-off-by: Drinkwater Co-authored-by: Drinkwater --- sig-support/meetings/032-2024-05-01.md | 161 +++++++++++++++++++++++++ 1 file changed, 161 insertions(+) create mode 100644 sig-support/meetings/032-2024-05-01.md diff --git a/sig-support/meetings/032-2024-05-01.md b/sig-support/meetings/032-2024-05-01.md new file mode 100644 index 00000000..671e3255 --- /dev/null +++ b/sig-support/meetings/032-2024-05-01.md @@ -0,0 +1,161 @@ +# Akash Network - Support Special Interest Group (SIG) - Meeting #32 + +## Agenda +- Triaging of Support Issues +- Discussion on Support Themes +- Updates on Network Upgrade and Roadmap Progress +- Participants can have an open discussion of any other issues or support related items on Akash Network. + +## Meeting Details +- Date: Wednesday, May 1st, 2024 +- Time: 07:00 AM PT (Pacific Time) +- [Recording](https://fp4bufbowjh5thinihsyy52ddcyesjk2yofv4fgjmrhnkahxg5ua.arweave.net/K_gaFC6yT9mdDUHljHdDGLBJJVrDi14UyWRO1QD3N2g) +- [Transcript](#transcript) + +## Participants +- Andrew Hare +- Andrey Arapov +- Scott Carruthers +- SGC | DCnorse +- Tyler Wright + +## Meeting Notes +### Introduction and Updates +#### Tyler wright +- Tyler Wright's Introduction: + - Welcomes participants to the Sig Support Biweekly meeting, marking it as the 32nd one. + - Highlights the focus on issues within the support repository and the core code base. + - Acknowledges the support community's role in assisting new and existing users with the Akash Network. + +- Triaging Process: + - Tyler Wright steps in to lead the triaging process due to ongoing main net and provider upgrades. + - Indicates that all current issues have been triaged, either through internal discussions or previous meetings. + +- Updates and Roadmap: + - Mentions new items added to the board by Overclock Labs core team, outlining a roadmap for the next seven months. + - Emphasizes tracking milestones for engineering projects and potential sub-projects. + - Discusses the progression of items from backlog to live on the Akash roadmap. + +- Network Upgrade: + - Alerts participants about a planned network upgrade scheduled for the next day at 1600 UTC. + - Specifies that it involves validator and provider upgrades, with validators upgrading first, followed by providers after network stability testing. + +### Emergency Provider Upgrade +#### Tyler Wright: +- Tyler Wright addresses a pressing issue regarding the need for providers to upgrade to version 0.5.14 due to a vulnerability that was found and patched. +- Urges community members to upgrade their providers to version 0.5.14 as soon as possible. +- Mentions forthcoming instructions for providers upgrading their nodes and providers, advising participants to watch for announcements. +- Notes that the validator upgrade proposal has passed on chain, with preparations ongoing for the upgrade scheduled for the next day. + +### Open Ticket Discussion +#### Tyler Wright: +- Tyler Wright invites questions or comments regarding any open tickets or offers for participants to get involved in resolving them. +- Encourages participants to add comments to open tickets, suggesting potential solutions or questions, and prioritize tickets by labeling them accordingly (e.g., P1, P2). +### Cloudmos Issues and Updates +#### Tyler Wright: +- Highlights Cloudmos team's diligence in addressing issues in Cloudmos repositories and keeping the community informed via Discord. +- Mentions a console refactor and rebranding on Cloudmos's roadmap, assuring users that it should not impact current usage as features will remain available in the console version, an open-source deployment solution for Akash. +### General Support Discussion: +#### Tyler Wright: +- Tyler Wright transitions to the second part of the agenda, focusing on general support in Discord. +- Acknowledges the lighter attendance due to preparations for the main net upgrade. +- Invites participants to share any recent Discord discussions or issues worth discussing. +- Highlights the role of Insiders in tracking spam and scammers in Discord and mentions ongoing monitoring by the Auto mod bot. +- Encourages participants to notify him if anyone seeking validator role access is not granted and assures verification. +- Notes the plan for communication during the upgrade, with validators updating in the validator channel and providers awaiting specific announcements. +- Announces a steering committee meeting post-mainnet upgrade, welcoming community participation and input on discussion topics. +### Other matters discussed +#### Feedback on Discord Events +- Tyler Wright addresses an issue raised regarding Discord events tooling. +- Considers the possibility of removing it due to random bugs and inconsistencies. +- Requests feedback from the community on whether Discord events serve as a useful indicator or are a distraction. +- Acknowledges the ongoing effort to update events in Discord and expresses determination to improve usability. +### Closing Remarks +#### Tyler Wright: +- Assures availability of meeting notes shortly after the meeting. +- Urges inviting individuals with a background or interest in Akash Network to the sig support meeting to facilitate their involvement. +- Reminds participants to encourage providers to upgrade to version 0.5.14 if they haven't already. +- Tyler Wright thanks everyone for their time and emphasizes watching out for announcements related to the network upgrade. +- Encourages continued growth of the Akash Network and invites further questions or thoughts via sig support or Discord. +- Wishes everyone a great day and anticipates further discussions in Discord as preparations for the mainnet upgrade continue. +## Action Items: +- All providers to upgrade to version 0.5.14 to address the vulnerability. +- Validators to prepare for the scheduled upgrade tomorrow. +- Cloudmos to prepare for the console refactor and rebranding, ensuring a smooth transition without affecting current users. +- Tyler to evaluate the usefulness of Discord events and determine whether improvements or removal are warranted based on community feedback. +- Group to continue monitoring and adjusting Auto mod bot settings to support server moderation. + +# **Transcript** + +_This editable transcript was computer generated and might contain errors. People can also change the text after it was created._ + +Tyler Wright: All Welcome everybody to Sig support biweekly. The date is May 1st. I believe this is number 32 for six support during the six support biweekly. The community goes over any issues inside of the support repo again any issues related to the core code base? Go inside the support repo. There's an escalation path that go happens in Discord to determine if items are really issues. So thank you to all the Insiders vanguards and general community members that help new and existing users get acclimated with the Akash Network. + +Tyler Wright: normally a member of the core team leads us through triaging but I know again there's a lot going on with the main net upgrade with additional provider upgrades. So there's obviously members of core team here, but I will be walking us through the triaging of the issues today and then I'll just call upon anybody that again can help. + +Tyler Wright: After that, we'll go on with the typical agenda and discuss just any support or any themes that might be worth talking about during the six support. Without further Ado than I will pass it to myself to get us going with the triashing of issues. + +Tyler Wright: As you can see there are no issues that currently need triaging everything has been triage already whether it be through internal core discussions and stuff that Court members of the core team are working on or again if it was previously triage at a Miko meeting two weeks ago. + +Tyler Wright: I do want to quickly call out again. there's a number of new items that have been added to the board in the maybe last week or so. overclock Labs core team comprised at the product and Engineering teams have come together to develop a roadmap of things that the core team is going to be focused on over the next I would say seven months again. All these items have been added to the board and they're probably will be some additional atom items that will be added over time as kind of sub-project to some of these major projects. If you can go into milestones and you can kind of track some of the major milestones for engineering and some of these groups. But again, we'll continue to track these items and discuss some more in detail and discuss progress many of these items over time. We'll get moved to the + +Tyler Wright: Akash roadmap some are in backlog right now. But again as they begin to get get moved from backlog to up next and in progress and testing and then again live so just a number of items to look out for One item that I want to touch on Just for everybody here is the network upgrade the believe that the new version has been cut in is in the documentation link. I will share with folks so that they have it and I'll put it in the notes. But again, there is a planned Network upgrade happening tomorrow around 1600 UTC. + +Tyler Wright: This will be a validator upgrade as well as a provider upgrade again as we do with every upgrade the validators will upgrade first. The stability of the network will be tested after that upgrade happens and then once announced providers will upgrade their infrastructure their providers. + +00:05:00 + +Tyler Wright: One thing that has been more pressing and I think some people have seen some notes. + +Tyler Wright: Messages and Discord and elsewhere there is the need for providers to upgrade to version zero dot five dot 14 again. There's been announcements over overnight. There was a vulnerability that was found that was needed to be passed and has been patched and again just sharing that with members of the community so that they can upgrade their providers to again version. 5.14 as soon as possible or version 0.5 dot 14 rather. + +Tyler Wright: Again, there will be some more instructions that happen tomorrow for providers upgrading both their node and the provider but please look out for those announcements. But again, first matter of business will be the validator upgrade again. The proposal has passed on chain this morning. And so now preparation is continuing release has been shared in documentation and again folks validated should just be getting ready for the upgrade plan for tomorrow. Does anybody have any questions or comments about The? Emergency provider upgrade that is going on right now. + +Tyler Wright: All right continuing on again there's nothing that's currently awaiting triage. Everything has been labeled. and has been assigned. I want to see if there's anybody that has any questions about any Open tickets or if anybody wants to get involved and solving any Open tickets. + +Tyler Wright: If not now then again anybody can feel free to add a comment to an open ticket, with potential Solutions questions that they have. And you can see the prioritization of different tickets by labeling here, P1 P2 Etc. + +Tyler Wright: All right continuing to move along with the agenda after going through triassing of issues in the support repo. If cloudmo's team is usually here we will see if there's any Cloud most issues. But again, the cloud most team does a great job of looking at the cloud most repos seeing any issues there and then continuing to keep people up to date in Discord. One thing to note is again. There is a cloud most and you can see this on the road map as well. There's most a console refactor and Rebrand happening. So again Cloud most will be + +Tyler Wright: changing branding and again the visual look will continue to evolve. There'll be some more information that happens over the next couple of weeks that's pertains to the plan for that switch over. It should not affect anybody that's currently using Cloud modes because again much of the work has been refactoring to make all the features that were previously available in cloudnos available in the console version which will be again the deployment solution open source that people can work on and deploy onto a trust with + +Tyler Wright: Cool, if one has any questions about any of the issues and support repo, then we can move on to the second part of the agenda around against General support in Discord. + +Tyler Wright: All right moving along. Usually we have a number of insiders and vanguards during this call, but I know a number of folks are again getting ready for the main it upgrade and doing some other items. So it's a lighter crew today. does anybody on this call want to mention anything that they've seen recently and Discord that might be worth discussing or just again just bring to the attention of this group. + +00:10:00 + +Tyler Wright: All right, I'll take that as a no again. I know that the Insiders look to track spam and scammers in Discord and try to eliminate them words get consistently added to the Auto mod bot again help support modding the Acosta server. So again that will continue to get monitored. If anybody sees anybody in Discord that's looking for a validator role because they are validator in the active set and they don't have access to that Channel. Please feel free to reach out to me or just tag me publicly in that whether it be General chat or whatever Channel we can again verify their validators status and make sure that they have access to the validator channel. + +Tyler Wright: during the upgrade tomorrow folks will be in the valley or channel to just talk about let the community know when they've upgraded their validator. And again we do with every upgrade just stay in tune just in case there's anything that needs to be updated or fixed and members of the community always will stare share snapshots in that channel again for validators. Following that upgrade as I just mentioned at the top of the call then again, there will be a specific announcement that goes in the provider announcements channel that will indicate when providers should be upgrading their provider and their nodes. So please don't feel like you have to do anything until properly notified. + +Tyler Wright: The last thing I will say is after the main net upgrade to tomorrow. planned though. There'll be a steering committee meeting happen again. They got pushed back one week. So if anybody has any disgusting they want to bring up or any talking points, please add to those discussions get folks from the community to participate in this discussions and leave comments. And then again, we'll discuss items and more detail at the steering committee meeting tomorrow after the meeting up great. So it's very very busy period + +Tyler Wright: That's all I have. I know I've been talking a lot. Is there any questions from anybody here today about anything support comments + +Tyler Wright: If not, then again, please if anybody here sees anybody in Discord in the provider channels or some of the other channels and you that they're provider. Please make sure that they have upgraded to zero. Dot 5.14 + +Tyler Wright: Yeah, what I would say is and I'm not at a crossroads right now part of me wants to and this is a direct response to sgcd dcnorse. there seems to be major issues with the Discord events. Just tooling. It just has bugs at random times. I would say I would ask that anybody in the community and I'm determining whether or not I should just remove it all together. But again it is a good indicator for some folks. But the best source of Truth for meetings on the calendar is always the website. I'll drop the link in here again. + +Tyler Wright: I tried to update the calendar in real time and it just does what it wants. I'll change I'll change the dates. I'll add meetings and it just will disappear and there's no Rhyme or Reason. there's been multiple people that have the same issues. So I'm going to determine if the events and Discord are distraction or if it's at least like a call to action that people can then reference against the calendar, but we can talk about that. It's steering committee or Beyond but please I'd like that. yeah, I appreciate that feedback in the chat, but we will update again the steering communities happening tomorrow and we'll continue to update the events and discourse so that it's more usable or usable at all. + +00:15:00 + +Tyler Wright: If there's nothing else then if anybody has any again specific questions about any issues drop them in the support repo, I'll make the notes available shortly after this meeting among. No. I'm a little bit behind on some of the meeting notes, but I will have those before steering committee tomorrow so we can just track again a couple of the last meetings and just continue to look forward if anybody sees anybody in Discord that has go background and wants to get more involved. I urge you to invite them to this six support meeting so that again they can meet some of the core team and look to get involved a little bit more Hands-On with the product or at least again get them acclimated. There's a number of documents that have been developed by members of core team and the community that helped to help folks to understand the cash Network. So again anybody that you see that's looking to get more involved, please push. + +Tyler Wright: Direction at six support client Sig providers Etc. And if you see anybody that's a provider that has not again upgraded to 0.5.14,… + +Andrey Arapov: Think of Tyler. Thank you. Later. + +Tyler Wright: reach out to them send them The Discord announcement that Andy has put in Andres put in provide our announcements this morning and… + +Andrew Hare: I guess. + +Tyler Wright: have them continue to make sure that they're upgrading to again zero dot 5.14, please. + +Tyler Wright: All right, if there's nothing else then I know everyone's busy and we can just get back to work. But again, please look out for announcements related to the network upgrade tomorrow and then again providers upgrading when announced and we'll just continue to work on growing the across Network. Most appreciates everyone's time today. And again, please feel free to reach on six support in a specific issue or just in Discord somewhere if you have any more questions thoughts Hope everyone have a great rest of the day and we'll talk more. I'm sure and Discord and as we get ready for the main net upgrade tomorrow. + +Tyler Wright: Talk to y'all later. Bye. + +Meeting ended after 00:16:35 👋 + From e169b4b937ef7f643300a5854ffa5f080f4645cf Mon Sep 17 00:00:00 2001 From: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Date: Fri, 24 May 2024 20:35:24 +0000 Subject: [PATCH 17/55] Create meeting notes for wg-website #29 (#581) * Create meeting notes for wg-website #29 Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> * Update 029-2024-04-04.md add transcript for meeting on 04/04/2024 Signed-off-by: Drinkwater * Update 029-2024-04-04.md add recording link Signed-off-by: Drinkwater --------- Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Signed-off-by: Drinkwater Co-authored-by: Drinkwater --- wg-akash-website/meetings/029-2024-04-04.md | 302 ++++++++++++++++++++ 1 file changed, 302 insertions(+) create mode 100644 wg-akash-website/meetings/029-2024-04-04.md diff --git a/wg-akash-website/meetings/029-2024-04-04.md b/wg-akash-website/meetings/029-2024-04-04.md new file mode 100644 index 00000000..3763f27f --- /dev/null +++ b/wg-akash-website/meetings/029-2024-04-04.md @@ -0,0 +1,302 @@ +# Akash Network - Akash Website Working Group (WG) - Meeting #29 + +## Agenda +- Review of website-related issues on Akash Network repo +- Discussion on ecosystem page and token page updates +- Update on graphic for the website + +## Meeting Details +- Date: Friday, April 04, 2024 +- Time: 6:30 AM PT (Pacific Time) +- [Recording](https://yiwmcmmelchqik2ii4s7yt2wzvjy55gwxnpe2uekrwv6rv552sgq.arweave.net/wizBMYRYjwQrSEcl_E9WzVOO9Na7Xk1Qio2r6Ne91I0) +- [Transcript](#Transcript) + +## Participants + +- Denis Lelic +- Piyush Choudhary +- Thomas Greco +- Tyler Wright +- Zach Horn + +## Meeting Notes +### Introduction and Updates +- Denis Lelic opens the meeting, welcomes attendees +- Review of issues on Akash Network repo: Two new issues identified - ecosystem page and token page update +- Piyush Choudhary to address the identified issues +- Piyush presents solution sourced from Discord community for consideration +- Proposal to summarize lengthy text, suggest scrollable solution +- Denis acknowledges possible outdated content, suggests verifying missing parts +- Discussion on updating a graphic for the website, involving Scott or Cheng for updates +- Tyler Wright confirms graphic update, advises verifying community member's advice +- Denis agrees to double-check before updating the graphic + +### Updates on new website features: GPU pricing +- Piyush Choudhary introduces new GPU pricing feature on the website, accessible through menu item and announcement bar +- Denis Lelic elaborates on new section in hero section of home page, detailing options for users to get started +- Discussion on discrepancies in documentation, specifically regarding GPU pricing explanations +- Thomas Greco suggests adding a paragraph to explain GPU pricing for users unfamiliar with GPUs +- Denis acknowledges the suggestion and notes existing explanations on the website, agrees to consider adding more detailed information +- Tyler Wright proposes adding GPU pricing details to documentation for further clarity, to be discussed offline or in sync docs +- Tyler mentions pending discussions on Google Analytics and Akash Accelerate 2024 page updates, deferring further discussion for later +- Zach invited to share any additional points related to Thomas's suggestion or pending topics +### Updates on Google Analytics +- Zach Horn brings up the topic of Google Analytics implementation, notes need for GA code embed on the website +- Tyler Wright confirms the need for GA tracking on call-to-action buttons and pages, stresses high priority +- Zach clarifies the need for conversion tracking and account transfer for GA +- Piyush Choudhary confirms readiness to implement GA code once received, mentions technical issues with tag manager +- Tyler inquires about timeline for implementation, emphasizes the importance of having a timeline +- Piyush estimates 1-2 days for resolution of technical issues and implementation of GA tracking +- Zach acknowledges the timeline and expresses gratitude +### Updates on Akash Accelerate 2024 event +- Tyler Wright discusses Akash Accelerate 2024 event, highlights the need for a landing page with basic information +- Denis Lelic and Zach Horn are working on design and content for the landing page +- Tyler emphasizes the high priority of the landing page, planned for phase one early next week +- Denis suggests considering a theme or visual team for the event, to be discussed further +- Tyler suggests discussing the theme offline, possibly involving SIG design +- Tyler acknowledges Thomas for his contributions to documentation and ongoing support +- Meeting concludes with confirmation of action items and gratitude towards Thomas. +### Discussion on "how to contribute" page +- Denis Lelic brings up Thomas's offer to assist with code or PRs, suggests a brief discussion on the "How to Contribute" page +- Tyler Wright explains the need for a visual guide for new contributors and plans for further discussion over the next week +- Denis reminds the team to check a message on the Akash website external Slack channel +- Thomas Greco shares updates on upcoming PRs and videos for onboarding, mentions the delay due to focus on the agoric mainnet release +- Thomas reaffirms commitment to assisting with onboarding efforts. +### Video content creation and tools discussion +- Denis Lelic and Thomas Greco express gratitude and collaboration regarding video content creation and tutorials +- Denis discusses plans for creating a blueprint for future video contributions, considering software options for editing +- Thomas raises concerns about potential costs for gated tools like 11 Labs, suggests considering free resources +- Zach Horn offers financial support for necessary subscriptions for video creation tools +- Denis confirms no cost blockers and encourages open communication for resource needs +- Denis concludes meeting, summarizes topics covered, and invites further discussion or adjournment +- Team members express thanks and confirm conclusion of the meeting + +## Action Items +- Piyush Choudhary to address ecosystem page and token page updates. +- Denis Lelic to check with Scott or Cheng for updates on the graphic. +- Denis Lelic to double-check before updating the graphic. +- Piyush Choudhary to resolve technical issues with GA implementation within 1-2 days +- Denis Lelic and Zach Horn to work on Akash Accelerate 2024 landing page design and content. +- Tyler Wright to coordinate with Zach and Denis regarding Accelerate 2024 theme and content. +- Tyler Wright and Denis Lelic: Discuss and plan "How to Contribute" page. + +# **Transcript** + +_This editable transcript was computer generated and might contain errors. People can also change the text after it was created._ + +Denis Lelic: Hi everybody and welcome to today's working group meeting for Akash website. We meet either on a weekly basis where we discuss everything website related ui/ux adding new features changing content and so on so I'm just gonna get us going. I just had a look. at the repo and the issue sections on the website repo on Akash Network. So let me just grab the link. So you can follow along. And I see there are two new issues. They're created one is for ecosystem page and the other one is token page update. Piyush. Do you want to take us through these two issues? + +Piyush Choudhary: yeah,… + +Denis Lelic: Thanks. + +Piyush Choudhary: depending on Financial. + +Piyush Choudhary: Yeah, so as you can see this is the largest thing pushed out by the commute numbers and Discord so I just grab it from there. So you consideration right now on the system areas. We cannot wait the whole text that is thinking So the status solution which is scroll down so that we can presentation. + +Piyush Choudhary: We store Donuts Edition. So when they follow the god. For the Restriction benefit like this. + +Denis Lelic: Yeah, that seems like a reasonable solution. So I know some of this text may be outdated. I know Greg was writing a lot of this in the previous ecosystem page and I believe there's also links inside of this. So yeah, I do agree if we're missing parts of this text, actually get the whole thing. + +Denis Lelic: yeah good call out. Thank you. + +Piyush Choudhary: So if you see there is a community which is required as 25% brightness living on information. So yeah, I just + +Denis Lelic: Yeah, I'm gonna have to check with Huey or Chang to see what are the updates on this graphic? + +Piyush Choudhary: + +Tyler Wright: Denis this is a graphic that we were talking about that we saw some P back on and we were trying to remember this is the graphic that has to be updated. + +Denis Lelic: I do have all the information or should I just check with Huey and I can update it. + +Tyler Wright: I would say double check with you, but I think the advice from the Community member was correct the double check if you + +Denis Lelic: Okay, you got it. Cool. Thank you. + +Denis Lelic: So yeah. + +Piyush Choudhary: So that's all from myself. + +Denis Lelic: We have you here. Is there anything website related that you would like to speak? about + +Piyush Choudhary: So yeah, so as we can see we have a new feature live on the website GPU pricing. So I was personally public information based and as you can see this light, so everything go to the lectures. So that's the new feature that is simply onto the website. + +Piyush Choudhary: We also have the papers as you can say. + +Denis Lelic: Yeah. this page is reachable through the new menu item called GPU pricing. I believe also through the announcement bar and through this button here view GPU availability also a new section in the hero section actually on the home page where we have get started basically right away above the fold and they're like three options one is to export apply pricing the gpus or get users going either through becoming a provider or deploying their first app. yeah, so I am a piyush anything else. + +Piyush Choudhary: So there is nothing much but there was on the dates going on in dogs. So there was a mistakes or something beings which maybe numbers are falling out and all of them were big or not from ourselves. That's awesome. + +00:05:00 + +Denis Lelic: Okay, Yeah I saw your hand when up first and Tyler then you can go. + +Thomas Greco: Yeah, so I think the GPU pricing stuff looks awesome, but I did have a question. So is there anything that explains? the GPU prep I explained this in more detail. So as somebody who's not. super well-versed and gpus + +Thomas Greco: I like even just a entry level, And paragraph kind of explaining what's going on. I'm not sure if anybody else thinks that would be useful. Or if we should just kind of assume that whoever's looking at this. + +Denis Lelic: Paragraph meaning to explain the pricing or something else. + +Thomas Greco: Yeah, a pricing maybe like chips right, what types of jobs? + +Thomas Greco: A specific chips maybe better equipped to handle stuff like that. again, this is just a half suggestion, it's just something I want to call out. + +Denis Lelic: Yeah, personally. I think that. if you're looking for gpus and you don't know what age 100 or a 100 offers if you don't know if a paragraph can help you… + +Thomas Greco: Mm-hmm + +Denis Lelic: but Yeah, we do explain a little bit in this hover button about the price. So how do we get the price? So it's actually like a bidding. + +Denis Lelic: there's a disclaimer here which this offers a better explanation how the price Are sorted out here. + +Thomas Greco: Okay, I get it I think and I think it looks really really great and it is in deformative and if you have this knowledge going into it then you're good. But yeah. And you're right. I think if you're looking at it. + +Thomas Greco: then if you're in the market for gpus you're gonna know which. the capabilities different ship sets, but I just yeah. + +Denis Lelic: Yeah. Yeah,… + +Thomas Greco: I don't worth mentioning. + +Denis Lelic: cool. Thank you Ty. Go ahead. + +Tyler Wright: Yeah, I think Thomas quickly to that point maybe it's something worth adding in the documentation that we can link to the pricing page. So maybe we could talk about that offline or in sync docs, but I think that would be great. The things that I want to talk about haven't been talked about yet. So I don't want to Sidetrack the conversation. I don't know Zach if you had something you want to talk about relatively Thomas's point, but I want to talk about this Google analytics as well as the classic celebrates 2024 page but yes. + +Zach Horn: Yeah, my points on Google analytics. So let's jump right to that. + +Tyler Wright: Okay, cool. I guess I know this has been something I've been trying to work with internal team member on I think it's just like a access issue for me because I've been looking all over Zach. I know it's been helping out but I know Google analytics is something that we want to get across the website and all the call to actions as well as Pages as soon as possible and have a dashboard. So Zach. I don't know if you had an update. I know that we just talked about this yesterday so they may not be an update quite yet, but I just want to see what your thoughts were on the Google analytics the next steps as well. + +Zach Horn: Yeah, definitely. So the question right up about is I saw the note yesterday that we need the ga code embed on the page. I've access to our overclock on Akash Google analytics account so I can get that any time. What was the thing we recording with our team + +Tyler Wright: That was it the ga code. Yeah, yeah. + +Zach Horn: Got Okay, I can get that. So there's no blocker there. On the Google analytics Point more broadly… + +Tyler Wright: Okay, cool. + +Zach Horn: what we really need and what is highest priority is that we know the conversion rate through each of these rents now buttons so that can't stress it enough. It's super high priority. We need that conversion implemented in GA ASAP so that we can start tracking it page total page volume and it's great but we really need to know of the people that are landing on this page how many are converting through each of these buttons and be able to measure them against themselves? Each other I should say that's highest priority because we want to see other people that are landing here which chips are they converting on and one of the interested in so we can start to gauge demand. So two things one for next steps. What is the status on putting that conversion in place? And then what is the status of transferring that the entire account? + +00:10:00 + +Piyush Choudhary: Can you repeat the last point when you say entire town? what do you mean by an entire problem? + +Zach Horn: As I understand that the Google analytics are under your account currently, that's where we're tracking them. We need those to live. + +Piyush Choudhary: Yeah. Yeah,… + +Zach Horn: Yeah. Got it. + +Piyush Choudhary: so I just need to determine shows quotes that I mean those will be able to still. + +Zach Horn: Piyush your audios not great miss most of that. One more time, please. + +Piyush Choudhary: So yeah, I'm saying once we got the Gtech box as I said in the group, so we'll be able to implemented and all the lighting side is deciding in order Sports will be migrated with that for overlock Lots. + +Zach Horn: Got it. + +Tyler Wright: If we get those GA pose to you today? How long will it take for you to Those buttons are Implement like tracking for the red buttons and… + +Piyush Choudhary: + +Tyler Wright: then make it available to Zach and others. + +Piyush Choudhary: yeah, I was experimenting with the tag managers course to implemented on that are not working. But there are some issues that we think in terms of escrow and the specific cities cycling building algorithm and writers and just resolving those ones those issues are being resolved. I'll be able to presentation person. + +Tyler Wright: All right, when you say no you have issues, that's something that you're blocked by anybody on the core team or… + +Piyush Choudhary: So there's probably some technical issues in the Astro and… + +Tyler Wright: is this something that you're with? + +Piyush Choudhary: the specifics you get wrappings. So. I'm just resolving the issues when I Implement it's a little bit technology. + +Piyush Choudhary: Generally should connect to the United States transport, but it is not connecting producing issues. probably that's something look and this resolving those issues. Once those are it's all a legendary which + +Zach Horn: Okay, I think I understand that. You know what you're saying from a technical standpoint. We do need a timeline on it though. So what do you think in terms of timing? + +Piyush Choudhary: Second us think of wonderful days the patient steps in charge today, then tomorrow I'll be able to Otherwise on teleported for the US medicine. from now + +Zach Horn: Okay, so we're one to two days. So, call it Friday Saturday. Okay, sounds good. + +Piyush Choudhary: Yeah. + +Zach Horn: Thank you. + +Denis Lelic: Okay, cool I know you mentioned briefly the Accelerate 2024. + +Tyler Wright: Yeah with Akash accelerate proposal passing on chain and the production of the actual event is underway to think that was being secured. The date has been set the idea is that we want to have a landing page that we could start getting to people. So people know they're going to consensus or if they just love to pass and want to come to the event. They're more than welcome. So again, toothpages would be like a landing page and some basic information that we look to get up at some point early next week. I know that Denis and Zach are working on the lemonade designs and that's more information becomes available. Yes speakers schedule all that kind of stuff and we would just continue to fill out that page that's closer. But again, the event is scheduled for May 28th. So we want to start making it available for people to + +Tyler Wright: good to be a big link. Yeah Luma and then just again that's a basic information or website. So this is I think secondary to the Google analytics Zach here correctly from wrong, but this is also a high priority item when we're looking to get out and a phase one. early next week + +00:15:00 + +Denis Lelic: Yeah, like anything you want to add to that? + +Zach Horn: No, totally agree, though. + +Denis Lelic: Okay, Yeah, and Tom, I piyush I already saw you you saw the message here from Thomas. He's kind of offer his help with anything code or PR related. Just let Cool I don't know if we should talk about. how to contribute page we talked about it yesterday for a couple of minutes or do you think we could just push it to the next meeting? + +Tyler Wright: I think I can talk about what so I know that one thing that we get a lot of people in the community, is hey, I just found out about Akash, how can I contribute there's a number of ways whether it be doing a secret working group whether it be joint being an Insider a down key, this is a plethora of So I was talking to Dennis and Zach about basically making a visual page. It has some graphics and we can also turn into a handout that we can share with people in this board and elsewhere to make it easier for people to get on board and contribute. I just like being kind of be like a visual YouTuber experience map so we can talk more about that over the next week or so, I think and then see where we are going to the next meeting but certainly their priorities over the next couple of days and next week is around the Akashi accelerate 204 pages. + +Tyler Wright: Go ahead another stuff. + +Denis Lelic: cool + +Denis Lelic: Yeah, just one more thing about Accelerate 2024. I was thinking if we're gonna have some sort of a theme a visual team around the event or maybe it's even content related. On Zach, I'm not sure if you're really That deep into that issue, but that just something that pop into my mind. is it like a theme related? I don't know. + +Denis Lelic: Maybe something around AI gpus. + +Tyler Wright: Or something about Cowboys they get together so we can figure that out. + +Denis Lelic: He yeah. + +Tyler Wright: It's offline. Maybe that's a cig design type of problems. One thing I also want to call out quick is and this is kind of sick documentation related, but I do want to shout out Thomas for all the help that he's with the first video which will be added to documentation as well as he's looking to provide a great deal of support and looking at the documentation auditing specific sections appears. Just look out for some + +Denis Lelic: Thanks Peers, just one quick thing. There was a message it was on slack on the channel like Akash website external. So if you could please have a look at that Tom I saw your hand went up. + +Thomas Greco: Yeah, no, I was just gonna say I like no problem y everybody. And definitely be on the lookout for PR's videos in the coming days and I haven't had time this week to we're kind of getting the details all figured out but ask for why there's been nothing open yet. It's just been because we were getting it figured out and then I'll show with getting this kind of a goric mainnet to release. out the door that took up a lot of brain power, but I'm excited to start firing and all cylinders. Making this thing is a helping people on board, right? + +Thomas Greco: As best as we can. + +00:20:00 + +Denis Lelic: Yep. Thank you, Thomas. + +Thomas Greco: And Shadow 11 labs. the real MVP too + +Denis Lelic: Yeah, Me and Thomas were just like dming and the last couple of days or weeks about video content and tutorials and so on. So we're just trying to figure out a way. that's gonna be + +Denis Lelic: some sort of a blueprint for all the future contributions from community members, and I would just like + +Denis Lelic: explaining how to put a video together and have some sort of brand consistency throughout the videos. And one of them is 11 Labs, but their AI voice over then I provided some graphics that are available also in figma community and we were just discussing what kind of software to use to edit the videos one of the options would be canva because it's free for personal use so just basic editing adding a graphic in the front of the video and Probably get to go and the other option would be da Vinci which is kind of a bit more advanced to. But they're offering also. free package for personal usage + +Thomas Greco: so we could talk. I just add to that Denis and you've been a joy to work too. thank you for all the support. You've given me. We could take this async, but I'm also realizing 11 labs. For example, that is a tool that is potentially going to be gated, if we're kind of looking for free resources. and yeah, I'm not sure how far you can get with 11 labs? For free, so just another thing to keep in mind. + +Denis Lelic: Yeah, I think that the Viking remember correctly. They are offering free tokens every month. So the way I dealt with it, I know it's not perfect. But I just signed up through two different emails and I managed to do whatever I had to do in that time period but we should think about + +Denis Lelic: either subscription or I don't know. We'll see when we get there. So yeah that go ahead. + +Zach Horn: There's absolutely no Blocker on cost for this. If you guys need a subscription, we will get it done. Just let me know how much you need. + +Denis Lelic: Thanks Zach. + +Denis Lelic: Okay, so we covered a couple of different things + +Denis Lelic: pretty much everything that's crucial for this week. the analytics Akash accelerate. So if anyone has anything else to add the discussions we have please go ahead. Otherwise we can just meet next week or in two weeks and we can continue this discussions. + +Denis Lelic: Okay, sounds like very good. So, thanks everyone for joining today. I will see each other on Discord or slack whatever we'll see each other online async and thanks again for joining again see each other next meeting. + +Tyler Wright: Thank you. + +Piyush Choudhary: just + +Denis Lelic: Thank you. + +Thomas Greco: Thanks, everyone. + +Zach Horn: Thanks guys. Take care. + +Piyush Choudhary: tonight + +Meeting ended after 00:24:21 👋 + From 333818b92354861bb55f573ad1b866cb254784ad Mon Sep 17 00:00:00 2001 From: Drinkwater Date: Wed, 5 Jun 2024 00:20:17 -0400 Subject: [PATCH 18/55] sig-economics Update README.md add meeting details for may and june meetings Signed-off-by: Drinkwater --- sig-economics/README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) 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) | | | From 7f443a3c6237c28661d77ba2ca82dbae94f968db Mon Sep 17 00:00:00 2001 From: Drinkwater Date: Wed, 5 Jun 2024 09:09:39 -0400 Subject: [PATCH 19/55] sig-support Update README.md add meeting schedule Signed-off-by: Drinkwater --- sig-support/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sig-support/README.md b/sig-support/README.md index 467c5586..f85b2466 100644 --- a/sig-support/README.md +++ b/sig-support/README.md @@ -49,7 +49,7 @@ sig-support is responsible for defining mechanics of how support works at Akash | #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) | | | -| #34 | Wed, May 29, 2024 08:00 AM PT (Pacific Time) | | | +| #34 | Wed, June 05, 2024 08:00 AM PT (Pacific Time) | | | | #35 | Wed, June 12, 2024 08:00 AM PT (Pacific Time) | | | From fe590736f03954c61092f44b0580005bd2b8c5bc Mon Sep 17 00:00:00 2001 From: Drinkwater Date: Wed, 5 Jun 2024 09:27:25 -0400 Subject: [PATCH 20/55] sig-support Update README.md Signed-off-by: Drinkwater --- sig-support/README.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/sig-support/README.md b/sig-support/README.md index f85b2466..a7dc5dc9 100644 --- a/sig-support/README.md +++ b/sig-support/README.md @@ -44,11 +44,11 @@ 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) |Coming Soon |Coming Soon |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://www.altcoinbuzz.io/cryptocurrency-news/ionet-airdrops-5-to-strengthen-community/) |[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, June 05, 2024 08:00 AM PT (Pacific Time) | | | | #35 | Wed, June 12, 2024 08:00 AM PT (Pacific Time) | | | From de304469c972e260a6583a55f7043ddb51ebece3 Mon Sep 17 00:00:00 2001 From: Drinkwater Date: Thu, 6 Jun 2024 08:40:52 -0400 Subject: [PATCH 21/55] steering committee- Create 015-2024-05-02 (#583) * steering commitee- Create 015-2024-05-02.md Signed-off-by: Drinkwater * steering commitee Update 015-2024-05-02.md add recording link Signed-off-by: Drinkwater * Update 015-2024-05-02.md add meeting notes and action items for meeting Signed-off-by: Drinkwater --------- Signed-off-by: Drinkwater --- committee-steering/meetings/015-2024-05-02.md | 450 ++++++++++++++++++ 1 file changed, 450 insertions(+) create mode 100644 committee-steering/meetings/015-2024-05-02.md 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..2e91b4c5 --- /dev/null +++ b/committee-steering/meetings/015-2024-05-02.md @@ -0,0 +1,450 @@ + +# Akash Network - Steering Committee - Meeting #14 + +## 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 👋 + + From f7ffbc392eda20be8b69daec91df4687d60e9a29 Mon Sep 17 00:00:00 2001 From: Drinkwater Date: Thu, 6 Jun 2024 08:49:00 -0400 Subject: [PATCH 22/55] steering committee Update 015-2024-05-02.md updated the meeting number Signed-off-by: Drinkwater --- committee-steering/meetings/015-2024-05-02.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/committee-steering/meetings/015-2024-05-02.md b/committee-steering/meetings/015-2024-05-02.md index 2e91b4c5..c930b276 100644 --- a/committee-steering/meetings/015-2024-05-02.md +++ b/committee-steering/meetings/015-2024-05-02.md @@ -1,5 +1,5 @@ -# Akash Network - Steering Committee - Meeting #14 +# Akash Network - Steering Committee - Meeting #15 ## Agenda From 7b2af29a8f35e89877c1b1f7d802f8a77b7475c0 Mon Sep 17 00:00:00 2001 From: Drinkwater Date: Thu, 6 Jun 2024 08:49:29 -0400 Subject: [PATCH 23/55] steering committee Update README.md update readme table Signed-off-by: Drinkwater --- committee-steering/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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) | | | From 53bd1d11d66395f37d0c44bd18f69f584b958dc9 Mon Sep 17 00:00:00 2001 From: Drinkwater Date: Thu, 6 Jun 2024 08:51:16 -0400 Subject: [PATCH 24/55] sig-support Update README.md update links for meeting table Signed-off-by: Drinkwater --- sig-support/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sig-support/README.md b/sig-support/README.md index a7dc5dc9..1e5422b1 100644 --- a/sig-support/README.md +++ b/sig-support/README.md @@ -47,7 +47,7 @@ sig-support is responsible for defining mechanics of how support works at Akash | #29 | Wed, March 20, 2024 08:00 AM PT (Pacific Time) |Coming Soon |Coming Soon |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://www.altcoinbuzz.io/cryptocurrency-news/ionet-airdrops-5-to-strengthen-community/) |[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) +| #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, June 05, 2024 08:00 AM PT (Pacific Time) | | | | #35 | Wed, June 12, 2024 08:00 AM PT (Pacific Time) | | | From c3dfd281bb5b7d93254536c53fc704ddaa15bd7d Mon Sep 17 00:00:00 2001 From: Drinkwater Date: Thu, 13 Jun 2024 12:00:58 -0400 Subject: [PATCH 25/55] wg-provider-audits Update README.md update the meeting table. Signed-off-by: Drinkwater --- wg-provider-audit/README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) 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) | | | From 8451630759d05c2bb0ae1766e29f84ffbecccaf1 Mon Sep 17 00:00:00 2001 From: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Date: Tue, 18 Jun 2024 14:00:13 +0000 Subject: [PATCH 26/55] Create meeting notes for sig-clients #14 (#600) * Create meeting notes for sig-clients #14 Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> * Update 014-2024-03-27.md add transcript to the meeting notes Signed-off-by: Drinkwater --------- Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Signed-off-by: Drinkwater Co-authored-by: Drinkwater --- sig-clients/meetings/014-2024-03-27.md | 531 +++++++++++++++++++++++++ 1 file changed, 531 insertions(+) create mode 100644 sig-clients/meetings/014-2024-03-27.md 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 👋 + From 38080c586f73349e5be1e7aa03fc60c86d187d6a Mon Sep 17 00:00:00 2001 From: Drinkwater Date: Tue, 18 Jun 2024 10:31:08 -0400 Subject: [PATCH 27/55] sig-clients Update README.md updated meeting table with bimonthly schedule chore: add meeting 15 and 16 notes when available. Signed-off-by: Drinkwater --- sig-clients/README.md | 16 ++++++---------- 1 file changed, 6 insertions(+), 10 deletions(-) diff --git a/sig-clients/README.md b/sig-clients/README.md index 22aa65e5..16b719c6 100644 --- a/sig-clients/README.md +++ b/sig-clients/README.md @@ -46,17 +46,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 18th, 2024 10:30 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 From 1727624f6256774e9097b272e11e8127edf1ab83 Mon Sep 17 00:00:00 2001 From: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Date: Tue, 18 Jun 2024 15:51:40 +0000 Subject: [PATCH 28/55] update readme tables (#594) Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Co-authored-by: Drinkwater --- sig-design/README.md | 6 +++--- sig-documentation/README.md | 6 +++--- sig-support/README.md | 10 ++++------ .../meetings/{029-2024-03-06.md => 029-2024-03-20.md} | 0 wg-akash-website/README.md | 2 +- 5 files changed, 11 insertions(+), 13 deletions(-) rename sig-support/meetings/{029-2024-03-06.md => 029-2024-03-20.md} (100%) 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-support/README.md b/sig-support/README.md index 1e5422b1..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) |Coming Soon |Coming Soon |Coming Soon +| #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, June 05, 2024 08:00 AM PT (Pacific Time) | | | -| #35 | Wed, June 12, 2024 08:00 AM PT (Pacific Time) | | | - +| #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) | | | ## 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 From 37de4246e04f8a1fc28ff8b035293ccd744308e3 Mon Sep 17 00:00:00 2001 From: Drinkwater Date: Tue, 25 Jun 2024 11:50:05 -0400 Subject: [PATCH 29/55] sig-clients Update README.md update readme Signed-off-by: Drinkwater --- sig-clients/README.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/sig-clients/README.md b/sig-clients/README.md index 16b719c6..dcb68118 100644 --- a/sig-clients/README.md +++ b/sig-clients/README.md @@ -48,7 +48,7 @@ The goal of this SIG is to foster a community around each of these clients that | #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) |[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| June 18th, 2024 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) | | | @@ -61,9 +61,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) From 707842cbecc7b8d79b0aecfca65a6bd00ba1d3b9 Mon Sep 17 00:00:00 2001 From: Drinkwater Date: Tue, 25 Jun 2024 11:50:29 -0400 Subject: [PATCH 30/55] Update README.md Signed-off-by: Drinkwater --- sig-clients/README.md | 1 - 1 file changed, 1 deletion(-) diff --git a/sig-clients/README.md b/sig-clients/README.md index dcb68118..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 From d89c4794e2d1ffba517d891f0e7cd6a2fe4062d5 Mon Sep 17 00:00:00 2001 From: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Date: Wed, 26 Jun 2024 14:12:31 +0000 Subject: [PATCH 31/55] Create meeting notes for sig providers #16 (#592) * Create meeting notes for sig providers #16 Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> * Update 016-2024-04-24.md add transcript chore: add video recording link Signed-off-by: Drinkwater * Update 016-2024-04-24.md Signed-off-by: Drinkwater --------- Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Signed-off-by: Drinkwater Co-authored-by: Drinkwater --- sig-providers/meetings/016-2024-04-24.md | 286 +++++++++++++++++++++++ 1 file changed, 286 insertions(+) create mode 100644 sig-providers/meetings/016-2024-04-24.md diff --git a/sig-providers/meetings/016-2024-04-24.md b/sig-providers/meetings/016-2024-04-24.md new file mode 100644 index 00000000..45a48e3f --- /dev/null +++ b/sig-providers/meetings/016-2024-04-24.md @@ -0,0 +1,286 @@ +# Akash Network - Providers Special Interest Group (SIG) - Meeting #16 + +## Agenda +- Update from Praetor on all of the work that they have been doing. +- Open Discussion on all things related to Akash Providers. +- Provider Build Process and Stability +- Bid Engine Updates + +## Meeting Details +- Date: Wednesday, April 24, 2024 +- Time: 08:00 AM PT (Pacific Time) +- Recording: Coming Soon +- [Transcript](#transcript) + +## Participants +- Andrew Hare +- Andrey Arapov +- Damir Simpovic +- Deval Patel +- Jigar Patel +- Lukas Meilhammer +- Nathan Ward +- Scott Carruthers +- Tyler Wright + +## Meeting notes +#### Tyler Wright: +- Welcomed everyone to the providers monthly meeting. +- Emphasized the importance of the community repo for provider audits. Providers should follow the template available for audits. +- Acknowledged Andrey Arapov's efforts in keeping the provider announcements updated on Discord. +- Praetor’s role in facilitating upgrades for those who prefer an easier path than direct documentation. +- Mentioned efforts to ensure providers stay updated, noting some providers had outdated versions and incorrect contact information. +- Encouraged checking the provider announcements channel regularly for updates on versions and upgrade instructions. +- Weekly SIG meetings are led by Scott Carruthers with support from Andrew Hare and Andrey Arapov. +- They discuss support issues related to the Akash codebase. +- Providers are encouraged to track issues labeled "provider" in the support repo of the Akash Network organization. +- Tyler urged providers to participate in the weekly SIG meetings or leave comments on relevant issues. + +**Praetor Team Updates:** +- Tyler Wright announced the successful acquisition of the Praetor team by Overclock Labs. Praetor will soon be open-sourced, enabling community contributions and collaborative improvements. +- Jigar Patel highlighted the Praetor team's journey and expressed gratitude for the community's support. He outlined the steps being taken to open-source Praetor's three microservices. +- **Key Updates from Jigar Patel:** + - Praetor tooling will be open-sourced, with three microservices to be available for community contributions. + - Recently provided a one-click update for version 5.13 for providers. + - Active development on open-sourcing Praetor's microservices is ongoing. + +**Roadmap and Project Tracking:** +- Tyler Wright emphasized the importance of the public-facing roadmap available on GitHub in the project section. It will show ongoing and upcoming tasks, including contributions from the Praetor team. +- Providers and community members are encouraged to track progress and participate by leaving comments and suggestions. + +**Network Upgrade Information:** + - A network upgrade is scheduled for next Thursday, pending validator votes. + - Validators are encouraged to vote on the upgrade, which aims to enhance usability and unlock new functionalities such as private repositories. + - Post-upgrade, validators will test for stability on Mainnet before notifying providers to upgrade their nodes. + +**Provider Build Process and Stability:** +- Tyler Wright discussed efforts to improve provider stability and build processes. +- Scott Carruthers introduced a new automated Akash provider build process, currently in beta: + - Automated build process using K3s for Kubernetes clusters. + - Significant reduction in build time to 10-15 minutes. + - Current status: In beta, suitable for lab builds and testnet builds. + - Community and core team are invited to test and provide feedback. + - Documentation available at [Akashengineers.xyz](http://akashengineers.xyz). + +**Bid Engine Updates:** +- Scott Carruthers updated on the progress of converting the bid engine script from Bash to Go: + - Reverse engineering of the Bash script to Go is largely complete. + - Testing ongoing to ensure identical pricing outputs between Bash and Go versions. + - Discussion on supporting customization of the bid script for providers with specific needs. + - Andrey Arapov suggested maintaining support for both Bash and Go scripts temporarily. + - Consideration for an approach where providers can specify the script path to a custom binary or script. + +**Closing Remarks:** +- Tyler Wright invited additional provider-related discussions. +- Emphasis on staying engaged in discussions on Discord and GitHub. +- Reminded attendees about the upcoming SIG client call and the rescheduled steering committee meeting on May 2nd. +## Action Items +- Praetor to continue the process of open-sourcing Praetor’s microservices. +- Praetor to keep the community updated on progress and any issues via GitHub. +- Core Engineering Team to focus on improving provider stability and refining the build process. +- Core Engineering Team to Continue testing and developing the automated build process. + +# **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 providers monthly meeting for April It's April 24th, 2024 this special interest group for providers meets monthly to discuss all things related to the Akash provider. Usually have conversations have been around issues to the cost provider upgrades. There's been discussions on Those updates from the play tour team, which is a preferred and easy way to build a provider on Akash for those that are slightly less Technical and don't want to use the documentation. We've gone over the documentation in previous meetings related to the cost provider. + +Tyler Wright: There'll be a couple of announcements that I will go through before we might talk about a couple of things and then I open it up to any questions. couple things again as we talk about every month if anybody is looking to have to provide our audited please use the community repo. There is a template for those that are looking to have their provider audited Andrey Andy on Discord does a great job of keeping the announcements in the provider announcements tab updated for folks so that they can know again upgrades versions how to upgrade Etc. I know that pretor has historically followed behind with allowing those that use their path to upgrade. So again, please look out for those announcements. + +Tyler Wright: We are trying to keep people informed obviously. There's some folks that don't always check Discord as often as they are. So there are some workarounds that are being discussed to make sure that again providers upgrading because there were a group of providers that were previously audited that were running very very old versions didn't have proper contact information. So again, Andy is made announcements multiple times in the provider announcements Channel keeping people up to date and all things related to Providers and provider upgrades. + +Tyler Wright: Continuing on since our last meeting there has been a fair amount of work that's been going on related to the provider. There is a six weekly meeting that happens where usually led by Scott Arthur and with support from Andrew and Andre we go over any support issues that are in relation to the court code base in the support repo and the cash Network organization. Any issues that are related to the provider or tagged provider. And again, we have discussions about those issues during that time. So if anybody has any questions or comments about anything related to the provider any issues that they brought forth whether it be in the community or again Made issues directly, please. + +Tyler Wright: please track this repo and you can look by a track this issue the issues and the support repo and you can look by the label of report provider. And again, if you have any comments questions concerns, feel free to join that weekly meeting or feel free to drop a comment inside this relevant issue + +Tyler Wright: continuing to move on one of the big items that has happened on chain. I think it was beginning to talk about it was the community funding for prey tour to make it open source and to bring the pray to our team who was on the call today under overclock. Again, there's been some items that have been added to the roadmap. That will indicate some of the work that the Prater team will be doing on their roadmap. There will be some issues that will be created that can be tracked by folks. But again, I think the first thing is obviously there's got a lot of hard work that the prior team has done over. + +Tyler Wright: maybe two years at this point even longer to again allow another path for folks to easily build the provider. I know that when there's been issues with the prey tour app. The prior team has been very responsive and made changes as quickly as possible. They've worked very very closely with the core team on upgrades on again changing their structure to accommodate Helm charts. And again now is acquisition is now complete pray for will be open source in the near future so that it can be Community contributions. I know there's a whole plan that's pertains that provided microservices and just like a good improving the provider experience in general. + +00:05:00 + +Tyler Wright: It's going to be great to be working even more closely together on what that looks like. I do want to give Jigger and dabal a little bit of time if they want to talk because usually again during these providers they give an update on all things pray to our but again, it's a new day new age. So they'll continue to get updates on all the work that they're doing during these meetings, and it will continue to grow into more of a collaborative effort, especially as again provider microservices are broken out and The pretor cooling becomes more open source, and we get more contributions from the community. So again much. Congratulations to all the hard work and pray to our team. Go ahead. Jigar. + +Jigar Patel: Yeah, thanks Yeah, and thanks to everybody who supported us throughout our journey. we are very excited to continue work on Twitter with the work lab teams and all the family faces God Andrew and everybody actually right who supported us in our journey. And our past excellent. Now all the formalities are done. We started working on making Twitter an open source right now. And then in the meantime, we also gave one click update for 5.13 that recently updated in a provider. So that's on this road out and it's available for providers to update and + +Jigar Patel: yes, we are working currently on open sourcing all over three microservices. So our Predator is based on three microservices. So it'll be open source soon. And then obviously we will add more issues into all those data papers and we'll track and continue our work on working on those issues. + +Tyler Wright: excellent Again, the public facing roadmap for product and Engineering is in GitHub in the project section. We talked about it during the steering committee, which will happen next Thursday, May 2nd. But this is available to anybody anybody can leave comments at any time again Against this board as jigar just mentioned as they continue open source, and they have those three specific microservices that have become reposed. They will create issues inside of those repos that will then again get shown up on this board. So you can track all the work that they'll be doing amongst many other things. + +Tyler Wright: there's a number of items that kind of touch the provider. Some are More ux facing in terms of pricing and provider availability and inventory. So again, we' can always look inside this project roadmap for the product and engineering and again if you have any questions comments we can go from there. + +Tyler Wright: Besides the work that's going to be added from the parade tour team and again you'll see a reflected over the next couple of weeks on this roadmap. There are some other items that will be added to the roadmap soon. But two items that I want to call out today as many have seen on chain. There's a network upgrade that is planned for next Thursday pending boats that is open for voting right now. So if you're validator one of voting in general, please vote, on that Network upgrade functionality and I'll be unlocked. It's just like again more usability for all C. So as I can main reason for the upgrade, but there will be some other things related to again private repos that will be unlocked after the upgrade. + +00:10:00 + +Tyler Wright: As always the validator will go through the network upgrade process first. It'll be tested and make sure that it's stable. It's already been going through testing and sandbox and just a number of members of the core team have done testing. But again, once and made that upgrade happens next Thursday, and there will be a period of just making sure it's stable on Main net after that period has ended there will be a message that will be sent out to Providers to upgrade their nodes. So again, please wait for that announcement before Or doing anything next week. + +Tyler Wright: Outside of that there is one other thing that I think we kind of have touched on previously, but I want to give Scott the opportunity to talk a little bit more about this today. You can see it in testing on the product and Engineering roadmap, but one of the big task S of the core engineering team over the last three weeks has been around build product process updates as well as providers stability in general obviously with the provider incentives and the Akash Network continuing to grow. We're at the point where it's + +Tyler Wright: We've seen growing pains with the provider and stability and working through those growing pains. And we appreciate all the providers that have been helping to again do quick upgrades notice problems. But one of the things that the core team is trying to do at the highest level is just decrease the number of General problems, whether it be through testing which is continued to prove improve, month over month as well as just Figuring out at the highest level, because so much has changed with the provider so much ashamed of the network over the last few years just like going back over and spending a couple of times dedicated a couple of Cycles rather dedicated to really looking at build process really looking at the provider providers stability and fine-tuning any, technical debt. + +Tyler Wright: So again one thing that you see Andre Scott and others working on is around that provider stability. As well as provider Bill process Scott has been working with members of the community to test a new provider build process. And I know that the pretor team is also in line as to what's going on. But Scott, did you want to talk at all about provider Bill processing where it is? Just so this group on this call and those that are listening in later can get update on everything you're working on. + +Scott Carruthers: Sure, so, I guess I'm trying to remember if I have covered this in providers before I may have actually been since our last session that I started to work on this so. Sure my screen here for a second. + +Scott Carruthers: Maybe for some reason + +Tyler Wright: Not yet. + +Tyler Wright: it's popping up. Now we could hit you up now just went away. + +Scott Carruthers: Yeah, okay. Okay. + +Tyler Wright: At least for me. + +Scott Carruthers: I don't know what's going on with me. I mean, I'll try one more time. + +Scott Carruthers: about now + +Andrey Arapov: granted + +Scott Carruthers: are you able to see? + +Tyler Wright: meaning and now it's popular now it's coming up right now. Okay. Yes. + +Scott Carruthers: Yeah, mate seems to be very. unresponsive that okay,… + +Andrey Arapov: Yeah, it works. + +Scott Carruthers: so I'm not sure if there's Okay, I'm not sure if there's a little bit of a delay as I'm going through this but it should be fine either way. so as Tyler said so basically we've created a process that + +Scott Carruthers: allows a lot less friction and they provide a bill process and I would say that this is still in beta. right now and I think this can be heavily used today for lab builds or testnet builds and things of that nature and then we'll announce and also populate and the production documentation when this is ready for Primetime use so this is a engineering site that I Maintain, so this is ta.network. This is very developer focused and probably most in the audience are familiar with this from when I've This site before for different topics. But specifically for what we're talking about today. If you go to Engineers a costume Engineers that XYZ and you go to a cost provider automated build. + +00:15:00 + +Scott Carruthers: you can just read through this document yourself, but there's basically a series of install scripts that will and I describe this in the very Beginning portion or actually, it might be in the provider build section of everything that These scripts will conduct so essentially this is using 3s as the kubernetes cluster and essentially through pre scripts. We can install the characteries cluster along with and then on the worker nodes, we can install the case raise and join it to the cluster and then install persistent storage and GPU drivers and things of that nature and then finally the final build script actually builds the Akash provider, so + +Scott Carruthers: I build a large number of providers as I'm doing code testing. And so using this heavily myself. We've not been able to take the Akash provider Bill process down to a 10 or 15 minute install process. So for any of those that go through the traditional Cube spray. + +Scott Carruthers: methodology you can appreciate being a bill of cluster and 10 or 15 minutes is very powerful. And again, we look forward to being able to use this in production as well to take some of the friction away. So obviously the Prater team is very much focused on this as well and going through a Prater build. It removes a lot of the complexity and s tower mentioned earlier the Prater team and what I'm doing here in the scripts were very much in lockstep in the prettier team is looking at these scripts and are going to implement the same procedures and if they find a cause in their procedures to edit any of these processes then again, we'll be unlocked up and I can + +Scott Carruthers: Modify any of the build processes or the prayer team can modify their bill processes, but we'll ensure that we're in lockstep, but from a very high level we would love for people in the community to experiment with this. I've announced this to a caution ciders and hoping and know that I've got a response from a couple providers that have gone through this without any issues. So yeah, feel free to explore this documentation yourself, but from a very high level, this is a Automated a cost provider Bill process that with the execution of three scripts you can. build the Renaissance cluster you can install GPU persistent storage and any of those ancillary features and then build the actual cost provider itself and it Really extracts away a lot of the complex today. So no for example for GPU providers instead of having to go through. + +Scott Carruthers: And video driver installs and the runtime tool kits and things of that nature that's all abstracted and included within the build script processes. So again, we'll be testing this. Much more thoroughly over the coming. Days and weeks and then eventually release it into production. So yeah, that's basically the intent of this project and this current status. The guy heard a Pam go up. + +Andrey Arapov: Yeah, Scott. + +Scott Carruthers: I'm not looking at the meeting. + +Andrey Arapov: Thank you very much for presentation. It can hear me. + +Scott Carruthers: Yes. Yeah, I can hear you. + +Andrey Arapov: Operation looks very nice this is something that I've been like and we're beginning to join the capture something. I didn't also advocating for the beginning but there are a couple of things we need to focus really on if we want to get it to the production is the upgradeability that we can keep upgrading the cluster result impacts and the availability of such as the etcd database. That is the main ingredient of the kubernetes cluster. You need to check how it's done there in k3s so that in the event if one note is down or their moment laid down the etcd the database where all this information is stored about all config Maps secrets and so on so that there are ways to either restore it so we need to make it up somewhere. + +00:20:00 + +Andrey Arapov: Or that it has, What base of it running somewhere on different notes as well? + +Scott Carruthers: Yeah, and so to that point, I initially built this again to be able to do a code review and as we're writing new go code and the core code base. the other tests are very easily. So that's initially where we're building in and then we'll start to build on top of it as we move this to a production build. Strategy, so as we're going through that I'm adding more and more functionality to this one of the most recent updates that I just announced over the last few days is I've also now added a script to do cluster upgrades. So to be at an upgrade the k3's control plane nodes and worker nodes. This scripts will go through and basically does a analysis of the current version. + +Scott Carruthers: Running in a cost provider and then we'll look at the latest stable version and the k3's GitHub repository. And then if there's a diff between current version and latest stable the script will execute the upgrade. So I've started going through that and that works. Very well as well. So again, this is taking the kubernetes Procedure down to a 10 or 15 second procedure per node. But yeah to Andy's playing obviously that's the whole reason that we want both internal to the core team and within the community why we want this to be more thoroughly tested. We're not going to release this for production use until we've gone through all those Possible concerns so I think we're rapidly approaching that but I'm still some things that we want the community and the core team to test before we recommend this for production use. + +Tyler Wright: Go ahead Deval. + +Scott Carruthers: I'm gonna + +Deval Patel: Yeah, without wanted to add one point here there is a focus on skill ability on our side as well. Right? So when we Use the k3s are focus is on the scalability of the So basically they should be able to go from one node to I mean single note to multiple nodes are easily. + +Scott Carruthers: Yeah, absolutely. And I know that jigar in the fall and I have talked about this sum as well. So that's again something that I'm interested in The Predator team and others within the community testing as well. I think. we're probably all where k3's use over the last couple years as really started to Gain, an adoption and not just for our single node deployments but there's a lot of large Enterprise organizations that are now using k3s and multiple control plane nodes and multiple worker nodes whenever I'm using this is certainly in a multi-node environment, at least with isolated control plane and dedicated worker nodes. So any of the tests I'm doing and this is multi-node. I know the prayer team that shared possible issues that they faced in the past with k3's when it goes beyond a all-in-one node provider. So yeah, I'm + +Scott Carruthers: definitely interested in seeing the prater's teams testing of this over time and hopefully, with some of the advents and You continue to work in the k3's project As I said, I think a lot of those concerns have gone away just based on the amount that I'm seeing K3 is used in Enterprise use, but for a cost provider use specifically obviously very interested in seeing this used in large multinode clusters as well. So yeah, that's definitely one more element that we'll want to more thoroughly test before releasing to production and maybe I could even be a staged approach I think for a long time even going back A couple years ago Andy and I remember a conversation a year and a half ago where we've talked about using k3's for all-in-one node. a cost provider use so this could even be a phased rollout or possibly we + +Scott Carruthers: Recommend, the skirt build process for all-in-one providers, which is somewhat prevalent within our community. So possibly we'll roll this out and recommend this initially for small cluster use and then recommend it for larger. Cluster use as we've tested more thoroughly. + +00:25:00 + +Scott Carruthers: I'm gonna stop sharing now just so that can go back to the meet screen. But again, this will be part of production documentation initially. But if there's anyone on the call or listen to this recording that would like to play around and build a cost provider and 10 minutes and try to put this service Paces. You can currently get to this in a caution Engineers that XYZ and A automated build Tab and go from there. + +Tyler Wright: Thank you very much, Scott. That is actually a great segue to just quickly talk about. + +Tyler Wright: Docs We had a Sig documentation meeting last week or excuse me, a couple days ago during that same documentation meeting. I just want to let everybody that's here. Make sure that they're aware the documentation and this is not the documentation. It's got just reference. That's just an alpha that you all have for a cash cord engineering documentation before it makes it into again the official Doc sites for super experimental stuff with your class that Network slash docs is now + +Tyler Wright: Again under the website repo if anybody had sees any provider related documentation issues or any inconsistencies or anything that the one improve please go to the website repo you can make an issue inside the website repo and tag it documentation and again folks contributors from the community is also from the core team actively look at those issues and look to solve them. I know that recently. And I'll give you an example right now share my screen real real fast. + +Tyler Wright: So again, if you go inside the website repo you can see how to contribute to docs how to change shocks how to add new files. inside of the issues you can see issues that are tagged documentation. Here's an issue as an example that Andre saw where the documentation or Prater build was old and somebody from the community updated this yesterday and this will be merged very soon. So again, if anybody sees any provider related documentation issues where there be related or otherwise, feel free to Get involved inside that website repo again create an issue. You can create a PR if you want or just drop something in sick documentation or providers that references the issue and we'll look to get that in address as soon as possible. + +Tyler Wright: cool Real quick. One other thing. I know that Scott's been working on that touches. A provider is around bid engine scripts. I believe that now going to go as opposed to where it was historically and that's something that again Scott has shared a little bit of alpha in Akash insiders and it is currently on the projects road map. I'm trying to find it real + +Tyler Wright: But Scott, while I'm looking to find this? Is there anything that you want to give an update on as it pertains to the bid engine work? + +Tyler Wright: There we go. + +Scott Carruthers: I'm sure just briefly so as Tyler described this is a providers in the community are very familiar with the current Bachelor script that we use for dedicated or customized bit engine. So basically we're taking the current best shell script and converted to go so + +Scott Carruthers: Largely been complete for several weeks and I just needed a test environment to be able to test it against them. So just some current internal. Dev environment work that needed to be completed so that's now complete and so basically over the last couple of weeks I've had a development environment the new go logic running in parallel with the current Bachelor script and just doing an analysis to ensure that the price derived is identical. So basically just represent engineering the current best health script and along with one minor hiccup with GPU interfaces and the pricing around those which isn't really a go issue but something that currently the scripts DP on + +00:30:00 + +Scott Carruthers: for some technical reasons, but other than that anything that I throw at the new go Logic equates the exact same pricing as the current best shell script. So there's still some things that we need to work through. I'm very confident and they price derived out of the go logic so that reverse engineering is essentially done. There's still some things that we need to answer on. How people would customize that script and also I've done some testing of white listing and the ability for providers to get dedicated pricing based on the deployment address all that's working. But I think there's the core pieces of actually driving the price. I think we're perfectly in our now all converted to go and could go into production in the very near future and there's just some ancillary cases that we need to software or maybe look for their into so that's basically the effort is taking. + +Scott Carruthers: The logic that previously existed in best shell scripts and converting into go which I think is far easier to reason about especially for anyone. Familiar would go personally. I think the logic of it just and this is anything against the current bash Health script. I think it's work written excellently for what it is. But I just think they logic within the go code is a lot cleaner to look at. So yeah, that's the effort coning. They best sell script in the bid price Go logic. So yeah, hopefully we'll be able to introduce that in the very near future. + +Tyler Wright: Go ahead Andrew. + +Andrey Arapov: Yeah. do you guys want to remove a bit Script support entirely or still there will be this option kept for whoever still wants to customize with engine script because I know there are some providers that they use their own with scripts for instance. I know one provider who sets it so that it doesn't beat on really low CPU or the requests. Let's say minimum 1,000 recourse units and something like that. + +Scott Carruthers: Yeah, so that's what I was referring to and some of those. Cases that I'm very confident that the price derived out of the new go logic is identical to the pricing derived out of the previous shell script. But for those that want to actually customize the scripts we're going to have to solve for that. This hasn't really been discussed. these gray haven't happened yet, but personally I wouldn't see a future where we're going to support both the shell script and they go code. I think alternatively we need to come up with a strategy that would allow for the same type of customization. However, we do that I think it would probably involve them. + +Scott Carruthers: some variable entries are something like that that would so I understand the need and I'm very familiar with the fact that there's some providers that are customizing the bid price script and not bid on a very low resource like point one Bid, so yeah, that's something that we're definitely going to need to solve for but I believe the future would be that this would all be supported in go and then we need to solve for those educes instead of simultaneously about the bachelor script and the code logic, but yes, I'm not really something that has been solve for yet, but I obviously will be sell for before we convert to the go logic. + +Andrey Arapov: Yeah, thanks. I think the easiest to be to just keep the support for the whatever bit script people want to run just in case if they have Corner cases. I don't think it's expensive to just keep this option for the Provider Services that bit script path usually timeout options. It's just my wish and of course it can be discussed. But this is how I view things because there's a lot another point. maybe it's deserves for the engineering discussion of the providers, but the insurance is the apis because they can change but I believe the provider service will be supporting this environment variables anyway, so I guess we are good. Thank you. + +00:35:00 + +Scott Carruthers: yeah, I mean we can definitely have discussions about continuing to support both the shell script and the go logic so yeah. let's have those discussions that my personal preference would be to be able to solve for any of those needs within the go code. However, we need to do that. So for that customization where a user doesn't want to bid on. A sdl that only has 0.1. CPU to be able to solve for that and they Go logic, but yeah, we can have that discussion and maybe we will arrive at the decision that it makes sense to support both. Yeah, we'll have to say + +Andrey Arapov: Yeah, in the beginning at least here's one month. We support both and then we can cut it off something like that. It's in the worst case and if you don't gather enough information from the providers because some kind of keep running their providers and forget about or just not painted enough intention on these things being changed and then when suddenly they realized that something changed, so All right. + +Scott Carruthers: Yeah, yeah, that might be an idea as well to support both for just an intern basis. Yeah, I make sense. + +Andrey Arapov: Open that it's sort of the expensive just to let the provider run a simple script give all the data and script. I understand that it's a bash script not everyone is familiar with bash. But if it's about the structure how things look like there. It's quite easy to shape it into a better look as well, but nevertheless. + +Andrey Arapov: Yes, I don't have any specific point to that except for that. I just like love that, some things that you can really use basically I use the script is a kind of plug-in extension. So, there are a lot of software that you can use different plugins in different languages could be not necessarily a shell script. I think it actually even supports the python or whatever you specify there environment shell as well. So maybe actually if I'm not mistaken, I think it even supports you can just hide the past and you can put the binary in go link compiled and it's plugging and I think it will work because all it does it executes today or script or the binary? It's the standard input and it makes the calculations and just it's out the rate in your kitty per block and I think + +Andrey Arapov: Actually Scott, so I just hit right now this idea so that I don't miss it. Sorry if I take much time, but I think it was checking this out because maybe you can even like your go logic you can create the extension itself that would basically compile it and specify it is a bit script path to a binary and see if it works. I think or maybe a mistaken but just an idea + +Scott Carruthers: That's very much. I'm the see so to summarize just make sure that I understand you correctly the ability to update the go Logic on the same as we would be able to update the bachelor script because it's calling an external go file that… + +Andrey Arapov: Yeah. + +Scott Carruthers: what you mean? Yeah, yeah, so yeah. No, I think I did definitely that's feasible. I literally have not looked into that at all. But yeah, I think that probably would be one path is a continuing to allow. The customization of the script but it's now just in go and set of a bachelor script. So yeah, definitely think that's feasible. + +Andrey Arapov: Yeah, because I think is that then you can just here is a goal Inc version or people don't even need to care about looking into it because then I think we nearly haven't received any Community commits to the big pricing script but what I'm saying, my point is that hey you can either use that or you can use goal link implementation and you will not see any difference except which language you prefer. All you need to set is the proper bus to this binary or JavaScript. Basically, that's it. + +Scott Carruthers: Yeah, that makes sense. + +Tyler Wright: Excellent love that discussion. And did bring up another thing that I just want to touch on and I think damir has done a great job of this in the past. He will start conversations in Discord about specific features and then he will push some of those features over to discussions to get more input from the general Community. If anybody sees I would ask anybody on this call and I asked us with everybody across all calls make your voice is heard on some of these conversations. + +00:40:00 + +Tyler Wright: Whether it be for new features again related to provider just experiences. I know that we were talking I think damir had previously put feature requests around multiple bids on the same single order. I know this is something that Scott's been working on in terms of for the new go bit engine logic. But again, there was also an issue created around this as being tracked. So for those that Again have any thoughts ideas. Please get involved in some of these discussions and this will help drive, + +Tyler Wright: Priority on some of these things, along with just constant conversation in these meetings, because I know that Scott the pre-tor team other members of community often in time attendees meetings here feedback from data center providers smaller community-based providers and then take those insights back into their work. So again, feel free to get involved or stay involved in somebody's discussions and s***, but thank you very much. For the work that you do to start some of these discussions. + +Tyler Wright: All right. We talked about a number of things today doing the providers call. I wanted to see if there's anything else that anybody wants to discuss provide a related. + +Tyler Wright: again, look out for some announcements related to the main net upgrade and how it affects providers. Again. If you have the ability to vote, please vote on the main upgrade. It is planned for next Thursday. If you are looking for a provider audits, please go the community repo and said they cost that work organization and follow the template there. There will be a provider audits working group call. I know that Piper Dev and the team have been working on an automated tool and there will be a call next week Wednesday, I believe. So again, please add that to your calendar. + +Tyler Wright: And yeah, we'll just continue to work together between meetings again if anybody wants to test upgraded way that Scott has built for again building provider, please go to Akash engineering that XYZ and follow documentation. There are reach out in providers for more details. + +Tyler Wright: Both much appreciate everyone's time and about 14 minutes. We will have the Sig client calls where again folks that are building clients on top of Akash Cloud most there are a number of other teams that sometimes join that meeting. But again, feel free to get involved in the state clients call which is happening in again a little under 14 minutes and then steering committee, which is usually the last Thursday the month has been moved to again next Thursday May 2nd following the network upgrade just for timing Much appreciate everyone's time. Let's stay connected in Discord and on GitHub again. Look at the roadmap. If you have any questions about anything we talked about today, but we'll just continue to work together online much appreciate y'all. Talk soon. + +Andrey Arapov: Thank you all. Have a good one. Bye. + +Tyler Wright: Bye. + +Scott Carruthers: Thanks, everyone. + +lukas meilhammer: Dubai + +Jigar Patel: nice guys + +Meeting ended after 00:44:12 👋 + From 0a7f03558f87c94dca542feb620a94770a97e9ed Mon Sep 17 00:00:00 2001 From: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Date: Wed, 26 Jun 2024 14:13:24 +0000 Subject: [PATCH 32/55] Create meeting notes for Sig-providers #15 (#591) * Create meeting notes for Sig-providers #15 Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> * Update 015-2024-03-27.md add transcript chore: add recording Signed-off-by: Drinkwater --------- Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Signed-off-by: Drinkwater Co-authored-by: Drinkwater --- sig-providers/meetings/015-2024-03-27.md | 188 +++++++++++++++++++++++ 1 file changed, 188 insertions(+) create mode 100644 sig-providers/meetings/015-2024-03-27.md diff --git a/sig-providers/meetings/015-2024-03-27.md b/sig-providers/meetings/015-2024-03-27.md new file mode 100644 index 00000000..50c0683c --- /dev/null +++ b/sig-providers/meetings/015-2024-03-27.md @@ -0,0 +1,188 @@ +# Akash Network - Providers Special Interest Group (SIG) - Meeting #14 + +## Agenda +- Update from Praetor on all of the work that they have been doing. +- Open Discussion on all things related to Akash Providers. +- Update from Scott on provider feature discovery +- Discussion on provider feature discovery +- Provider Audits Updates + +## Meeting Details +- Date: Wednesday, March 27, 2024 +- Time: 08:00 AM PT (Pacific Time) +- Recording: Coming Soon +- [Transcript](#transcript) + +## Participants +- Andrew Hare +- Andrey Arapov +- Anil Murty +- B S +- Damir Simpovic +- Dani +- Deathless +- Deval Patel +- Jigar Patel +- Nathan Ward +- Rodrigo Rochin +- Scott Carruthers +- Thomas Greco +- Tyler Wright + +## Meeting notes +- **Welcome and Previous Meeting Recap**: + - Recap of lively discussions from the last meeting on gas fees and provider audits. + - Update on the creation of a working group for provider audits and implementation of provider incentives. + +- **Provider Announcements**: + - **Scott Carruthers**: + - Recent announcements on updating provider attributes to include RAM and interface specifications. + - Importance of updating these attributes to ensure compatibility and accurate bid responses. + - Documentation updates to reflect these changes. + +- **Provider Attributes Updates**: + - **Scott Carruthers**: + - Providers should include RAM and interface tokens in their attributes for better bid specifications. + - Updated the bid price script to accommodate pricing differentiation based on GPU interface. + - **Damir Simpovic**: + - Suggested applying similar logic to processor, memory, and storage attributes. + - **Anil Murty**: + - Explanation of efforts to standardize provider attributes and automate their update through provider inventory service. + - Importance of displaying GPU pricing to potential customers and ongoing work to make this information available. + +- **Provider Audits**: + - **Tyler Wright**: + - Reminder for audited providers to update their contact information. + - Importance of community members spreading this information to ensure all providers are up-to-date. + +- **Praetor Team Update**: + - **Jigar Patel**: + - Ongoing work on feature discovery and addressing provider issues. + - Busy with roadmap tasks and provider support. + +- **Open Discussion**: + - **Tyler Wright**: + - Network upgrades and parameter changes positively impacting gas fees and provider operations. + - Call for community assistance in spreading the word about updates and upgrades. + +- **Closing Remarks**: + - **Tyler Wright**: + - Encouraged attendees to share provider announcements and updates with their networks. + - Mentioned upcoming meetings: Sig clients monthly meeting and steering committee meeting. + +## Action Items +- All Providers to update RAM and interface attributes in their configurations. +- All Providers to Ensure contact information is current for provider audits. +- Core Team to Continue working on GPU pricing page and automation of provider attribute updates. +- Praetor Team to continue support and updates for feature discovery. + +# **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 providers monthly meeting number 15 during the provider special interest group folks come from the community come together to talk about all things related to being a provider on We get updates from the page war team, which is a tool that many folks in the community use to build and manage their providers. We talk about any provider related documentation or announcements that have been made over at the last monthly meeting number 14. There was some Lively discussion around some gas fees related to r attributes. There was some conversation about provider audits in general and there has since been a working group created around that + +Tyler Wright: there was some discussion around the provider incentives that is since gone chain passed on chain, and there's a number of folks that have already come on board. I think a nearly even hinted at some of those things at the last six providers meeting were at a meeting since then about some of those relationships. So there's again been a lot of action over the last month in terms. So what's thing going on related to their cash provider? I know that there's been a number of announcements that have been made recently as well related to + +Tyler Wright: Related to the provider. So I know that at the part of today's agenda we could touch on any of the things I talked about the top of a call. We'll check in with the page war team. to see if they have any updates on anything they're in but I do want to start to see if Scott or Andrey want to talk about anything specific related to some of the provider announcements. They've thrown in the chat over the last couple of days. So I will hand it over to Scott Andrey to get us kicked off. We're talking about some of those announcements and then we'll go into the typical agenda. + +Scott Carruthers: Yes, I'll just briefly cover I think the last couple of announcements have been related to attribute So several days ago. We announced to providers that they should begin including. They Ram token and their provider attributes and the reason for that is so if you look at an sdl and you're wants gpus in your bid you define the model and then the deploy or else has the ability to specify a Token or a RAM amount. So the reason that we sent out an announcement recommending that all providers update their attributes would they the ram token? + +Scott Carruthers: Is before that if a deployer decided to include Ram in the sdl and the provider didn't have that attribute defined then the one embed. So we had one announcement to please update mirror. So we had a number of providers that were already using those kind of attributes, but they were typically Only providers that had GPU models that had different ramp specs. So as an example some of our providers that are sourcing a0 Nvidia a100s would have already included those type of attributes because they need to specify if the a100 had 40 or 80 gigs of memory. But then if you had a RTX 30 70 or something like that, that only had one ram footprint providers typically weren't including those attributes. + +Scott Carruthers: But again, we want all the providers to update with the ram token and attributes because if I deployer decides to include that they're deploying with an RTX 37 day, but they find some value including Ram in the dly. So that was one provider attribute update and then last night yesterday we had. a request to request how providers to update their attributes an additional iteration in this time is to include the interface attribute or token, so + +Scott Carruthers: The sdl supports the ability again. This is all GPU related. The sdl allows the ability to include interface model So currently is that's just pcie or xxm. So if a deployer decides to include the interface in their sdl again the provider Like that on that if they have a attribute that includes C interface specification. So those are just a lot there. You can follow the announcements in the Jeep in the provider announcement Channel, but that's been the most significant updates and announcements over the last weekly as all related to provider attributes and ensuring that providers bid when certain specs are included in the sdl some tangential. + +00:05:00 + +Scott Carruthers: I'm updates in those regards and yesterday or this morning included the interface for GPU specifications. if I interface is included in the bid price script now has the logic to do pricing differentiation depending on the interface. So again, you could have a 100 and it could have a pcie bus or interface or I could have a xxm and we should have the ability to do pricing differentiation if they Tenant, or the deployer includes the interface and the sdl so not only do we have the announcement out to Providers to update their attributes, but bid price script has also been updated to again do pricing differentiation based on the interface of the GPU that's included in the STL. so off the top of my head. Those are the most significant announcements also. + +Scott Carruthers: everything that I just talked about from a sdl perspective has been updated and documentation. So we've also had a number of Provider documentation. updates see how the top of my head. Those are the most significant updates. + +Tyler Wright: Thank you very much, Scott. + +Scott Carruthers: does anybody any other providers in the audience have any questions and those regards? + +Scott Carruthers: Okay. + +Tyler Wright: I had damir. + +Damir Simpovic: Hello, everyone. I do have + +Damir Simpovic: I don't know. how important it is to have it implemented right now, but + +Damir Simpovic: I think the same logic would be. really prudent to apply to processor memory + +Damir Simpovic: storage, Etc. So, yeah. just for me. Yeah. + +Scott Carruthers: Yeah, yeah Yeah, so I think there's gonna be a lot of announcements and updates that are Generally in the umbrella feature Discovery. So the other thing. that is very top of mind right now as we want to take out How much manual actions are necessary in this process so feature brought us light years ahead and that you don't have to manually label your nodes any longer for gpus or other We no longer have to specify what type of menuing label nodes for persistent storage type in GPU types, and it's certainly Our intention that we're going to bring those feature discovery. + +Scott Carruthers: Aspects into attributes as So providers won't have to manually Define these attributes. So we're going to be using feature Discovery in the near future to update that and then simply to your point Not only would that be applicable to gpus but it would also be applicable to CPU and memory and so yeah, I think there's going to be a significant amount of feature Discovery related introductions in the outcome in few months + +Scott Carruthers: so that you had your hand raised did you have + +Anil Murty: I think I was going to say some of the things that you said already So yeah, as wrest Scott said basically we've had discussions about standardizing on provider attributes for a really long time. I think I may have included you on some of those discussions as well. There was a document that we started working on a while back trying to collect all the possible attributes that we could think of and come up with a standard naming convention for them as well as a structure in terms of where they sit in the IRT. So we started thinking about that a while back. We never got to actually + +Anil Murty: Implementing and enforcing that across the providers and as we were trying as we were working through and thinking on how we want to do that the provider inventory service came about and so the thinking was rather than having the updated. It'll be really nice if the inventory service could read. the capabilities on the provider automatically and updated for the providers rather than relying on people having to do it manually. So that's basically what the story of this whole thing is and so the reason why this kind of became a little bit of an urgent request this week was Driven privately by as needing to us wanting to come up with a pricing page for gpus. So one of the pieces of feedback we have gotten from a lot of customers in the last few weeks is it's great that you guys have a lot of gpus and when we get on conversations with these customers we show them. Hey robot all these gpus you can know submit a bit request you can get + +00:10:00 + +Anil Murty: a bunch of bids from whole bunch of providers on the network and they're very impressed by all that but the problem is that if somebody comes to the web page, there is no way of knowing that we have all these gpus on the network and they're available for such amazing prices, So what we realized is that we need some way of displaying what the prices specifically of the gpus but in general compute resources on the network are for anybody that comes to the network and typically anybody that comes to a web page, so It's kind of a little bit of an image not emergency. But a kind of an urgent request that we're handling one off just to deal with being able to surface up pricing on gpus and then when you talk about pricing of gpus + +Anil Murty: The type of interface that the cluster has typically PCI versus S6 and 5 or 6 and 4 that makes a significant difference on the price that the provider charges. So that's where these requests are coming in so just to provide a little more context and why number one we decided to handle just these two attributes one off And what's kind of the overall plan going forward, hopefully. Thanks. + +Tyler Wright: I had the ball. + +Deval Patel: Then that would be good for us because then from the provider side we do manage pricing at this point of time, but we do it hard way we store those in database and things and if they do it, let's say if they update their pricing directly on the price script and we don't have track of that. So that's always one issue from our side as well. + +Anil Murty: Yeah, so I think we'll have to check with the Maxi on whether he's able to expose it as an API. He's actually working On that API right now whether it becomes a public API, I think most likely it will be either way. We'll figure out a way to get it to you guys. But one of the challenges essentially just to go a little bit deeper on that is that there is no way today to extract specifically the GPU pricing from a provider directly because number one we don't actually get pricing from the pricing script directly. We only find it out when the provider responds to a big request and when the provider responds to a better request, there's quantifically to the Entire CPU of this memory storage. so max C has been working on a workaround to that he's trying to figure out the lowest. + +Anil Murty: bid request that has gone in with mostly a GPU request and then use the responses to that to figure out what the price of GPS maybe so it's not like a super accurate solution right now and we have improve it but that's kind of where + +Tyler Wright: Excellent. Does anyone have any other questions? Related to what Scott was just talking about. + +Tyler Wright: Cool kind of a natural segue before we again talk again update from the pray to our team. I know that Andy Andrew Andre, excuse me, had put a message in provider announcements about r attributes and excuse me about provider Audits and asking folks to update at least email or an organization if they have So if you have seen that in your audited provider, please look to update or if you're an Insider or somebody's active in the community, please let folks know again. We just want to make sure for things like this. There's a number of folks that go through the upgrades may not be as active and Discord, so they're hard to get a hold of and they may not know what's going on. And so we want to make sure that again folks that are in the community on this call or + +00:15:00 + +Tyler Wright: any other providers that they know or see around Discord or elsewhere know about the most recent information related to upgrades so that again all providers are as up to date as possible and then making sure that there is at least a contact information for audited providers. So that's been added recently to documentation as well as to the provider audit process moving forward Andres or anything specific you want to talk about that or + +Andrey Arapov: I guess nothing from my end. + +Tyler Wright: like other RF + +Andrey Arapov: I put it in announcement. I think it's quite clear there and people already started deleting their provider attributes. So if anyone has any additional questions, they can find me on this card or just Drop messaging providers Channel tag me or some other core member of the team. + +Tyler Wright: Thank you. All right, continuing to move along with the agenda. And again, if anybody has anything they want to talk about feel free to drop it in the chat or we'll talk to the prey to our team real fast. And then feel free to raise your hand after that. But I do want to hand it over to the Creator team. They usually give us an update on a monthly basis on things that they've been working on or just things that they're seeing related to a cost provider so printer team take it away. + +Jigar Patel: Hey guys, good morning. So from the last month as we discussed in last meeting, we are updating all the latest provider update that has the feature Discovery portion it So we gave that update with the recent Sergeant providers. We are very very busy with all the providers solving their issues plus working towards our roadmap as well. So yeah, that's a short update from us and I think so at this point of time, but we'll continue work on it. Thank you. + +Tyler Wright: Thank Again presentation does a great job of answering questions? They see inside the ecosystem pray to our Channel inside of Discord as well as in other channels. So I know that the crater team is very active all over Discord. So Much appreciated feel free to reach out to them or anybody from the core team if you have any questions there. + +Tyler Wright: Again out of the last meeting. We talked a little bit about some of the gas fees some of the things related to provider. I think it was a great Lively discussion on that. There was a network upgrade that happened March 13th that I believed stalls many of those issues as well as there was a parameter change I think came on the network March for 11th that lowered a bit amounts from five akt to 0.5. Akt so some of the Lively discussion that went on at the last providers meeting went into direct actions that have positively affect the network so much appreciated everyone's participation here. + +Tyler Wright: Is there anything that anybody wants to talk about related to the account provider that has been talked about? Quite yet on this call today. + +Tyler Wright: cool + +Tyler Wright: all right, if not then obviously everyone here is very busy. So I don't want to hold you. I know there will be a number of updates that will continue to happen and provider announcements in the providers Channel. I think aniluded to a GPU pricing page that will be added via the working group that cost website very soon. So there'll be announcements. I'm sure there again providers are continuing to come on to the network via provider incentives phase one and more relationships have been had since I know there was event set Nvidia GTC and a cubecon in Paris where conversations continued with various data centers all over that are looking to provide resource on the car. So again conversations are continuing there. as just a general + +00:20:00 + +Tyler Wright: All out and I think we've talked about this previously. But if anybody has any relationships with data centers in Latin America, Australia areas like that where you see kind of less folks generally on the map, even though again the map is continuing to get dots on it all over the world day by day. Please feel free to reach out to myself or somebody from the court team. We're actively always looking for kind of three tier four data centers in amongst many other regions, but certainly in those regions + +Tyler Wright: Cool, there's nothing else that anybody wants to talk about provider related then again. I'll certainly let you go. I would ask that everybody continue to push these messages that you see and provide our announcements out to again various providers that you have relationships with or connections with just to make sure that everybody is using the most up-to-date kind of upgrades and experiences. So again much appreciate everyone's time if anybody has any questions or comments, so they want to feel free to drop those in providers Discord Channel and we could talk about those at the next monthly meeting or between meetings. We'll have the Sig clients monthly meeting is following this in about 36 minutes, or we'll get some updates from + +Tyler Wright: the Maxes and some other folks that are looking to build tools on top of Akash, and then steering committee is planned for tomorrow. It's a normal end of months during committee. So just look after those couple of things. But much appreciate everyone's time today. Hope everyone has a great rest of their day and hope to talk to you all soon. Thank you very much. + +Andrey Arapov: Guitar lesson here on a good one. + +Scott Carruthers: Etc + +Jigar Patel: Thank you so much. + +Rodrigo Rochin: You guys. + +Meeting ended after 00:46:58 👋 + From 9982a12e6ffc8114e46cf4441e1bb35aee957d57 Mon Sep 17 00:00:00 2001 From: Drinkwater Date: Wed, 26 Jun 2024 10:48:19 -0400 Subject: [PATCH 33/55] sig-providers Update README.md Signed-off-by: Drinkwater --- sig-providers/README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/sig-providers/README.md b/sig-providers/README.md index f42318dd..08e7b94c 100644 --- a/sig-providers/README.md +++ b/sig-providers/README.md @@ -29,10 +29,10 @@ Provider SIG covers everything pertinent to Providers on Akash Network. This inc | #12 | Wednesday, December 13, 2023 08:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-providers/meetings/012-2023-12-13.md)|[Link](https://github.com/akash-network/community/blob/main/sig-providers/meetings/012-2023-12-13.md#transcript)|[Link](https://ro5kevc2mbgfpzyb7ufa5bor6thecu23sbzrqrham53ivpiljp2q.arweave.net/i7qiVFpgTFfnAf0KDoXR9M5BU1uQcxhE4Gd2ir0LS_U) | #13 | Wednesday, January 24, 2024 08:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-providers/meetings/013-2024-01-24.md) |[Link](https://github.com/akash-network/community/blob/main/sig-providers/meetings/013-2024-01-24.md#transcript) |[Link](https://7jnmboxzie2zlrw5nrmwu7ddgmzxiaywbjvmbx2xpr5qmfss7s3a.arweave.net/-lrAuvlBNZXG3WxZanxjMzN0AxYKasDfV3x7BhZS_LY) | #14 | Wednesday, February 28, 2024 08:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-providers/meetings/014-2024-02-28.md) |[Link](https://github.com/akash-network/community/blob/main/sig-providers/meetings/014-2024-02-28.md#transcript) | Coming Soon -| #15| March 27, 2024 08:00 AM PT (Pacific Time) | | | -| #16| April, 2024 08:00 AM PT (Pacific Time) | | | +| #15| March 27, 2024 08:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-providers/meetings/015-2024-03-27.md) |[Link](https://github.com/akash-network/community/blob/main/sig-providers/meetings/015-2024-03-27.md#transcript) | Coming Soon +| #16| April, 2024 08:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-providers/meetings/016-2024-04-24.md) |[Link](https://github.com/akash-network/community/blob/main/sig-providers/meetings/016-2024-04-24.md#transcript) | Coming Soon | #17| May, 2024 08:00 AM PT (Pacific Time) | | | -| #18| June, 2024 08:00 AM PT (Pacific Time) | | | +| #18| June 26, 2024 08:00 AM PT (Pacific Time) | | | | #19| July, 2024 08:00 AM PT (Pacific Time) | | | | #20| August, 2024 08:00 AM PT (Pacific Time) | | | | #21| September, 2024 08:00 AM PT (Pacific Time) | | | From 43dec9419d5e0f7da1b5578077378d048c102d90 Mon Sep 17 00:00:00 2001 From: Drinkwater Date: Thu, 27 Jun 2024 12:40:44 -0400 Subject: [PATCH 34/55] steering committee Create 016-2024-05-06.md (#613) * steering committee Create 016-2024-05-06.md Signed-off-by: Drinkwater * Update 016-2024-05-06.md add recording for meeting Signed-off-by: Drinkwater * Update 016-2024-05-06.md add participants and transcript Signed-off-by: Drinkwater * Update 016-2024-05-06.md add meeting notes and action items Signed-off-by: Drinkwater --------- Signed-off-by: Drinkwater --- committee-steering/meetings/016-2024-05-06.md | 450 ++++++++++++++++++ 1 file changed, 450 insertions(+) create mode 100644 committee-steering/meetings/016-2024-05-06.md diff --git a/committee-steering/meetings/016-2024-05-06.md b/committee-steering/meetings/016-2024-05-06.md new file mode 100644 index 00000000..8ba58472 --- /dev/null +++ b/committee-steering/meetings/016-2024-05-06.md @@ -0,0 +1,450 @@ + +# Akash Network - Steering Committee - Meeting #16 + +## 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, June 6th, 2024 +- Time: 11:00 AM PT (Pacific Time) +- [Recording](https://capv32vqn7vrb5u3qvsjn3n6y6swnjkba32ukvydflmqqhrxbswa.arweave.net/EB9d6rBv6xD2m4Vklu2-x6VmpUEG9UVXAyrZCB43DKw) +- [Transcript](#transcript) + +## Committee + +- Anil Murty, Overclock Labs +- Artur Troian, Overclock Labs +- Greg Osuri, Overclock Labs +- Scott Caruthers, Overclock Labs + +## Participants + +- Amanda Keay +- Andrew Gnatyuk +- Anil Murty +- Artur Troian +- B S +- Bold Panther +- Deval Patel +- Dominikus Brian +- Hiroyuki Kumazawa +- Jigar Patel +- Joao Luna +- Joe +- Julius Haus +- Maxime Beauchamp +- Robert Del Rey +- Rodri R +- Scott Carruthers +- 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. + + +### [Product and Engineering Board / Community + Marketing Board](https://github.com/orgs/akash-network/projects) + +- Tyler talked at a high level about the Mainnet 12 Upgrade. +- Artur shared some details around the Mainnet 12 upgrade including unlock of the fee grant module that will fully enable functionality. +- There are no API or state changes. +- Artur talked about transition to Cosmos SDK 47. This is a big item, with many steps. The core engineering team discussed plans and roadmap. +- Artur talked about the Akash SDK, which will be coming in the future. There will be documentation changes to improve process around Akash API, including examples. The new SDK will be defined in multiple steps, after Cosmos SDK 47. +- Cosmos SDK 47 upgrade is planned for end of summer or early fall. There will be many updates coming over the summer. Please come to sig-chain to learn more. +- Artur mentioned that the core engineering team is continuing to work on stability of the provider. +- Scott talked about the Provider Build improvements. Core engineering team have been testing new k3s provider build path. Feel free to test this new path, if you desire. Please join the providers discord channel for more information. +- Anil mentioned that the Console 2.0 effort is being kicked off. Cloudmos is rebranded to Console, and there are a number of features that are being worked on. +- Anil mentioned that the user experience for people to get started is a big focus. +- Anil mentioned that other focuses include a VM like experience for developers that are used to that experience. +- Anil talked about the HoomanHQ team which is working on the CI/CD solution for Console. +- Updates will happen in the sig-clients bi monthly meeting. +- Tyler talked about the wg-provider-audits meeting around the work from Piber Dev and his team for the automated auditor. +- Tyler also talked about the work from Mystic Labs around the metamask cosmokit integration. + +#### [Community and Marketing](https://github.com/orgs/akash-network/projects/6): + +- Tyler reminded everyone that Adam Wozney, Head of Community, is out for paternity leave. Amanda will be leading efforts on the events side. +- Tyler and Zach talked about Akash Accelerate 2024 and Consensus 2024, which have happenned since the last Akash Steering Committee meeting. +- 1400 signups for Akash Accelerate 2024. Over 400 people showed. There were great speakers and great connections made. +- Consensus 2024 was also a success. There were a lot of great connections. There were a number of side events at Consensus 2024. +- Tyler talked about the Hackathon as well. Results can be found here: https://dorahacks.io/hackathon/akashathon2/detail +- Rodri asked if there was any news on Brussels? +- Akash will have a large presence in Brussels. Akash is hosting a number of side events, and Greg will be speaking all over Brussels. +- Tyler talked about bounties highlighting documentation, website, and design as key areas for participation thus far. +- Robert gave a Zealy update. + + +### Github Discussions: + +- Tyler asked the Akash Community to get involved in discussions and make their voices heard. + + +### Open Discussion + +- Domi asked about some of the longer term goals for Console 2.0. + +### Action Items: + +- Follow up around Cosmos SDK 47 upgrade plan. +- Continue prep for events in Brussels. + + +# **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. It's June 6 2024 Usually the steering committee monthly meetings are at the end of each month, but with so much going on in terms of events. Again. The last two have been pushed out to the beginning of the following month. For those that are trying to track all things related to the steering committee again the notes and the transcripts and the recordings can be found in GitHub inside the community repo with specific links relative to each meeting. You can also find the agenda or again the steering committee, which we will go through here today. + +Tyler Wright: If anybody has any specific items that they want to add to the open discussions at the end of the agenda again, feel free to drop those in chat. If anybody wants to talk about a discussion that they've brought forth in the GitHub discussions again, feel free to drop that GitHub discussion in chat as well so that we can make sure that we touch on it. + +Tyler Wright: cool Her usual, we always start off the agenda trying to see if there's any review discussion or do we want to address anything Community feedback Credence to grievances or conflicts related to the cigs and working group structure. Does anybody from the community on this call have anything related to cigs or working groups that they want to discuss here today? + +Tyler Wright: Real quick for me, and I've already started to address this with some of the cigs and working groups. + +Tyler Wright: Because of participation in some cigs being very small and updates kind of being the same month over month. one of the things that I've been thinking about with other members of overclock and other members of the community is a slight restructure to the states and working groups. They've been very successful over the Inception purse for bringing people together for transparency across ideas that members of the core team are working on as well as project members of the community are working on but again from a Cadence standpoint. We are going to change a Cadence of some states and working groups and there might also be a merger of some things and working groups. So again, look out for messages in Discord, if anybody wants to get involved in a specific working group and needs more information, feel free to reach out to myself or just again, there's an entire section in the Cosh Discord where a lot of conversations + +Tyler Wright: ongoing + +Tyler Wright: So again, look out for announcements there. The one thing I'll always remind folks of is if anybody is looking for information on timing for cigs and working groups. The best source of Truth is always the website where again on the calendars page. There is a Akash Network Community groups kind of a calendar section and you can track all the specific events that are happening across six and working groups as items move again announcements will be made in specific channels. But again, that's a great source of Truth for anybody that's looking to get involved. It's there to date on all things special description working groups. Anyone have any questions on that before I continue on with the rest of the steering committee agenda? + +00:05:00 + +Tyler Wright: Much appreciate all those that have attended and contributed to discussions and get involved. So again, it goes a long way in keeping folks within the core team other teams that are building on top of a cost Network in just a general Community aligned on, goals missions projects Etc so much appreciate all those that watch the videos read the transcripts. Look at the notes attend the meeting Etc. + +Tyler Wright: All right moving on the next item that gets worked on. I guess just discussed during these meetings is the projects list inside the Akash Network organization and projects. There's two projects boards one for product and Engineering which has a roadmap across again. All things being worked on by the overclock product team as well as overclock engineering team and other members of the community that have community pool support or just generally working on things that get added to that board as well as the Akash community and marketing initiative sport. So as we normally do I'm going to because I want to spend a little more time talking about all the community and marketing initiatives. We can start off with the product and Engineering roadmap to begin with one big item that I will touch on before. + +Tyler Wright: I handed over to Archer is around the main net 12 upgrade as many of that are active participants in voters. there's a proposal rather on chain for Mania twelve upgrade. I let Archer discuss a little bit more about what that upgrade entails. + +Artur Troian: To Cosmos sdk47. + +Tyler Wright: But if you have the ability to vote and… + +Artur Troian: So this is quite substantial change as well as pretty big item in terms of work that needs to be done here team has mats two weeks ago to discussion plans… + +Tyler Wright: haven't yet, please do vote again. I'll drop the proposal in chat. I'll pass it over to Artur. Scott's to if they want to talk a little bit about the main Network upgrade and where things are today. + +Artur Troian: what we're gonna do how you're gonna do and + +Artur Troian: roadmap to this part and we have a couple items that we're still cleaning up and we should be able to update all the issue. I think the support to four about all through the work that needs to be done. But summarize it. First of all you have the entire stack to the Social Security bring us quite a few nice features like that was proposals and so forth. It brings the ABC to most updated versions and believe seven, but the biggest change from perspective World Akash is we are transitioning to allow more developers ease of use of the eye which + +Artur Troian: One word is we are trying to create I know many people don't like this abbreviation by SDK. So right now imagine a cost to cars from third-party services is a little bit hard due to documentation is I would say + +Artur Troian: Creators focused I mean core team instead of developers focused. so what we are doing the stage is + +Artur Troian: identifying what are the complex entry points into a cautious Decay and how we can fix them and then we're gonna buy the presentation a lot of that. So we're not saying the documentation is going to be changed significantly, but we are just, construction needs making sure that all the aspects of the API are covered document as well have examples and so forth. They're not a big items related to that is we are switching to vanity URLs for going modules. So for example, actually Pi report reminds their GitHub, but actual go more goes gonna be having different names purchase dedicated to mind for that and it's all been already working and you can track all the progress related to this particular transition in support issue. + +00:10:00 + +Artur Troian: the SDK for too much I would say. The stage of development of that is going to be defined in multiple Steps step. Number one is as soon as we wrap all the requirements up and have put above generation migrated to the cosmos SDK for seven. You're gonna talk to a couple clients that use API and + +Artur Troian: Ask for their feedback as soon as we get that then we transition to upgrades actual blockchain codebase or the responsnet and let everyone tested. Did you take a few weeks maybe a month? And as soon as we got all the Box make sure that the actual upgrade is fine and the API is stable. You're gonna upgrade sandbox, let it tests one more time and then move one to prepare for the actual minute. I'm great. So that's because multiplication migration as a main ad is going to happen. No earlier than end of the summer maybe even actually + +Artur Troian: Autumn time so it's still trying to figure out when but as this entire task is quite complicated. It's really hard to do some predictions on when we gonna do our clone. Right as this is going to be massive State migration. We need to develop your guidelines for especially validators to make sure that they are prepared in terms of Hardware. So the size of the ramp for example is really crucial for this before think. We gonna try to keep you updated on the actual steps and the milestones in regards of this transition. Hopefully next couple weeks. We wrap everything up and the next six chain will be able to move on. + +Artur Troian: I think it's from the location perspective and the provider side is you continue to work on which machine pro instantility of the provider and making sure that it is ready for SDK immigration as well. As the immigration brings quite a lot of API changes obviously affects provider as well as the manufact parts. So that means you're gonna have to have implemented migration for the provider side as well. And we don't have clear definition of that yet. We will be Taking this to action as soon as we please. Look at freeze on the SDK any questions + +Artur Troian: Right Tyler back to you. + +Tyler Wright: Thank you Archer. And again, I think that's a great shout out to all those that are looking to get more involved and understanding, the migration to a customer specific k47 or however that route continues to evolve. Please feel free to join the same chain meetings are a couple of new folks from other Cosmos projects that again are getting involved trying to understand and trying to support so if anybody wants to help with testing wants to help with ideation again, feel free to drop a message in Sig chain, that'll be the main focus of those discussions around again, making sure validators are tuned up and making sure that the migration is properly tested. So if you want to be involved in that process Sig chain, it's a place to get involved as we look forward in the next couple of months. So look out for updates there. + +Tyler Wright: Again, I know Artur just touched on and we've been touching on this both in sick providers in a previous steering committee readings around all the work that Scott Jigger Deval Andrea and… + +Scott Carruthers: yeah, and so for anyone that's not familiar we came up with as Tyler alluded to some build scripts that can take the Akash provider Bill process from a matter of a two-hour build down to a 10 to 15 minute build and… + +Tyler Wright: others are doing around provider build process and supporting the testing. There's also been members of the community both here on the call seek providers and… + +Scott Carruthers: that includes even… + +Tyler Wright: elsewhere that have also been testing this new provider Bill process Scott. + +Scott Carruthers: if you're have a GPU provider with a GPU driver installs… + +00:15:00 + +Tyler Wright: Don't feel oblige. + +Scott Carruthers: runtime environments and… + +Tyler Wright: You could just thumbs up… + +Scott Carruthers: all that is boiled down to a 10 or… + +Tyler Wright: if you want but is there anything specific that you want to call out? + +Scott Carruthers: 15 minute process has been tested essentially by the core team as we Build providers and… + +Tyler Wright: That might be an update on all things provided build processes still in testing? + +Scott Carruthers: clusters for code testing. So it's very well tested and now the Prater team jigarh and Deval have been testing. Thoroughly as well. So we're now in the stage of testing, durability of ensuring the STD cluster and things like that remain stable and I key threes build. So this is using these build scripts use k3's instead of our traditional Cube spray AIDS methodology. So yeah, we definitely encourage the community to engage in testing and let us know if there's any features that you would like added or if you run into any issues. + +Tyler Wright: If anybody has any questions, feel free to get active in the providers Channel as well as sick providers Channel where again a number of folks in the community are continuing to test and again as announcements. I'm getting made about Creator again. Look out for the ecosystem Predator Channel and all the work that Jigger and Deval also the provided build process and then obviously all the work they're doing on the Predator tool. + +Tyler Wright: Cool, that is a little bit of a natural segue. I don't want to call out all the things that the product team has been working on, but I did want to see if there's anything again the product team has done a great job. + +Tyler Wright: The max is jigarette the ball and Neil arm and everybody else that's working on Everything console related row. There's other again members of the community as well. I don't want to call out everybody Go ahead and Neil. + +Anil Murty: yeah, so the big thing that people need to be aware of is that We're kicking off… + +Tyler Wright: but it's a big team of folks that are consistently working on Console a number of other efforts and… + +Anil Murty: what we're calling essentially the console 2.0. + +Tyler Wright: have been doing a great job of sharing some of those updates and… + +Anil Murty: Effort and roadmap. So what that is is basically Cloud Moses obviously now rebranded to console. + +Tyler Wright: sharing some of the backlog and adding to the roadmap. I just want to see if there's anything that anybody wanted to call out that is currently working on product. + +Anil Murty: And there's a bunch of significant initiatives that we're going forward to summarize it broadly around. + +Tyler Wright: Obviously again, people can stay up to date on all things product and the road map here, but I just want to see… + +Tyler Wright: if anybody from Max or… + +Anil Murty: Improve or… + +Anil Murty: reducing fiction the people getting started on Console. + +Tyler Wright: anybody else want to call it anything specifically here today. + +Anil Murty: So that includes eliminating the need for or… + +Tyler Wright: Do not feel a blast… + +Anil Murty: giving people the option to use credit cards instead of wallets will always be supported… + +Tyler Wright: if you don't want to. + +Anil Murty: but offering the options credit cards alongside wallets is the second big initiatives around improving developer experience for people wanting to transition from using some other service to using Akash and that typically falls under sort of two or three buckets of developers so developers are coming from Traditional cloud services like gcp Azure and need a device. + +00:20:00 + +Tyler Wright: Thank you very much, India. Again, if anybody has any questions, feel free to drop those in the Sig clients Discord channel marker calendars for the sick clients meeting. I think we change a Cadence of that to buy every other month. So again, feel free to mark your calendars and make sure you join this one where we're talking. I'm sure they'll be a lot of conversation about console 2.0 the roadmap in specifics and then again ways for other people to get involved. So look out for that coming soon. + +Tyler Wright: I know there's a number of initiatives that are being worked on by folks in the community as well as by folks in the core team. I will call out to know Piper dev has been working on the automated auditor with open source tooling. There is a working group session for that on June 13th next Thursday, I believe. So again that's on the working that's on the Akash community group calendar. There's also another team Mystic Labs that previously was working on some Cosmo kit meta mask work on they got some community pool funding that team has been diligently letting folks in the community and letting folks from overclock know of their progress they are currently in testing right now and again once they're finished testing and they will get the rest of those funds but they have been again great stewards of those funds making sure that all the work is done and + +Tyler Wright: live before claiming fun. So again, those are also being tracked as well. Is there anything else on the product and Engineering roadmap that anybody wants to discuss right here while we're alive? + +Tyler Wright: cool If not, then we can jump ahead to the community and marketing initiatives. There's a number of things that I want to talk about and I'll pass it over to Zach and others to talk a little bit more detail. One thing. I will remind folks here on the call is Adam bossney who's ahead of community is? + +Tyler Wright: That one more time. I'm sorry. + +Tyler Wright: Yes, we'll talk about that actually in a brief second because that's actually in progress column if there's not an update here during the call because I don't think Amanda's here. She's traveling to some live events that are happening today in this upcoming weekend. We'll get an update soon. But before we jump into Brussels were ECC and a number of other events where we'll have a cash wrapper presentation set. I do want to go back… + +Tyler Wright: Going on fraternity leave and… + +Tyler Wright: since our last steering committee meeting Akash,… + +Tyler Wright: so he will be significantly less responsive than he normally is. + +Tyler Wright: accelerate 2024 has happened as well as consensus 2024. + +Tyler Wright: I think he's made announcements in Discord and… + +Tyler Wright: We touch a little bit about consensus 2024 and… + +Tyler Wright: other channels again to help with the vents Amanda who's been helping out significantly with the cost accelerate consensus and… + +Tyler Wright: the State Community or inside our office hours. I do want to kick it over to Zach to talk a little bit about a costume… + +Tyler Wright: will continue to support events through the summer while Adam is out is going to be managing and… + +Tyler Wright: because I know and again anybody else that was live there feel free to chime in… + +Tyler Wright: owning those efforts in terms of community efforts. + +Tyler Wright: but again,… + +Tyler Wright: Again, the Insiders are doing such a great job of almost being self-sufficient. there was so much that went into cost accelerator. We're going to continue on with the inside our office hours and there'll be a collective effort between myself Zach Scott Scott both Scott's and many others on the overclock team to try to serve as the poorest version of Adam Watson. 24 and so I just want to highlight what's happened and where we are today. So ach. If you have a second feel free to talk about our cost accelerating consensus if you don't mind. + +Tyler Wright: + +Tyler Wright: + +00:25:00 + +Zach Horn: Yeah, of course. So just a quick update on how Akash accelerate went and… + +Tyler Wright: So again while he's gone, + +Zach Horn: how consensus went because we did pull Community fundings for those things across accelerate was great. + +Tyler Wright: if you have any questions, feel free to reach out to any one of us, + +Zach Horn: I mean, it's our first event of that size that we posted,… + +Tyler Wright: but again, we'll look to keep + +Zach Horn: with full production and… + +Tyler Wright: You thriving while he's gone. + +Zach Horn: promoting it to that degree. + +Tyler Wright: And again if anybody has any thoughts or… + +Zach Horn: We had hundreds of people show up. + +Tyler Wright: questions about anything whether it be teacher events Etc. + +Zach Horn: I mean, I think the total signups were about 1400 we had about 400 or… + +Tyler Wright: Feel free to reach up. Go ahead rodri. + +Zach Horn: so that actually showed up roughly in that 25% plus range attendance. And overall, I mean it was great. there's a lot of learnings that go into these things and getting over the road bumps and putting everything together. But largely the consensus among everyone that was there. No pun intended on consensus is That it was really good. The connections were high quality. The turnout was excellent. I'm sure you guys saw some of the footage that we got from the speakers. Obviously, Eric Voorhees SRI Ram is a professor at UT Austin some really really high quality content came out of it. That's on the on the consensus side. we had the booth of the main venue. That was really great. We had the Insiders who were there, the folks from crador who know the overclock team. Lots of great connections there. I mean the Highlight in my mind from consensus was + +Zach Horn: simply that we had this booth and we had people coming up to the booth. Lots of people wanted to connect and we could have a minute to walk people through the network and really engage on a deeper level. I thought that was excellent. We also did a number of side events, around consensus. That was run by Amanda for the large part. Those went really well too. So, I mean we hosted I think five or so for five around consensus turn out for those was equally as quality as accelerate was so On the whole I would say it was a really excellent outing for us. Accelerate was excellent consensus was excellent the side events were So Really positive on the whole. I know there's a couple people on this call who were there as well. If you guys want to jump in What did you guys think? I know Anil was there? You want to jump in quickly? + +Zach Horn: And if not, no worries. + +Tyler Wright: Yeah, as I was I was there myself and… + +Zach Horn: Yeah. + +Tyler Wright: I think one thing besides obviously meeting members to the core members of the community that I hadn't met in real life but have been working with for so long was great. But again the venue and there were three venues total for a Kash accelerate all three were filled up at one point, and again it was great to see so many people in real life that took time out of their day to make sure that they were at the Cox accelerated event again consensus was great. I was only there for half of a day but on the Cox accelerated front so many people knew about it. There's some engaged with so many people that are looking to build on top of it and it's just great to connect with them in person because then you can see the excitement in their eye and you can pass some resources and you have a direct line to them which sometimes they've lost when folks are just in Discord and maybe too shy to ask + +Tyler Wright: Specific questions, but again, I think there's going to be a lot of positives that come out to a cost accelerating consensus very similar to what's happened out of eat them for some of the other more recent events. + +Tyler Wright: Thank you very much Zach again. I'm sure there will be a number of follow-up pieces of the content. I know that Dennis's not here at this meeting. I don't think because he's not allowed to go outside until he does some initial edits Robert we might be calling upon you to help support that as well. But again, there will be a lot of content that comes out of a classic celebrate as well as consensus both from the community members of the core team as well as the AV teams that was tasked with working on it. So look out for more content and follow coming soon. + +Tyler Wright: And I do want to shout out all the people that attended and hosted watch parties broadcast accelerate for the live stream. I know there was watch parties. I think all over the world, which is really exciting to see and just witness so major shout out to all the people that hosted and attended those events. And again as we can continue to push as many of those people into Discord and then into various conversations with insiders vanguards and members of the core team to get folks contributing as quickly as possible. It's just gonna further improve and improve the community. So shout out to all + +00:30:00 + +Tyler Wright: All Next up is the akashathon one thing that has happened. I believe the cash packathon happened ended on. May 17th judging took place there was a demo where again a bunch of participants that wanted to show off their work. We're able to Showcase it live to the judges. + +Tyler Wright: winners have been chosen and have been paid out. I'll drop in the link to the results in the track for people but I can't speak very much for Adam but speaking for myself again. I know there was a number of folks that have reached out to me about wanting to participate in this hackathon leading up to the last few days. It didn't seem like there were that many entries but it was very exciting to see so many different teams in individuals working on projects if anybody here was working on anything for the cops upon and wants to talk about next that's how they move forward again. Feel free to reach out to me but there were so many interesting hackathon projects again, feel free to look at the Biddle and look at door hacks to learn a little bit more about some of the projects. I know some people are continuing to develop those products even after the hackathon but again major, + +Tyler Wright: Out to all those that were involved in managing the meetups and events during the hackathon shout out Robert. I know who was also doing that both that got judges. Thank you to all the judges that quickly turned around looking at all the hackathon projects. But again, I think there was a number of interesting projects and there's a lot to look forward to as we continue to move forward. So just want to shout that out real fast. + +Tyler Wright: All right, continuing to move along Roger kind of alluded to it. One of the big events. Next up on the calendar is happening ECC and Brussels believe there's a number of side events that are also going to be happening Greg. I think as a number of speaking opportunities laws out there and their class network will do be doing a number of side events and hosting some of the other supporting events that are going on there if anybody wants to get involved in attending whether it's inside or otherwise again, there is a form in inside of his Discord channel for those that may want to attend live those decisions will be made over the next couple of days. Okay, perfect. + +Tyler Wright: One thing that again out I'll call out is a number of bounties. We try to put as many of these Bounties in the bounty hunters areas possible,… + +Tyler Wright: I think that was just talked about and inside our office hours. But again, + +Tyler Wright: but you can see some of these in progress tasks that are being worked on by members of the community and Ben's happening… + +Tyler Wright: there will be a significant more information following around all + +Tyler Wright: + +Tyler Wright: happening… + +Tyler Wright: members of the core team around against Sig documentation happening in Brussels for ECC and… + +Tyler Wright: documentation and some of these other projects that there are some Community Support rewards for those that want to participate happening some of those other Summits that are happening in that area around the same week. I don't have any more details right now. Amanda will provide some more information when she lands I think later today or tomorrow, but just that may not be a good enough to answer for your question Roger. Do you have anything specific that you want to know at this time or is anything that I can pass on to Amanda to make sure she adds in her update? So again, if anybody's looking for a way to participate, please look at the bounty Look at these project boards, feel free to leave a comment under specific issues. And then again join a cigar working group where you can talk live to the team get to know some other folks that are working on things and we can go from there. + +Tyler Wright: Is there anything else on the community or marketing initiatives board that anybody wants to discuss here live today? + +00:35:00 + +Tyler Wright: Go ahead Robert. + +Robert Del Rey: Hi everybody. I'm gonna be a little short. I'm feeling a bit under the weather today. I don't know what happened. But The silly campaign was officially over on June 1st. When you and I reviewed the submissions and we are right now in the process of Distributing the rewards. I also shared yesterday. Some summer stats about the project like how many unique users we got how many submissions? and other stuff + +Robert Del Rey: so by tomorrow we should publish the whole ceiling recap so you can have more data about the Deep if we made our goal if we reach our budget Target and what's the future gonna look like from this campaign? So yeah, expect the post tomorrow and next week actually I wanted to tell you that if it's possible to call off the call for next week, Benji, and I agreed that During the discussion period maybe we can chat in the telegram Channel, but it's not necessarily to join in a biopical at least four for one month. + +Robert Del Rey: and yeah, that's what I want to say about the hackathon. I didn't shining in these about that the hackathon and that we are waiting for Dora hacks to complete some of the payments. Or I also took delivered to arrange a call with George from Dora so we can seek about how the hackathon end. And what are the next step after this? So that's my updates. Yeah. + +Tyler Wright: Thank you very much. Robert. besides throwing those updates and Discord, if you could drop updates around zeely in this marketing ticket number 29 and an updates around the akashathon in community ticket number four 66 that would be greatly appreciated just for transparency across the organization. So that would be again much appreciated and thank you for all the work that you do. + +Tyler Wright: All Is there anything else that anybody wants to discuss discuss related to community and marketing initiatives? Again, take a look at this board in your free time to get updates. I'm sure there will be a number of more updates coming soon from Amanda and other members of the team. + +Tyler Wright: All right, if there's nothing else then again continuing on with the agenda at this point. We're at the part of the agenda. where we review any new GitHub discussions because there are a number of GitHub discussions. We want to make sure that there's a proper vetting process. We've discussed this every month at this point. We do want to ask that anybody that's made discussion and wants to talk about in more detail and is here, please feel free to raise your hand again a number of these discussions. Had come up and GitHub or a student have come up in special interest groups and working groups. We asked that the owner of discussions do their best to try to get folks from the community to participate. But again, there are + +Tyler Wright: not that many new discussions that we are having already. Talked about in some detail. I believe bold Panther is here. + +Tyler Wright: No, he's not here. Are there any discussions that anybody wants to bring up with this group here today? + +00:40:00 + +Tyler Wright: Go ahead Anil. + +Tyler Wright: Robert thank you Anil again. If anybody wants to track the conversations, there's a final proposal that again will get updated as just mentioned by a nail. There's a draft proposal that start off these conversations as well. As a number of Sig clients meetings that you can watch recordings to see demos. There's also a version in awesome It's like a scaled down version and a company blog that should be out soon for folks that one easier way to doctorize some of their stuff. But yeah again, there are more discussions in the draft proposal comments. So again, feel free to look at this train proposals and get up to speed and all think the human HQ game has been talking about and doing with the core product team over the last couple of months. + +Tyler Wright: Terrific. All right, are there any other discussions that anybody wants to bring up right now? + +Tyler Wright: Again, I ask that anybody on this call get please feel free to get involved in discussions make your thoughts and… + +Dominikus Brian: All Thank you. Tyler. Have fun questions about this console 2.0. + +Tyler Wright: opinions here and… + +Dominikus Brian: So originally in the product strategy oracas,… + +Tyler Wright: feel free to ask any questions. I'm sure there's many people in the community that have the same sort of questions,… + +Dominikus Brian: I saw there is this idea of having HPC kind of environment. + +Tyler Wright: but may not have the time or maybe two uncomfortable to ask. + +Dominikus Brian: Onto akas. + +Tyler Wright: So it does a great deal good to again speak up. + +Dominikus Brian: Will that be something still Beyond? far ahead or… + +Tyler Wright: Go ahead dummy. + +Dominikus Brian: consult 0.0 will start, toward the direction something like work manager like slurm or other stuff. it's what we usually use in the high performance Computing environment. Will that be a In the console 2.0 maybe at the end of it or something like that. Yeah, that's the question. + +Tyler Wright: Thank you. Dummy, go ahead and + +Anil Murty: Yeah, I can take that one hit only so that's a great question. + +Dominikus Brian: Yeah. + +Anil Murty: So we haven't gotten as far as looking into slurm specifically but console 2.0 at least initial goals are like I said before is to privately solve the friction around onboarding crypto as well as non crypto users that are not native to Cosmos so solving The wallet in token problem as well as the developer experience problem for somebody coming from AWS or versatile products today. the only thing we've done really from if you want to call it HPC perspective is Adding support for deploying rate clusters to So there's a blog post for that as well as a template for it. We will look to build something that is more. + +Anil Murty: Native or custom for Rey in the future. I'm talking with the developer that actually worked on that initial template. But if you have ideas around what we can do with learn. I would love to discuss those with you or if you want we can start a discussion on the discussion board as well. I think it's a great idea. + +Dominikus Brian: Thank So in my view, perhaps will come a bit later. But for a time being I'll try to explore what there is this a kubernetes are pretty good enough. I mean for you have a worker note must not and things like that, but for heavier job, there will be tough because you need to keep shuffling information here and there and it's not good, but I'll try first and when will + +Dominikus Brian: I mean the kind of things that doesn't work in this current environment and let's see whether things can be improved later on. But for now, I think this planning for this console 2.0 is exciting one more question before we end perhaps is whether in the 2.0 fashion will still pretty much stuck with Docker or is there other options that you can deploy directly bypassing the need of having a instance public docker. + +00:45:00 + +Anil Murty: Yeah, I can take that one as So yes for now. We'll just stick with Docker we have in the past at some discussions around the idea of micro VMS, but that doesn't progress very far. If you have some thoughts again around that happy to have a discussion about it as well. But now just Docker and what we're trying to do is one of the issues you'll see in the product roadmap is trying to give people experience but with Docker containers by essentially. Taking their public SSH Keys including them in the docker image and then letting them SSH into it, but there's no plans to actually get micro VMS in the near-term world map. And part of the reason is because we just have enough things just to solve from a basic, Reliability and redundancy perspective. So for example + +Anil Murty: outside of the developer experience stuff that we talked about We also have to work on the provider side of things. So one of the things as part of console 2.0 is going to be the pretor team they will and jigar they're going to work on implementing a new front-end for greater and they're going to implement that inside console. and then once that is done, we're going to look at things like + +Anil Murty: being able to select a backup provider that we can redeploy onto if the primary provider was down or the least closest for some reason. looking at pulling in data from automated audits that different team fiber Dev and Benjamin are working on things like that. So some more low-hanging fruits before we go and look at something like micro VMS. But again, if you have ideas or you spent more time researching that area you can certainly have a conversation about it. + +Anil Murty: Yep, and appreciative bringing these up. + +Tyler Wright: Thank you Domi. + +Tyler Wright: Last part of the agenda is around open discussion. Does anybody here on the call have any questions or anything? They want to discuss with the last nine minutes. We have a lot of for this call. + +Tyler Wright: All right. One thing that I can briefly talk about is again just a quick look ahead. Obviously, we have the steering committee here today, which is usually at the end of the month, but again has been moved to the beginning a month the zealing meeting for next week will be removed. But as we look ahead there are a number of items to look forward to obviously Sig chain. we might be postponing this big chain because we just had a recent change where we talked about. Somebody's Network up great things. Look out for announcements there. That will be the same days the main net 12 upgrade as well as sick Community which will be talking about events and all things related to the community think support which we just have last week, but it was postponent week before which is probably a quick meeting during six support meetings the group gets together to look at all things that are awaiting triage. + +Tyler Wright: For support repo is where all things related to the court code base are so again if anybody has want to get involved in understanding the core code base of The max is usually attend that event as well and anybody has anything related to console issues that they want to get involved in or need solving again. We discuss those during six support. A couple other call-outs again Anil mentioned what's going on sick clients of anybody wants to get involved in console 2.0 and learn a little bit more in-depth about what's going on there. Sick clients will be happening. + +00:50:00 + +Tyler Wright: Big economics is another one that has been moved back because the number of stakeholders weren't available this past week, but there's a number of topics that have been shared in a number and there's great active discussion happening in the Sig economics Discord Channel and we'll look to have the most discussions and has some action items kind of that meeting on the 18. So if anybody cares about all economics, staking some of those discussions that you can kind of see in sick economics, feel free to get involved there and then again per usual we have sick providers again analytics, which is a buy monthly meeting and then the steering committee which will happen. + +Tyler Wright: Off Thursday, June 27th. So there may be a couple more sessions that get added for a website working group and some other things. But again, feel free to get involved in a number of these signaling working groups where again we'll be going depth on number of things in real decisions are made and we look to get the community involved. There's committee support rewards in terms of akt available to those that are help that happen to get the time to help. So thank you to all those that are contributing already. Is there anything else that go ahead and deal? + +Tyler Wright: excellent All right, we've come to the end of our agenda again. I'm opened up to General discussion from those here. I appreciate everybody joining here today to know there's been a number of meetings and we're coming off of Kash accelerating consensus. So it's been a very busy period again, if you are a validator slash at voting power, please vote on The Proposal on chain right now as he's Quorum and it did schedule this. + +Tyler Wright: And with that being said the main net 12 upgrade is most likely going to be happening June 11th next Tuesday around 1600 UTC. So please mark your calendar so that we can again continue to have smooth upgraded validators or upgrade first, then we'll make announcements for exchanges and other providers to just upgrade their RPC node. But again, please mark your calendars for June 11th, especially if you're about data. + +Tyler Wright: Again much appreciate everyone's time and energy today again,… + +Robert Del Rey: Thank you, Tyler. Bye. + +Tyler Wright: feel free to get involved in significant working groups between these monthly meetings. Look out for discussion to get involved in discussions and GitHub and will continue to get ready for the meeting upgrade as well as all the other things that we're working on so much appreciate everybody here on the call today everybody listening in and look at the notes later. Hope everyone has a great rest of the day and we will talk online soon as our good friend. Adam says see you in the metaverse. Have a good day everybody. + +Meeting ended after 01:05:46 👋 + From f23d7b387ae1ece569e039d88dcfb10f09f9f092 Mon Sep 17 00:00:00 2001 From: Drinkwater Date: Thu, 27 Jun 2024 12:41:20 -0400 Subject: [PATCH 35/55] Rename 016-2024-05-06.md to 016-2024-06-06.md Signed-off-by: Drinkwater --- .../meetings/{016-2024-05-06.md => 016-2024-06-06.md} | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename committee-steering/meetings/{016-2024-05-06.md => 016-2024-06-06.md} (100%) diff --git a/committee-steering/meetings/016-2024-05-06.md b/committee-steering/meetings/016-2024-06-06.md similarity index 100% rename from committee-steering/meetings/016-2024-05-06.md rename to committee-steering/meetings/016-2024-06-06.md From e00fb5f80f3e03389f990d1828bd5a2d7d4c5aa1 Mon Sep 17 00:00:00 2001 From: Drinkwater Date: Thu, 27 Jun 2024 12:41:57 -0400 Subject: [PATCH 36/55] Update 015-2024-05-02.md update date for meeting Signed-off-by: Drinkwater --- committee-steering/meetings/015-2024-05-02.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/committee-steering/meetings/015-2024-05-02.md b/committee-steering/meetings/015-2024-05-02.md index c930b276..cd765861 100644 --- a/committee-steering/meetings/015-2024-05-02.md +++ b/committee-steering/meetings/015-2024-05-02.md @@ -10,7 +10,7 @@ ## Meeting Details -- Date: Thursday, March 28th, 2024 +- Date: Thursday, May 2nd, 2024 - Time: 11:00 AM PT (Pacific Time) - [Recording](https://s7ymsn3qwdtyyfd5tyjshf4r7a5ticrqhgf7nzpllkmf76gnqmpa.arweave.net/l_DJN3Cw54wUfZ4TI5eR-Ds0CjA5i_bl61qYX_jNgx4) - [Transcript](#transcript) From a2228dd03b5fedbc61e09017e4a3ad1eb0e7a643 Mon Sep 17 00:00:00 2001 From: Drinkwater Date: Thu, 27 Jun 2024 12:43:43 -0400 Subject: [PATCH 37/55] Update steering committee README.md add meeting 16 details to the table. Signed-off-by: Drinkwater --- committee-steering/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/committee-steering/README.md b/committee-steering/README.md index 01e570af..f52cb991 100644 --- a/committee-steering/README.md +++ b/committee-steering/README.md @@ -29,7 +29,7 @@ The Steering Committee is a special SIG that periodically evaluates the list of | 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) |[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 06, 2024 11:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/016-2024-06-06.md) |{link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/016-2024-06-06.md#transcript) |[Link](https://capv32vqn7vrb5u3qvsjn3n6y6swnjkba32ukvydflmqqhrxbswa.arweave.net/EB9d6rBv6xD2m4Vklu2-x6VmpUEG9UVXAyrZCB43DKw) | Thursday, June 27, 2024 11:00 AM PT (Pacific Time) | | | | Thursday, July 25, 2024 11:00 AM PT (Pacific Time) | | | | Thursday, August 29, 2024 11:00 AM PT (Pacific Time) | | | From 766ea3c5a9b8816077e2d3425c337f7210399c26 Mon Sep 17 00:00:00 2001 From: Drinkwater Date: Thu, 27 Jun 2024 12:44:34 -0400 Subject: [PATCH 38/55] Update steering committee README.md Signed-off-by: Drinkwater --- committee-steering/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/committee-steering/README.md b/committee-steering/README.md index f52cb991..e25967d6 100644 --- a/committee-steering/README.md +++ b/committee-steering/README.md @@ -29,7 +29,7 @@ The Steering Committee is a special SIG that periodically evaluates the list of | 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) |[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) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/016-2024-06-06.md) |{link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/016-2024-06-06.md#transcript) |[Link](https://capv32vqn7vrb5u3qvsjn3n6y6swnjkba32ukvydflmqqhrxbswa.arweave.net/EB9d6rBv6xD2m4Vklu2-x6VmpUEG9UVXAyrZCB43DKw) +| Thursday, June 06, 2024 11:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/016-2024-06-06.md) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/016-2024-06-06.md#transcript) |[Link](https://capv32vqn7vrb5u3qvsjn3n6y6swnjkba32ukvydflmqqhrxbswa.arweave.net/EB9d6rBv6xD2m4Vklu2-x6VmpUEG9UVXAyrZCB43DKw) | Thursday, June 27, 2024 11:00 AM PT (Pacific Time) | | | | Thursday, July 25, 2024 11:00 AM PT (Pacific Time) | | | | Thursday, August 29, 2024 11:00 AM PT (Pacific Time) | | | From 25295aab461c9056fa68eae40d4bae1f68e00964 Mon Sep 17 00:00:00 2001 From: Drinkwater Date: Thu, 27 Jun 2024 12:49:49 -0400 Subject: [PATCH 39/55] Update steering committee README.md add items to the agenda Signed-off-by: Drinkwater --- committee-steering/README.md | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/committee-steering/README.md b/committee-steering/README.md index e25967d6..b721509c 100644 --- a/committee-steering/README.md +++ b/committee-steering/README.md @@ -40,8 +40,8 @@ The Steering Committee is a special SIG that periodically evaluates the list of ### Typical Agenda -- Review/ discuss/ address any community feedback, greviances or conflicts -- Review [projects list](../projects-list/README.md), prioritize/ add/ remove if necessary +- Review/ discuss/ address any community feedback, greviances or conflicts. +- Review [Akash Project Boards](https://github.com/orgs/akash-network/projects) and prioritize/ add/ remove if necessary. - Review any new [Github Discussions](https://github.com/orgs/akash-network/discussions). - Since we're limited on time, discussion topics and proposals will be chosen based on the following criteria: 1. When was the discussion topic created? (older ones that have not been discussed in SC yet get priority) @@ -49,9 +49,10 @@ The Steering Committee is a special SIG that periodically evaluates the list of 3. What level of engagement has there been on the discussion thread itself? (ones with higher engagement should be prioritized over others). 4. Is the champion of the initiative on this call? (not being there to talk about your proposal means we don't spend time on it). 5. Is the champion someone who is currently active in the community? (generally priority to people that actively participate in other discussions as well is discord and sig/ wg calls) -- Open up to any other questions from the participants +- Open up the floor to any other questions from the participants. +- Look ahead at special interests groups (sigs) and working groups (wgs) for the following month. -## Leadership +## Steering Committee The Steering Commitee is initially comprised of the following members who have the most familiarity with Akash Network but the meetings are public and anyone is welcome to attend and listen-in. From 51e20b70478c72ce44105dfe54c12d16e0988571 Mon Sep 17 00:00:00 2001 From: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Date: Tue, 2 Jul 2024 14:44:56 +0000 Subject: [PATCH 40/55] Create meeting notes for sig-economics #17 (#616) * Create meeting notes for sig-economics #17 Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> * Update 017-2024-06-18.md add meeting recording and transcript Signed-off-by: Drinkwater --------- Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Signed-off-by: Drinkwater Co-authored-by: Drinkwater --- sig-economics/meetings/017-2024-06-18.md | 410 +++++++++++++++++++++++ 1 file changed, 410 insertions(+) create mode 100644 sig-economics/meetings/017-2024-06-18.md diff --git a/sig-economics/meetings/017-2024-06-18.md b/sig-economics/meetings/017-2024-06-18.md new file mode 100644 index 00000000..9836d1b3 --- /dev/null +++ b/sig-economics/meetings/017-2024-06-18.md @@ -0,0 +1,410 @@ +# Akash Network - Economics Special Interest Group (SIG) - Meeting #17 + +## Agenda +- Recap of the previous call (early May) +- Provider incentives update +- Coinbase Learn progress +- Tenant incentives discussion +- DAODAO and Cosmos Wasm integration +- Inflation and staking percentages discussion + +## Meeting Details +- Date: Wednesday, June 18, 2024 +- Time: 10:00 AM PT (Pacific Time) +- [Recording](https://camg45yyujtsslq5bwquh3pybr3ugqzi27rkdbhxfk3bgej5v5yq.arweave.net/EBhudxiiZykuHQ2hQ-34DHdDQyjX4qGE9yq2ExE9r3E) +- [Transcript](#transcript) + +## Participants +- Andrew Gnatyuk +- Joao Luna +- Robert Del Rey +- Robert Hochmayr +- Robert Koschig +- Rodri R +- Scott Hewitson +- Sean Morris +- Tyler Wright + +## Meeting Notes + +- **Provider Incentives Update:** + - Scott mentioned the progress on the provider incentives dashboard, which is almost complete. + - Action item: Scott to finalize the dashboard in the next few days. + +- **Coinbase Learn:** + - Over 500,000 activations achieved. + - Current budget is still substantial, with future campaigns and quests planned. + - Discussion on the translation of these activations on-chain and the strategy to encourage long-term holding through a staking quest with the Keplr team. + +- **Tenant Incentives:** + - No significant progress on tenant and Sonos. + - Discussion on potential pilot programs to incentivize tenant deployment. + - Update on oWce fixing, allowing for easier deployment. + +- **DAODAO and Cosmos Wasm Integration:** + - Nick Merrill's proposal to add Cosmos Wasm to Akash for community pool tokens vesting and other functionalities. + - Current focus on core functionality; smart contracts integration is a lower priority. + +- **Inflation and Staking Percentages:** + - Discussion about recent Discord discussions on inflation and staking percentages. + - Current APR is approximately 20%, with inflation around 19%. + - Props 240 and 241 adjusted inflation parameters and increased the community pool tax. + - Concerns about high inflation leading to sell pressure and negative price action. + - Scott to run some numbers and continue the discussion in Discord and the next call. + - Discussion on estimated time to reach market cap with current inflation parameters. + - Current projection: September 2030 at 344 million tokens, cap at 388 million. + - Community pool tax (40% of inflation) ensures tokens are locked and released only through governance proposals. + - Emphasis on maintaining a decentralized approach to managing the community pool for long-term health. + +- **Proposal Discussion:** + - Jeremy from Shade Protocol suggested funding a pool on Shade to enable secret AKT transactions. + - Rodri shared his experience with AKT transactions on the Secret dashboard, which were not working in December. + - Scott emphasized the importance of community input and thorough testing before moving forward with proposals. + - Encouragement for Rodri to share his experience in the discussion for better context. + +- **Inflation and Token Dynamics:** + - Sean Morris raised a question about the average tenant lease period, which led to a broader discussion about the need for more detailed metrics to understand token economics better. + - Scott mentioned the importance of tracking lease periods to understand the market dynamics and stickiness of tenant leases. + - Sean was advised to check Sig Analytics for any existing metrics and potentially raise the question there for further analysis. + +- **Additional Listings for AKT:** + - Andrew Gnatyuk asked about the strategy for additional listings of AKT on exchanges. + - Scott emphasized the trade-offs involved in paying for listings and the focus on organic growth. + - Scott mentioned that paying for listings is generally not prioritized, focusing on organic growth and meaningful integrations. + - Major centralized exchanges like Kraken have listed AKT without solicitation, showing organic interest. + - Dex listings are considered case by case, with emphasis on meaningful integrations that provide real value to the ecosystem. + +- **Proposals and Community Involvement:** + - Tyler Wright highlighted the importance of community input in discussions around inflation and staking percentages. + - Acknowledged the global nature of the community and the challenge of aligning meeting times across different time zones. + - Encouraged ongoing discussions in Discord and Sig Analytics for broader community engagement. + +**Closing Remarks:** +- Scott invited any final comments or questions from the attendees. +- Tyler Wright noted the importance of following up on inflation discussions in Discord to ensure inclusivity of community members in different time zones. +- Reminder that meeting notes and recordings are available on GitHub for review and continued discussion. +- Meeting concluded with a reminder to engage in Discord for any ongoing or new discussions. + +## Action Items +**Scott Hewitson:** + - Finalize and share the provider incentives dashboard within the next few days. + - Continue work on future Coinbase Learn campaigns and quests, including the staking quest with the Keplr team. + - Follow up on tenant incentives and potential pilot programs. + - Run numbers on inflation parameters and share in Discord for further discussion. + +**Rodri R:** + - Share experience with AKT transactions on Secret dashboard in the Github discussion thread for better context. + +**Group:** + - Consider Nick Merrill's proposal for Cosmos Wasm integration in future roadmap discussions. + +# **Transcript** + +_This editable transcript was computer generated and might contain errors. People can also change the text after it was created._ + +Scott Hewitson: All right, gmgm everybody. Today, we've got the monthly Sig economics call for June 2024. And typically how we run through these is a kind of talk some recap from the last call and then talk through any discussions either and GitHub discussions or in Discord in the cigar economics Channel. We'll talk about any props that have gone up and then touch on any items that anybody else from the community wants to bring up any ideas. literally anything at all becomes an open room. So with that + +Scott Hewitson: so last call. Was early May so it's been a month and a half since we talked a little bit about provider incentives the status on that I said, I was gonna have a dashboard up and ready to go by this call. I've got something built out that a few more things. I wanted to add to it so that I'm gonna take that as action item. I should have that and the next couple days kind of just reporting on what's been committed what's been spent and any full of funds or any context that can give + +Scott Hewitson: I think someone asked a little bit about coinbase learn and any progress on that or data points on that. And again, there's been over 500,000 Activation. So that's 500,000 people who have gone through the flow to learn about it's a good number. and it's still quite a bit of budget left. I think we've suspended one of The learn for now, we're going to do some quests and some future campaigns so that big prop that happened a while ago as being used there. What else we got? So I talked a little bit about tenant and Sonos haven't really made any significant. Movement on that there's been quite a few other things I've been dealing with. + +Scott Hewitson: But the idea essentially is we have this provider centers up. we have these committed pools and for gpus and other resources and then on the other side just like any two-sided Marketplace that incentivize a behavior having some tenant incentives to allow folks to deploy for free test out just an easier way to onboard and get people see in the power of that's unlocked now because of the update to office Basically we fixed it so that we can do it now. But if that does come I anticipate that to be a smaller pilot just to start small and then expand from there. + +Scott Hewitson: Another thing talked about last call Nick Merrill from dowdow came on you talking about adding cosmoism to Akash maybe to help with the vesting of community pool tokens or various other functionality that it would add. I know it requires entertaining accounts and that is not something that we currently have implemented on Akash and it's say it's on the road map, but it's lower priority. I think core team is, focused on the core functionality of Akash before adding kind of the flare to it with smart contracts + +Scott Hewitson: Let's see. What else we talk about. I don't think Andrew is here last time so it didn't get his great five questions that he always asked which we always appreciate and always gets the brain going a little bit. But yeah, that was last call. + +Scott Hewitson: So moving Going into the discussions just the channel and Discord. Yeah, Robert go ahead and anyone feel free to interrupt me at any time. I kind of just had this natural progression, but feel free to stop me at any time. + +Robert Del Rey: All right, I will keep betting All right. So you mentioned a cash has. 500,000 sign up in the coinbase learn but I hear the right beautiful 500,000. + +Scott Hewitson: Yes, yeah. Yeah, they call on activations. Basically it means Yeah. + +Robert Del Rey: Activation. I'm sorry. Wow. + +Scott Hewitson: And that might not translate on chain, because you do that you do it and then you get your tokens on and these are three dollar. This first one was a three dollar quizzes. So about 1.5 million and spend But I said, it might not translate on chain because it's just, three dollars worth of akt and someone's coinbase account. + +00:05:00 + +Robert Del Rey: I can imagine and I would say that not only that. I'm sure that in case they get any ATP. It's gonna happen through coinbase, this home base… + +Scott Hewitson: Sorry. + +Robert Del Rey: who holds the ponds of those learners? + +Scott Hewitson: Correct, correct. + +Robert Del Rey: so that also… + +Scott Hewitson: Yeah, so Immediately. + +Robert Del Rey: what that + +Scott Hewitson: Yeah, so when that prop passed funds were released and those are immediately transferred to coinbase. So they hold a remainder of funds. I have to talk to get an exact amount to see how much is left but there's still Sizable amount for future campaigns and quests. One of them is going to be a staking Quest. I know we've been talking with Kepler team to help with that. So basically it's like hey you get these tokens and you withdraw it and stake and you get more tokens. So incentivizing long-term holding versus just do this and dump. + +Robert Del Rey: Really cool night. Thanks. + +Scott Hewitson: Yeah. + +Scott Hewitson: all right, so going back to so Discord chat since the last call there's a few folks and I don't see any of them. Here is Camille Bob or Sith Lord? No, there's some discussions about inflation and staking percentages. I think right now we're at 20% APR ish in 19 and change on inflation. So there was a prop proposal 240 and 241 changed some inflation parameters on Akash and along with adding, or stepping up the community pool tax. So higher portion of that inflation going to the community pool that can be used for governance proposals for all sorts of different things. So when I did that the idea was to + +Scott Hewitson: by increasing the tax We also increased inflation and that was just to make sure that the actual economics and validators. stayed net even what's happened since I think so that was back in cember. So six months ago what happened has happened since is the ratio bottom number of tokens bonded has gone down. So The inflation amount It's gone higher because how it's set up is basically you have a Target and Target bonded ratio of 67% and when it's below that inflation is higher and then as you reach that and go over it and then inflation goes down so current parameters are 13. The Min is 13% and the max is 20% + +Scott Hewitson: So I know some folks have been concerned about that from the standpoint of price action and people say hey Cosmos tokens. They just have high inflation just cause people to dump I know, the past week. Price action has not been as favorable and there's kind of an overall Market Trend down but it's definitely a concern I wanted to address and if you go back to the original Genesis and unlock schedule, so three four years ago the original calculations. We're supposed to buy this time. We were supposed to have 245 million and tokens and supply. + +Scott Hewitson: Circulating Supply. It's like 240 when we ran the calculations last December it was showing 234 so I say that all Say the original schedule. We're still under This updated one. We're a little over it. I talked with Chang a little bit offline and + +Scott Hewitson: without us saying hey we want to reduce inflation. it's definitely something we're thinking about and if there's concerns broadly, it can be changed with the governance proposal. Anyone can put up that proposal if you need help putting it up. By all means over at this point. I don't know if overclock will we may but yeah, if there's concerns or folks who want to explore that more run the numbers more. I'm happy to help assist in any way. or none of the folks that were talking about that in Discord are here. Is there anyone want to talk about it at all? So inflation parameters or any questions about it. Just want to give anyone an opportunity to voice concerns or bring up ideas or anything else. + +00:10:00 + +Scott Hewitson: Yeah, Robert, go ahead. + +Scott Hewitson: No, definitely appreciate that and it's really been recent within the past year and change that we've had the community pool tax and we weren't really working with the community pool for a while. So the 240 and 241 were put into place kind of, open the faucet a little bit for the community pool. And if you look at the proposals that have passed I mean it's all things that are progressing the network. So yeah, I'm a firm believer of having a healthy community pool. But I also do realize inflation is a little high maybe we feel around a point where the community pool is, sufficient we can dial it back and the other thing you could do too is, reduce inflation and increase tax a little bit more to kind of even things out if people are worried about seeing a 20 + +Scott Hewitson: and staking APR, I know anything over 10 people serve people are it's just I don't know if it's a mental thing or not. But I know some folks don't like to see those high percentage staking aprs and then it also can contribute to some cell pressure as well because they're all right. I've got my tokens and this is all just cherry on the top so I can just sell those and be good. But no, I definitely definitely appreciate the perspective Robert and I tend to agree with you at a healthy community pool is good for the ecosystem at Large. + +Scott Hewitson: All right, if anyone has anything else they want to talk about from inflation. I'll take an action to kind of run some numbers and put it into Discord and we talked about a little bit more next call as well. Andrew what's going on man? + +Andrew Gnatyuk: Yeah. Hey guys, what's up? Hey Hey My to say just a question about the inflation do we have estimated that time when we will reach market cap on our tokens full open Supply with this inflation … + +Scott Hewitson: Hey, hey. + +Andrew Gnatyuk: if going to be like + +Scott Hewitson: Yeah. yeah, let me so I'm going I'm looking at the original Genesis unlock schedule and + +Scott Hewitson: In how that was set up as it has the APR starts high and it gets lower over time there. this one that I'm showing shows September 2030 is at 344. I think we have a cap of 388. So it would be + +Andrew Gnatyuk: Yeah. + +Scott Hewitson: seven eight nine years from now. Depending on they're all parameter changes so you could put inflation to 75% and if it passed governance, it would be at that. But yeah as of right now. we're actually under what the original. the supply estimates were + +00:15:00 + +Andrew Gnatyuk: Got it. Yeah, it's a problem with that. + +Scott Hewitson: yeah. + +Andrew Gnatyuk: Thanks. Thanks. + +Scott Hewitson: but to say it again, I think it's something to look at and we should definitely try to make sure that that is that there's a supply estimates are kind of staying closest to what we were originally intending. + +Andrew Gnatyuk: Yeah, I agree actually think that we have quick decent community pool for now. That's just a concern about basically for the price actions just right because for example the seedlord and this guys are coming from price group. So yeah, eventually they invest in can they just wanted to make sure that not many talking are going into the market on the monster basis. basically look + +Scott Hewitson: Yeah. Yeah. No, I mean, because the community tax of 40% going of that inflation going to the community pool. I mean that's tokens that are not in the open market, right? they to become into the open market. They ask, someone has to put up a community support or Community spend prop that would release those tokens into the market. So even though it's high it's going into a locked pool that can only be unlocked by governance. + +Andrew Gnatyuk: Yep, you got it. + +Scott Hewitson: Which actually I think it's for long term. I know overclock is, we help Steward things, but a community pool. That's the centralized and you can only release funds through governance and the community, I think that's better than having, a bunch of tokens that someone controls so we have,… + +Andrew Gnatyuk: agree + +Scott Hewitson: a bunch of tokens that everybody controls and if you look at the proposals that have passed or not passed as a community at large, I think we did a pretty good job of snuffing out things when it doesn't make sense and pushing things through when it does make sense. + +Scott Hewitson: all right, I'm gonna is anyone have anything else they want to say from the inflation standpoint. If not looking at proposals, so there's been software upgrade proposals but no community pool. there is one right now. So yeah, if you haven't voted on that go vote looks like it went up today actually. + +Scott Hewitson: Yeah, rodri, go ahead. + +Scott Hewitson: Yeah, Thanks for keeping me honest. Time go for it. + +Scott Hewitson: Thank you for that context. I know this is a prop for sixty thousand dollars. talking about the inflation. So this is community pool funds this is something that's going to help the network and the community gets to vote on it. So I think it's a cool thing we have going. It's a really way of operating so yeah. What else we got? Let's see. So yeah, other than that and I don't see any major proposals. + +00:20:00 + +Scott Hewitson: if there's anything else I wanted to chat about. I know. Jeremy from shade protocol. He posted and say economics five minutes before this call has been talking about asking for funds to fund a pool on shade which is built on secret and the rationale is so that people can get akt in a secret manner. Because there is no so you go to secret and then you could buy akt there and it would all happen secretly. + +Scott Hewitson: my opinions on that are I'm open to seeing open it's see things test things out, I try to play Switzerland quite a bit with the proposals, but we'll see maybe Ty we can if he's been waiting for a while. He's been doing all the diligent things that we ask folks before putting up proposals. Maybe we can get him, a minute or two and steering committee to try to propose his idea at the larger community. + +Scott Hewitson: Rodri what's going on? + +Rodri R: just wanted to add to that that I tried buying akt on secret dashboard a few months ago and it was not working. I even posted it in one of our channels. And try to contact the secret team, but I haven't tried it again and didn't receive a confirmation that they made it work. So maybe someone wants to have that too that discussion or if not all at it and if it's already working because I think it was in December or something like that, and it was not working. + +Scott Hewitson: Interesting was that on shade protocol built on a secret or… + +Rodri R: What it was not a shape protocol. + +Scott Hewitson: is it some other decks on speaker? + +Rodri R: It was on secret dashboard. But yeah,… + +Scott Hewitson: Okay. + +Rodri R: maybe on shade is working. I haven't tried it. Maybe I'll give it a try. But I don't think it's available yet. + +Scott Hewitson: Yeah, that's what this proposal is to do is basically take some community pool funds to help see to liquidity pool on shade so that folks can do that. + +Scott Hewitson: But yeah, that would be great. If you could at the very least drop your experience into there because into that discussion, that's discussion 543 because that just helps folks with more context saying hey, I wanted to do this I couldn't so this helps unlock that… + +Rodri R: So for I think shade protocol and… + +Scott Hewitson: then that would be good. + +Rodri R: the secret dashboard they complement each other. So that's why I was sharing this here. + +Scott Hewitson: No, Really? Appreciate that. All That's all I had from a plan standpoint. + +Scott Hewitson: Is there anybody wants to bring up anything at Large? Thai go ahead + +Tyler Wright: I don't have the answer on hand to this. But Sean Morris did drop a question in the chat that was unrelated asking was curious… + +Scott Hewitson: + +Tyler Wright: what the average tenant lease period is + +Scott Hewitson: I don't know that I'm sure there's some stats. I'm like the cloud on the skies. I know because I mean all the data is indexed. But yeah, that would be a good question and Sig analytics and maybe that question has been asked and sea Analytics. + +Sean Morris: Okay, I'll take a look. Thanks. + +Scott Hewitson: Yeah, no worries. + +Scott Hewitson: Yeah, because I do know that Lisa's are being indexed with the cloud listen to indexer. + +Sean Morris: That's sort of my yeah,… + +Scott Hewitson: So if it's not shown and… + +Sean Morris: so that I think the stats stackboard tracks like total outstanding leases,… + +00:25:00 + +Scott Hewitson: stats that network and… + +Sean Morris: but it doesn't do anything about sharing… + +Scott Hewitson: you… + +Sean Morris: which is sort of what I'm more curious about. + +Scott Hewitson: It would be a good metric to track because it shows to the sticking power, if there's leases that are years long versus, there's leases that are five days. Nobody goes past five days. It's probably not a good thing. + +Andrew Gnatyuk: Yeah, yeah client point of discussion as the distance alive community and… + +Scott Hewitson: yeah, no, that's definitely be an interesting metric to check. + +Andrew Gnatyuk: with lots of listings already for akt are we still looking for additional access to list akt to find the pools for that or… + +Scott Hewitson: All Does anyone have any other questions related to Sig economics or tokens or… + +Andrew Gnatyuk: something like that or… + +Scott Hewitson: anything at all, Andrew? my question man. + +Andrew Gnatyuk: additional listings at all, except the major Exchange. That we don't talk about. + +Scott Hewitson: yeah, I'd say I mean no, I mean, yeah, that there's definitely a part of exchange it having exposure right where there's more avenues for people to buy the token. that's better. It's kind of just the trade off of All right, this small exchange and this area wants to charge 300 Grand to have akt listed and you might get a hundred thousand and volume or something from it. So I know from I'll say the core teams focus and kind of like, everything's open source anyone can add it. we're happy to help with any kind of technical integration and technical support but really paying listing fees is not really what we're trying to do at the moment. + +Scott Hewitson: I know there's a few major centralized exchanges that are left that we're not listed on. always trying to see what we can do about those but in general, the pay to play stuff. We haven't really + +Scott Hewitson: entertained as much and then from the deck side. So seating pools with liquidity. It's like this, shade protocol discussion. And I think the question to ask is anytime like something comes in to me. It's like I'll look and All right. This Dex it's built on this chain or that, is it what kind of volume are they doing? it's funny when akt is pumping. Everybody wants to list it like hey, we want to when it's not people aren't trying to list it so I think a lot of these deckses they tried to + +Scott Hewitson: they try to ride the waves as things are going up. + +Scott Hewitson: That being said if there's something more than just liquidity like the shade one because you can't get akt secretly anywhere else and… + +Andrew Gnatyuk: Yep. Got it. + +Scott Hewitson: that would be a more compelling story for me. I'm just one person and just one person on the team. But yeah, I mean if it's a Decks that has, a million BBL and they're asking for a hundred grand of Liquidity, it's like all right, is that using those tokens there? + +Scott Hewitson: I don't know. But yeah, I think yeah in general. We haven't been paying for listings, which I think is a good thing and Dex is kind of case by case. Yeah. + +Scott Hewitson: All Yeah, I know it's like, we all get hit up all the time. Hey, We want to list here and kind of say yeah go for it. + +00:30:00 + +Scott Hewitson: Yeah. + +Scott Hewitson: Yeah, and realistically too it's some of the I think Kraken listed us without even telling anybody so, it does happen. So + +Scott Hewitson: does it really like dex's are exchanges they're making money off of volume. So special if akt volume is going up and there's a lot of trading volume. That's where they can get their trading fee. But yeah as volume goes down, they're not as + +Scott Hewitson: I guess incentivized to Add tokens. + +Tyler Wright: Here real quick. I was just gonna follow up to the question is Sean have anybody has any questions like that? + +Scott Hewitson: Already, does anyone else want to bring up anything at all any ideas any comments? + +Tyler Wright: Feel free to drop them and sick analytics and… + +Scott Hewitson: And … + +Tyler Wright: then members of the core team. + +Scott Hewitson: you could say hey,… + +Tyler Wright: I think Scott you mentioned this… + +Scott Hewitson: we're not running Sig economics. + +Tyler Wright: but members of the core team that are working on the indexer can help with scripts or… + +Scott Hewitson: We could do it better, always looking for ways to improve try to make these very open and… + +Tyler Wright: queries to look for that kind of stuff. + +Scott Hewitson: and welcoming,… + +Tyler Wright: So if there's any other questions on that front again,… + +Scott Hewitson: anyone who is new I think yeah anyone who's new… + +Tyler Wright: feel free to drop in the sick and let us out that Sig meets every other month. So feel free to get engaged there. + +Scott Hewitson: if anyone wants to talk or you… + +Sean Morris: Awesome. Thanks Tyler. + +Scott Hewitson: bring up anything at all. The floor is open. And if not, we can catching the cut things short. We've got another 25 minutes, but if there's not a lot of chatter than we don't have to go the full time. So I'll leave it open One Last Time Ty. + +Scott Hewitson: All I think with that we can conclude today's meeting. I'll give one last chance anybody want to say anything. Doing once go in twice. + +Tyler Wright: Yes, sorry. One thing I will add is I know that a couple of people that were having those discussions around inflation. They are based in parts of the world… + +Scott Hewitson: I saw a hand raise. + +Tyler Wright: where I think it's three o'clock in the morning for them right now. + +Scott Hewitson: I don't know if you were clapping or trying to raise a hand. + +Tyler Wright: So maybe we can follow up with these discussions in the chat and… + +Scott Hewitson: It happens I do that all the… + +Tyler Wright: Discord to make sure that they know that we talked about them and… + +Scott Hewitson: All righty. + +Tyler Wright: we can continue discussion there… + +Scott Hewitson: All thank you everyone for joining we'll have these notes up in there on GitHub on these as a reminder. + +Tyler Wright: because I think again some of these six have participants from all over the planet. So it's hard to get everybody aligned to come to the same meeting time. So again,… + +Scott Hewitson: All these calls are recorded and… + +Tyler Wright: especially Sig economics… + +Scott Hewitson: transcribed and… + +Tyler Wright: if anybody + +Scott Hewitson: we have notes taken for them. + +Tyler Wright: Want to bring up any conversations between meetings in a Discord cut,… + +Scott Hewitson: So if there's anything you want to free review go for it. + +Tyler Wright: that would go a long way. + +Scott Hewitson: And if there's anything you want to drop into Sig economics, feel free can tag whoever I feel like we do pretty good job of getting back to folks. + +Andrew Gnatyuk: Smile right my guys. + +Robert Del Rey: guys + +Scott Hewitson: no, that's a great call out and I'll make sure to post and say economics that we talked about it and they can review the video and ask any other questions. + +Scott Hewitson: Alrighty, I hope everyone has a great rest of your day, and we'll talk soon. Appreciate y'all. + +Meeting ended after 00:33:40 👋 + From 0cc01b855de30dab2f9c63ec03703c2364e35d83 Mon Sep 17 00:00:00 2001 From: Drinkwater Date: Tue, 2 Jul 2024 14:04:33 -0400 Subject: [PATCH 41/55] sig-economics Update README.md update meeting table to add notes and recording for June meeting Signed-off-by: Drinkwater --- sig-economics/README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/sig-economics/README.md b/sig-economics/README.md index 1f6d5fef..5e80050c 100644 --- a/sig-economics/README.md +++ b/sig-economics/README.md @@ -26,10 +26,10 @@ Meetings happen every [First Wednesday of the Month](https://calendar.google.com | #12| Wednesday, January 10, 2024 10:00 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-economics/meetings/012-2024-01-10.md) | [Link](https://github.com/akash-network/community/blob/main/sig-economics/meetings/012-2024-01-10.md#transcript) | [Link](https://gbxszp7zaubg3dskphdcgwpqkjtz3mb3zgtq46ka2yyzzkfij7na.arweave.net/MG8sv_kFAm2OSnnGI1nwUmedsDvJpw55QNYxnKioT9o) | #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 +| #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) |[Link](https://445y2d4z2tii6zb3mgio36s2cgvrem3ghe7qjvjtmwfpwsgwzbjq.arweave.net/5zuND5nU0I9kO2GQ7fpaEasSM2Y5PwTVM2WK-0jWyFM) | #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) | | | +| #17| June 18th, 2024 10:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-economics/meetings/017-2024-06-18.md) |[Link](https://github.com/akash-network/community/blob/main/sig-economics/meetings/017-2024-06-18.md#transcript) |[Link](https://camg45yyujtsslq5bwquh3pybr3ugqzi27rkdbhxfk3bgej5v5yq.arweave.net/EBhudxiiZykuHQ2hQ-34DHdDQyjX4qGE9yq2ExE9r3E) +| #18| July 3rd, 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) | | | | #21| October 2024 10:00 AM PT (Pacific Time) | | | From 2c5516d3b99f8a40b252bbe9e8ee18e22870180a Mon Sep 17 00:00:00 2001 From: Drinkwater Date: Tue, 2 Jul 2024 17:27:03 -0400 Subject: [PATCH 42/55] community-pool-spend-reporting Create README.md work in progress repo for individuals and teams to report on funds from Akash Community Pool. Signed-off-by: Drinkwater --- community-pool-spend-reporting/README.md | 15 +++++++++++++++ 1 file changed, 15 insertions(+) create mode 100644 community-pool-spend-reporting/README.md diff --git a/community-pool-spend-reporting/README.md b/community-pool-spend-reporting/README.md new file mode 100644 index 00000000..0d5f41cf --- /dev/null +++ b/community-pool-spend-reporting/README.md @@ -0,0 +1,15 @@ + + +# Akash Network Community Pool Spend Reporting + + +### The Community Pool Spend Reporting Repo is an area where individuals share reporting for all intiatives that have used funds from the Akash Community Pool. + + +## Community Pool Reporting Table + +| Proposal Number | Name | Link to Proposal | Link to Report +| --- | --- | --- | --- | +| --- | --- | --- | --- | +| --- | --- | --- | --- | +| --- | --- | --- | --- | From 3ae0c45030c9021e3cbb4c3cdd2521ba2c14dfe9 Mon Sep 17 00:00:00 2001 From: Drinkwater Date: Tue, 2 Jul 2024 17:55:08 -0400 Subject: [PATCH 43/55] Update README.md Signed-off-by: Drinkwater --- community-pool-spend-reporting/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/community-pool-spend-reporting/README.md b/community-pool-spend-reporting/README.md index 0d5f41cf..3de6a25c 100644 --- a/community-pool-spend-reporting/README.md +++ b/community-pool-spend-reporting/README.md @@ -3,7 +3,7 @@ # Akash Network Community Pool Spend Reporting -### The Community Pool Spend Reporting Repo is an area where individuals share reporting for all intiatives that have used funds from the Akash Community Pool. +### The Community Pool Spend Reporting Repo is an area where individuals / team share reports for all proposals that have used funds from the Akash Network community pool. ## Community Pool Reporting Table From 574b6e123ab394bbfdf3b8016efe1fc14cbe78f4 Mon Sep 17 00:00:00 2001 From: Hewi <121134490+heyhewi@users.noreply.github.com> Date: Tue, 2 Jul 2024 23:02:27 -0500 Subject: [PATCH 44/55] community-pool-spend-reporting Update README.md (#619) --- community-pool-spend-reporting/README.md | 23 ++++++++++++++--------- 1 file changed, 14 insertions(+), 9 deletions(-) diff --git a/community-pool-spend-reporting/README.md b/community-pool-spend-reporting/README.md index 3de6a25c..5c2d8181 100644 --- a/community-pool-spend-reporting/README.md +++ b/community-pool-spend-reporting/README.md @@ -3,13 +3,18 @@ # Akash Network Community Pool Spend Reporting -### The Community Pool Spend Reporting Repo is an area where individuals / team share reports for all proposals that have used funds from the Akash Network community pool. +### The Community Pool Spend Reporting Repo is an area where individuals / teams can share reports for all proposals that have used funds from the Akash Network community pool. - -## Community Pool Reporting Table - -| Proposal Number | Name | Link to Proposal | Link to Report -| --- | --- | --- | --- | -| --- | --- | --- | --- | -| --- | --- | --- | --- | -| --- | --- | --- | --- | +## Community Pool Spend Reporting Table +| Proposal Number | Pass Date | Name | Link to Discussions | Link to Proposal | Link to Report | +| --- | --- | --- | --- | --- | --- | +| 260 | July 01 2024 | 2024 Q3 Events Resourcing Proposal | [Link](https://github.com/orgs/akash-network/discussions/380) | [Link](https://www.mintscan.io/akash/proposals/260) | [Link](https://lookerstudio.google.com/u/1/reporting/96c38594-7ec4-4a4f-9128-3feaf3b82ac8/page/BIUND) | +| 259 | July 01 2024 | 2024 Q3 Community Support Proposal | [Link](https://github.com/orgs/akash-network/discussions/394) | [Link](https://www.mintscan.io/akash/proposals/259) | [Link](https://lookerstudio.google.com/u/1/reporting/f12da20a-b5bf-4f80-8a45-ff8861a1473e/page/BIUND) | +| 254 | April 05 2024 | 2024 Q2 Events Resourcing Proposal | [Link](https://github.com/orgs/akash-network/discussions/380) | [Link](https://www.mintscan.io/akash/proposals/254) | [Link](https://lookerstudio.google.com/u/1/reporting/96c38594-7ec4-4a4f-9128-3feaf3b82ac8/page/BIUND) | +| 250 | March 15 2024 | Akash Accelerate 2024 | [Link](https://github.com/orgs/akash-network/discussions/499) | [Link](https://www.mintscan.io/akash/proposals/250) | [Link](https://lookerstudio.google.com/u/1/reporting/b321bc26-970e-4f1a-9863-3200164b0cee/page/BIUND) | +| 246 | February 09 2024 | Akash Network Provider Incentive Pilot | [Link](https://github.com/orgs/akash-network/discussions/448) | [Link](https://www.mintscan.io/akash/proposals/246) | [Link](https://lookerstudio.google.com/u/1/reporting/f2f8fe80-97cd-45cd-bbd0-17826eab5ae5/page/BIUND) | +| 245 | January 23 2024 | 2024 Akash Hackathons Proposal | [Link](https://github.com/orgs/akash-network/discussions/415) | [Link](https://www.mintscan.io/akash/proposals/245) | --- | +| 244 | January 15 2024 | 2024 Q1 Events Resourcing Proposal | [Link](https://github.com/orgs/akash-network/discussions/380) | [Link](https://www.mintscan.io/akash/proposals/244) | [Link](https://lookerstudio.google.com/u/1/reporting/96c38594-7ec4-4a4f-9128-3feaf3b82ac8/page/BIUND) | +| 243 | January 10 2024 | 2024 Q1 Community Support Proposal | [Link](https://github.com/orgs/akash-network/discussions/394) | [Link](https://www.mintscan.io/akash/proposals/243) | [Link](https://lookerstudio.google.com/u/1/reporting/f12da20a-b5bf-4f80-8a45-ff8861a1473e/page/BIUND) | +| --- | --- | --- | --- | --- | --- | +| --- | --- | --- | --- | --- | --- | From 26baa8527beabde0199d9defac492c4576b28290 Mon Sep 17 00:00:00 2001 From: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Date: Sun, 7 Jul 2024 15:44:47 +0000 Subject: [PATCH 45/55] Create meeting notes for wg-provider-audits #2 (#618) * Create meeting notes for wg-provider-audits #2 Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> * Update 002-2024-06-13.md add transcript and recording link Signed-off-by: Drinkwater --------- Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Signed-off-by: Drinkwater Co-authored-by: Drinkwater --- wg-provider-audit/meetings/002-2024-06-13.md | 411 +++++++++++++++++++ 1 file changed, 411 insertions(+) create mode 100644 wg-provider-audit/meetings/002-2024-06-13.md diff --git a/wg-provider-audit/meetings/002-2024-06-13.md b/wg-provider-audit/meetings/002-2024-06-13.md new file mode 100644 index 00000000..f93bf797 --- /dev/null +++ b/wg-provider-audit/meetings/002-2024-06-13.md @@ -0,0 +1,411 @@ +# Akash Network - Akash Network Provider Attributes Working Group-Meeting #2 + +## Agenda +- Welcome and Introduction +- Project Updates +- Demo of Benchmarking Tool +- High-Level Overview of Provider Auditing +- Next Steps and Planning + +## Meeting Details +- Date: Wednesday, June 13, 2024 +- Time: 10:00 AM PT (Pacific Time) +- [Recording](https://nergf5caumt4yjgrcif4bb6yxjrq6ftqaj52ge3l63ggj3qqlqaa.arweave.net/aSJi9ECjJ8wk0RILwIfYumMPFnACe6MTa_bMZO4QXAA) +- [Transcript](#transcript) + +## Participants +- Anil Murty +- Benjamin B +- Deathless +- Deval Patel +- Jigar Patel +- Maxime Beauchamp +- oïclid +- Rodri R +- rUqeRT +- Scott Carruthers +- Tyler Wright + +## Meeting Notes + +**Introduction:** +- Tyler Wright welcomed everyone and provided background on the group’s formation. +- Noted issues with previous meeting timings and the availability of meeting notes and transcripts post-meeting. + + + +**Demo of Benchmarking Tool:** +- Benjamin B provided an update and introduced the upcoming demo by Sebastian (rUqeRT). +- The benchmarking tool consists of four main parts: + 1. Indexer - Deploys to various providers. + 2. Benchmark - Runs the actual benchmarks. + 3. Database - Stores the data (using PostgreSQL). + 4. API - Gathers data from the database. +- Demo showcased the deployment process, running benchmarks, storing results, and accessing data via API. +- Example API call to fetch benchmark data for providers was demonstrated. + +**High-Level Overview of Provider Auditing:** +- **Scott Carruthers:** Requested an overview of the provider auditing process and its integration with Cloudmos. +- **rUqeRT:** Explained the use of API for accessing benchmark data and potential for expansion. +- **Benjamin B:** Discussed plans to integrate benchmark results directly on the blockchain and signing benchmarks on-chain. + +**Q&A Session:** +- **Anil Murty:** Asked about the benchmark comparison to a Raspberry Pi and its swappability. + - **rUqeRT:** Confirmed it's possible to swap out the baseline comparison and provided rationale for using Raspberry Pi as a familiar baseline. +- **Deval Patel:** Inquired about the frequency of running benchmarks, handling hardware changes, and displaying benchmark results on provider status pages. + - **Benjamin B:** Confirmed the capability to run benchmarks more frequently and discussed the potential for additional attributes. +- **Tyler Wright:** Clarified the goal of open-sourcing the auditing tools. + - **Benjamin B:** Affirmed the plan to open source the tools and allow others to run them independently. +- **Deval Patel:** Suggested integrating the benchmarking tool as an optional part of core platform engineering for continuous data capture. + - **Benjamin B:** Supported the idea for smaller benchmarks and uptime checks but highlighted challenges with more complex benchmarks like GPUs. + +**Next Steps and Planning:** +- **Benjamin B:** Acknowledged the need for partnerships between auditors and providers for cost-effective benchmarking. +- **KYC Integration:** + - Addressed the withdrawal of the KYC idea in favor of a decentralized trust system inspired by a hackathon submission. + - Suggested multiple trusted entities could sign off on KYC, improving the trust system. + - Discussed implementation strategies and the need for feedback from Scott regarding the best way to enable address-to-address trust sign-offs. +- **Console Integration:** + - Mentioned the plan to either send back funds to the community pool or extend the deadline for integration. + - Clarified the goal of integrating benchmarking results into Cloudmos and console for filtering and selection based on verified attributes and KYC status. +- **Uptime Indicator Clarification:** + - Benjamin B clarified the current uptime indicator in the provider dashboards is based on the provider's ability to interact with the service rather than lease uptime. +- **Future Directions:** + - Anil Murty suggested building a service that runs periodically to increase the number of variables available for users to select providers, considering both price and uptime history. +- **Next Session Planning:** + - **Tyler Wright:** Asked about the timeline for the next demo and narrowing down the direction moving forward. + - **Benjamin B:** Estimated a timeline of 14 to 20 days for the next demo. + - **Tyler Wright:** Agreed to follow up offline to finalize the schedule for the next session. + +**Closing Remarks:** +- Tyler Wright encouraged everyone to continue discussions in the working group for provider audit channel or the specific project tile. +- Benjamin B requested notes and transcript to be sent privately as an additional reference. +- Tyler Wright agreed to share the notes later in the day. + +## Action Items +- **Benjamin B:** Share [links](https://github.com/luxas/benchmark) to the actual benchmark being used in the WG provider channel on Discord. +- **Tyler Wright:** Ensure meeting notes and transcript are posted in the repo for this working group and shared privately with Benjamin B. +- **rUqeRT:** Explore and document how to swap benchmark baselines for future flexibility. +- **All Members:** Review the shared benchmark links and provide feedback or suggestions on potential improvements or additional benchmarks to consider. +- **Benjamin B and Deval Patel:** Discuss the integration of benchmarking tools into the core platform engineering for continuous data capture and notification. + +# **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 working group for provider audits. This group came out of a proposal that was put on Chain by piber Dev after conversations in Sig providers pi overdev and the pi 3 team puts together po a discussion that went on GitHub and then proposal that passed on chain for a automated auditing tool and then some other support work that was going into the cloud most indexer. There's been a couple of issues around timing for past meetings. But again, we're here to day to get update to all the work that has gone on since the inaugural meeting. I think which was in early April if anybody wants to track what's been going on again. There is a repo for this working group for provider Audits and you can see + +Tyler Wright: After this meeting the notes and transcripts in the video will be available. Just like the first meeting and just continue to track moving forward. With that said again, there's a couple of members of the community and this has been shared wider. But I do want to kick it over to Benjamin to give us an update. I think since the last update that they provided in on the engineering project board, but Benjamin, I'll kick it over to you and you feel free to share screen and we'll just go from there. + +Benjamin B: Thank you I don't have anything a concise yet. If you want me to make some notes off to this meeting I can write something there. But we have some few points. We want to share with you guys today. And the first one is actually with Sebastian who's going to present the demo of the benchmarking tool. + +Benjamin B: Are you ready for that supposed to? + +rUqeRT: Yeah. So person contacts into … + +Benjamin B: also + +rUqeRT: how the thing is structured. So it's comprised of four different parts like you got. An indexed as we call it. That's the one that actually deploys all of the to the different providers then when you have the actual Benchmark itself. Then we got the database to store everything in we decided on postgresql. and then just an API to that later gather all of the data from the database to let's see, where's the button for sharing screen? + +rUqeRT: Yeah. I found it. + +Tyler Wright: assuming that if you can see there's a ation, perfect + +rUqeRT: So can everyone see this? + +Benjamin B: Yes. + +Tyler Wright: Yes. + +rUqeRT: Yeah, so the main program that is deploying all of the benchmarks Brittany go. it doesn't And basic stuff to just set it up. + +rUqeRT: later finds all of the things it needs. to the provider we have currently on the run it against the testnet. since we've just been developing and don't want to pay all the money that is involved in starting up and taking down deployments all the time. So it sets up the deployment then it waits for the benchmarks to run and then just the file from the image. And close the deployment then we push it over to the database. It takes a while to run this thing. So here we have an example all the logs. And don't worry about the credentials there. They're all just for the sandbox environment. + +rUqeRT: So let's say it starts opinion. Yeah, so this is just the config needed to start it up. + +Tyler Wright: Sebastian while you're doing that. There's a question in the chat. What image is this deploying the benchmarking Scripts? + +rUqeRT: so we found a bench called Lucas Benchmark That we're using. can go into We made it sunlight modifications to it. + +Tyler Wright: Go ahead Benjamin. + +rUqeRT: So it's Benjamin pie better. Who's Has rear published the image. I could send you a link to the original benchmark. + +00:05:00 + +Anil Murty: Okay, I think I drop the links to the actual Benchmark that you're using in the WG provider channel. That will be great. + +rUqeRT: Yeah, could you fix that Benjamin? I'm doing this. + +Benjamin B: Yeah to the district Channel. + +Anil Murty: Yes, please. + +Benjamin B: Sure. + +rUqeRT: Yeah, so then that's all that waits for the Results come in and then this is the actual Benchmark that comes in. the summer part is The relative performance compared to a Raspberry Pi 1 model B. And this is just the actual raw data that it's performing against + +rUqeRT: so then we just push this into the database we got. can + +rUqeRT: show these are the different tables because to store the data. We got the actual Benchmark results. That's this first part. Yeah, overall the CPU RAM and real. this is then linked to these two which we call the bench specifications + +rUqeRT: and then we just have providers that are unique records that all of these benchmarks are linked to and we also have a run log just to keep track of everything and make sure that things are running. + +rUqeRT: Then on the API side once again, it's written in go and what you do is basically you run. This carol command. + +rUqeRT: Where you ask for the different providers? And you get back all of the benchmarks for that provider? + +rUqeRT: and that is basically + +rUqeRT: that is how this thing works in a nutshell. + +rUqeRT: Yeah, Benjamin. + +Benjamin B: Yeah, I just want to start here. That's the benchmarker we have right now. Could easily be swapped out for anything else. This is just so we can show something if there's demand to + +Benjamin B: to Benjamin's Market gpus to Benjamin smart networking anything else that could easily just be built. Basically. We just have to add more of the stls right now. We just made that single one, but we could just add more of them. + +Benjamin B: Try other things. Is there any questions for this demo? + +Anil Murty: Yeah. Yeah, this is great. Thank you for the demo. Could you dig a little bit deeper into the and I think you said this a little bit in class and I didn't catch it. But could you talk a little bit about the use you mentioned something about a Raspberry Pi and + +rUqeRT: Yeah, just There's some part of them. And Mark data is compared to how much better it is than a Raspberry model 1B + +rUqeRT: that is just something that is part of the benchmarket that we text. + +Anil Murty: got it. + +Anil Murty: Is that something that is? Swappable meaning can you replace who you're comparing against? + +rUqeRT: That should be possible. Yeah. It's just that this gives you a nice kind of Baseline. So, because most people have at some point interactive with a Raspberry Pi Wright. Then you get that goes, Because oftentimes benchmark scores are quite abstract. So you don't really know what the Baseline is. just This is my machine and it's better than that machine or worse. but if you have a concrete point to measure it against gets a little bit easier to think about + +rUqeRT: No, not yet. But Benjamin said Benchmark is quite easy to swap. Because it is just we change what image with deploy and we create some new models. + +00:10:00 + +Tyler Wright: Go ahead Scott. + +Scott Carruthers: so then if I don't want to distract from the current demo of benchmarking, so if We'd rather. Stick with that specific topic and then revisit this later. Let me know. I don't want to. be disruptive to this specific demo, but possibly just because it's been a period of time since we last met and there may be some people in the call that don't know these details at all. Is it possible also I wonder if this would be helpful for how everyone is conceptualizing this to provide a high level overview of the entire + +Scott Carruthers: accounts of what provider auditing from your tools is going to look like and so in other words, I appreciate that. We're currently looking at benchmarking statistics and that it's ready to a database. Is this the entirety of the Focus right now and I also saw some updates that you're not currently looking at the integration with Cloud most. So I'm just wondering you go out and you do this benchmarking against different providers you write to a database and then how does that holistically fit in? + +Scott Carruthers: and even how if we were going to include these benchmarks within provider attributes, how is that information getting into a providers attributes is the entire extent of the service at this point that we're just benchmarking writing it to a database and then it would be incumbent on other tools to bring that into it's + +rUqeRT: You would probably use the API that we could expand in whatever way you'd like. it has one endpoint to get this but you could easily expand upon it do some processing and expose that as well. but just as a starting point,… + +Scott Carruthers: okay. + +rUqeRT: you can ask for the provider from this API and then you get the benchmarks for the API for the provider + +Scott Carruthers: Okay, I see that has a hand raised as well. So might have some thoughts. + +Benjamin B: Yeah, I have some more things to speak on this matter. I think this was actually a perfect time to break up from the demo on this and what has any more questions. You can leave the screen share of Sebastian. But otherwise, what's the last I mentioned about the API? It's true for console usage for other usage. Just having the API would probably be enough. But we still have some more things. And that we're going to talk about today. And we're still planning to release it. So that it's not just their Internet. It's also the blockchain directly the other assigned by fields. We will speak a little bit more on this circuit that we see. Actually, I can take that right now. + +Benjamin B: So the idea is that when we have all the benchmarks and The Benchmark stls ready. And we just want to look at what is important for people to know is it up time? Is it CPU score? It's this and as soon as we have everything established here what people actually want to know. we can start signing people on chain for one address for everything that They want to know so if uptime being over 90% of this we can sign people that factor. If it's important to know if they have a CPU score I don't know over 500. We can sign people that as We don't have the demo for that today. but is that what you're asking? + +Benjamin B: Yeah, so we would use the API from the other service later on to do all this and before I speak on some other points like How we wanted to do kyc and other things we still have planned and I want to let them all and Anil speak. So please go ahead and de. + +00:15:00 + +Deval Patel: And so my question around is how frequently do you run this page practice and can we run more frequently than what we anticipate and I raised this question in discussions. sometimes what happens is that provider the hardware and change underneath changes right and that can change the Audited attributes in terms of CPUs and RAM and is there a way to and know that and how do we know those things on our side? + +Deval Patel: As a dashboard or we have the provided status page what we want to show those things there as well. So yeah my questions around that as well as we do + +Deval Patel: Right now in auditing the audit each attributes whatever the providers actually do are provide. + +Benjamin B: Yeah, I will start 50 second question whether or not we can do more attributes than this and… + +Deval Patel: So do you guys have that kind of capacity to do that? + +Benjamin B: the answer is yes. We just have to include some more benchmarkers like we mentioned this one is really simple,… + +Deval Patel: Let's say even the bandwidth they say what they have right like we manage and… + +Benjamin B: but this one can be more advanced or… + +Deval Patel: we sign that particular attributor as well. + +Benjamin B: we can just create new ones. of how often we run it. I think this depends not of the software but rather how we make the business model later on we can definitely make sure that anyone can run it and it can be triggered in other way, but it would depend how would we make this self-sustainable? We'll do it and create a business model where people pay for Benjamin smarts when we get to network to sponsor it what we do our own benchmarks. + +Benjamin B: so how much could we afford and that's a dependent north of that question so we could probably build so that regardless of who hosts the services. it's possible to choose how often you do it or if it fails if you want to retry And if you see any changes if you want to retry the benchmarks. + +Benjamin B: It's this what you're asking or was there anything else as well? + +Deval Patel: yeah, I think that's + +Tyler Wright: Jigar, did you ever end up? + +Benjamin B: awesome + +Benjamin B: yeah, I think again this depends some providers could probably try to have some sort of limitations in their bidding Scripts if they don't want to be done our benchmarks. That's kind of up to them. if they don't pay down benchmarks, and maybe we don't have super expensive benchmarks. Some providers have a minimum amount to USD per month for them to accept it. maybe we won't be able to reach maybe those on the opposite side of the spectrum where They have super expensive a million akt per per block. We couldn't pay for those either. Of course. But other than that the plan is to a bunch work everyone. Yes, but again, it depends a little of + +Benjamin B: at them go like how will the business model look like that kind of? makes a big difference was that's everything. + +Tyler Wright: I had a quick question. I think Deval has a question after that. I understand the idea around the business model. And I think that's something we talked about during the steering committee and trying to make sure this is self-sustainable. But as I understand that the main component was an open source automated auditor that anybody could use to audit a provider. Is that still the plan? Because again I think that's the main product requirement. So I just want to make sure I understand the business component, but it's very much till the plan to open sources so that any other cool client Etc can also use the provider audit and benchmarking tools. Is that correct? + +00:20:00 + +Benjamin B: This is correct. We want to make sure that anyone can run it themselves. If we can't host it ourselves. We're going to have everything open source for anyone to run. and the plan is that we were going to try to run it ourselves. But how long we can do that totally depends on other factors, but the main goal is the development of the open source tools. Yes. Please go ahead. + +Deval Patel: So to say same thing, and that goes with the Tyler side, open source. Let's say if you open source, and we really, make this part of a core platform engineering thing then and we have four I mean pods running let's say inventory part is running to notify the inventory and stuff like that can we not make part of this as an optional tool there? They can deploy this part as in + +Deval Patel: independent part and we basically capture the api's from that particular part and we showcase that to the providers are to the provided dashboard and provider status page? So, that way if we don't have to constantly ask for the beads rather than asking for bids like we can catch directly the data from the API. + +Benjamin B: Yeah, I think that's a good idea. So basically we're skipping the deploying on a cost process and the providers can just willingly allocate some of their resources to us like to always other and this is a good idea it kind of Doesn't make sense. If you want to scale it, if you want to test the gpus, I'm sure that a lot of providers don't want to rent out one entire GPU or least that for free to the auditor indefinitely. but for a smaller benchmarks and for uptime checks and Things checks everything like that this talk to make sense. and then + +Benjamin B: there's also the question of if you have this way of running it will provide us try to cheat it if they don't really know where it's coming from. and the last thing + +Benjamin B: was one more thing therefore Yeah, if we want to update the benchmarks to do something else. It also might be hard to ultimately update that but the idea is good and it could work for some of the benchmarks for sure. please + +Deval Patel: But I think what you can do with that part, is that whenever you want to run the Benchmark and frequency, You can grab the GPU at that point of time and then release it right and let's say all the gpus gets field right then we show the last status of the GPU what we had right stuff like that can be done and let's say even in your case, if you want to run a benchmark on a GPU and if the gpus are not available for that particular provider than what you're gonna do, right you will not be able to fetch that data at that point of time. + +Benjamin B: This total makes sense. It could also be so that something like this would be a triggered as soon as some resources gets Freedom that you want to Benchmark and The Benchmark could run. So if you're renting all the gpus at once and then someone closes at least that could be the trigger to say. Yeah, we're ready to Benchmark now. I don't think we're going to and keep this in the current scope, but we would definitely be happy to help out and discuss how to further build results because right now our system is built on a completely different way. But we could probably figure out some way where we create the proper Integrations to our systems. + +00:25:00 + +Benjamin B: Yeah, we did have some meetings in the past. I think one or two and this is a good thing to keep in mind for a future reference. Unfortunately, we can't really do anything about it now and I still think it's really valuable to do this via bidding. for making it cheaper. This will totally work. But then for this to work. You would have to need some Partnerships between the Auditors and the providers. If you're able to get that, it's not really certain whereas with bidding as long as the auditor wants to pay for the benchmarks or the provider wants to pay it or the networks. You can get it to work. Whereas the solution you're proposing. It will definitely work. But everyone would have to want to be involved. please go ahead and + +Benjamin B: Also, thanks for that to know I can definitely cover that right now and let me have to go through my points really quickly and we can have all the questions later because this was already on the agenda. I just didn't make it clear enough. First of all, I want to quickly mention that for the benchmarker while we are going to continue developing it and making it for a moment Posh. We are going to make withdrawal for This Milestone the kyc idea. + +Benjamin B: And that were going to work with. Different kyc providers but this is a very centralized way of doing it. If one kyc provider gets shot down. It really didn't work like all the development efforts will be done for in vain. and we had some internal discussion me and some other battle guards just a few days ago and we were talking about how to best to kyc not really kyc there. We were talking about a general trust system that we also want to help develop. Along with the kyc. + +Benjamin B: we still are discussing what the best way of doing. This is Basically, what we wanted to do is start. + +Benjamin B: Just like the services that we develop the open source tooling. + +Benjamin B: And where everyone will be able to run we want everyone to be able to be able to kc hold on or what? It's on in a different way. basically We want to have different people and if you trust maybe overclock clubs, you can trust their Senators if you trust us for our science, you can trust us and we would prefer to keep everything here on Shane similar to how we are going to sign by the attributes. This will be done for kyc. Preferably and other questions like Imagine if overclock Labs were to sign everyone. At one of their employees have met at a convention. + +00:30:00 + +Benjamin B: Maybe that's not a full proof way of trusting someone but it could definitely improve their trust if they're an Insider. Signed by overclock Labs. Maybe that's another thing that as you would trust. The list goes on. rotary sit important or ICU to cure handout I would prefer to keep the questions off through these points. If possible. + +Benjamin B: We are not going to develop something like that, but we were actually inspired by one of the hackathons submissions where they implemented a way to pay with credit cards to get akt. We saw how they did their kyc and we're probably going to create our kosc system in a different way or in a similar way rather and also have some other things that you can sign by to create this cross system that anyone can get involved in. we're also trying to get some value like there's some other people right now too getting involved in this and as soon as we have the best way of the creating and implementing the system and we're going to work with a simple to beta test this + +Benjamin B: the one thing that we were wondering when we had our discussion in the vanguard's chat is what could be the best way so that we can search of all of this. Or we're going to just create transactions with memos. We're going to create new transaction types or what would be the best I think this is a question maybe best. For Scott's to answer what we wanted to do here is we want any address to be able to sign other addresses? so that + +Benjamin B: We want to make it clear. what one person thinks of another address? I don't trust this one. I've met this personally real life. This is an Insider. you can have any amount of questions and answers in this memory transaction. And we also want to find it very easily when picking out the provider or + +Benjamin B: Or going to opposite way of which people do this person Go ahead Tyler. + +Benjamin B: Thank you that the last thing on the agenda. Is the console integration? We were thinking of just not doing any work and sending back to the funds to the community pool. but we can definitely keep discussion open to continue working or continue with some sort of integration. We're going to make the API public. Either if you want to continue on that and maybe we can send the funds to you in some way or if you want us to continue. We would probably want to increase the deadline if that wouldn't be a problem with everyone else here. + +Benjamin B: Yeah, but otherwise if nothing else like our original plan was just to send it back and not do anything, but we're open for ideas. Go ahead Scott. + +Scott Carruthers: It is just to make sure that everyone is on the same page. What exactly would they integration with Cloud most look like or where would there be? Value I would assume that it would be in Claude most implementation of recommended attributes. But could make sure we're on this same page with what it integration with cloudmus would entail. + +00:35:00 + +Benjamin B: And yes, just give me one second to open the proposal page. + +Benjamin B: Yeah, so the idea I start we could include filtering for that for cloudmaster now console. So if you wanted to find the + +Benjamin B: provider that has successfully shown that I'm capable being having this up time having these attributes verified or anything else you can just And quickly select what you need or if you need them to be from a certain region you can just filter that and to be able to only find those providers the assigned by the other API from us now. It's + +Benjamin B: Yeah, and I lost the thing that we want to have here as well is the kyc thing. So if you only want to now we have the non audited providers. Another very important thing is having a versus non-ky seed provider. I think this should be enough for this answer, please go ahead Anil. + +Anil Murty: Yeah, just going to the list of things contributions related benchmarking providers testing RPC know the tracking of time sort of these. It seems like what you've gotten so far and correct me if I'm wrong is. A portion of the benchmarking tool Is that correct? So track testing and no tracking of uptime. but + +Benjamin B: this is correct we have not done in a contributions to the indexer and we don't Have the API or Benchmark to work on the RPC quite Jets? and we also haven't done the + +Benjamin B: The filtering contribution on cloud nodes or console. and the rest while it's close, we actually have the last Point like half of that one right now what otherwise Pilates being worked on and It's quite close. We don't have it quite yet this meeting. No. I see some questions in the shortest world or some messages rather. And the kyc is not important for the benchmarking, but could be important. If you want to be able to trust their provider. It's a separate thing just like deathless basically if you want to run from a random Provider on the Internet or… + +Anil Murty: Got it. + +Benjamin B: if you want to run from a trusted company or person that kind of what we want to separate here. + +Anil Murty: but it makes sense and then really quick Tyler one other question is so think just in my head right? I think what I was thinking and maybe other people jump in if they don't agree with this, but today we have a uptime indicator in the provided dashboards when somebody goes to deploy something. There's a similar uptime history just when you go to the details of Provider that available on both the pre-order dashboard as well as a cloud most dashboard. I think ultimately what will be cool to do is to build something that adds to that. So meaning today more than when people try to pick a provider the primary things. They try to decide please is based on the location the price and the uptime indicator integral. That's it. So I think ultimately we want to add something that increases the number of variables that people get to pick from and so this would have to be + +Anil Murty: I think a service that runs periodically. + +00:40:00 + +Anil Murty: Ideally, it would be something that gets deployed onto each provider. And it has to be small enough that it doesn't consume a whole lot of resources. There is the problem of how to be deal with this on the GPU side because it's an all or nothing outside of gpus, I think it's the way I was thinking about this. So to answer your question about what you should do next. I feel like this is early enough that there isn't that much that has been done. that it makes sense to potentially go in a different direction with this, but that's just kind of I thinking on this + +Benjamin B: I think we're on the same page in kind of what we want to show on the console. I just want to make one thing clear here. Is that the uptime show unless something else has changed since I lost checked the uptime is not based of. How the leases are online or it's not based of that uptime. It's rather based of is the service running. They provider pulled or can the provider bid can they provider and do all of those things. Can you interact with the least shell All of those things is… + +Anil Murty: That's correct. + +Benjamin B: what is already being tracked and then something super small could just be tracked to get the actual uptime. I'm guessing. + +Anil Murty: That's great. + +Benjamin B: Yeah, and then for the other benchmarking things you mentioned. That makes sense. Yeah. + +Benjamin B: Did you have anything else or should we leave it to Tyler? + +Anil Murty: No, that is it. I think so. Overall. what I'm saying is I think if all you've gotten is one third of bullet number one, it makes sense for us to just revisit how we want to be doing. This periodic auditing, separate session and think about how you want to proceed from there. + +Benjamin B: All right, I'll leave it to you Tyler. + +Tyler Wright: Yeah, that was actually just my follow-up point because it seems like based upon these four General deliverables that are outlined. You're still fairly early in a number of these. So I was wondering to deval's point maybe obviously we're a little bit behind schedule. But do we have the ability to kind of direct how we're going to move forward from here to get these across the finish line so that they can be used by console and other members of the community. So it sounds like a near was talking about maybe doing another session where we can talk through some of these in a little bit more detail, but Benjamin, I just want to follow up with you about is that correct in terms of + +Tyler Wright: these four deliverables and percentage done probably across the board is less than 25% for each of them. And so again, we have some time to shape the direction move forward and determine From a Time standpoint if you can get all these things done or the order of operations and getting those things done. That's just sounds like we saw some time to make some decisions as a group and kind of just narrow down where we're going from here. is that fair to say? + +Benjamin B: No, I think. for most of this we're going to be able to finish them within the deadline, but then everything related to the + +Benjamin B: contributions to console and the cloud loss. We're not quite sure if we're going to have much time to dedicate that it's cool. We could look into increasing the deadline or we can return the community funds for those things. But everything else should be able to be done within a month, hopefully. + +Benjamin B: I'm open towards having more sessions to discussing more of these things. especially if you want to increase the deadline and do the Council integration in some other way But otherwise we haven't under control. + +Tyler Wright: Got I'm reading your chat. And can you speak to this a little bit more if you can? I'm just trying to + +00:45:00 + +Benjamin B: Yeah, I think especially for the council integration we can leave that. Just being a nullified but for the other things as I mentioned, we're developing it and should be done within the end of the month, even though we don't have the demos today to show everything. but those 100 hours For filtering and API usage of the clouds front end. We can definitely just return to the community pool. + +Tyler Wright: Okay, perfect. Thank you for that clarification and in terms of I guess implementation of the automation of the auditor. I know you said you don't have a demo today. Do you know have a timeline when we can set up another session to have to demo that and then get feedback from the community and then again narrow down getting that to production as quickly as possible. + +Benjamin B: I think the best thing here would be if we could shoot next time offline. So that we have the time to look at our schedules. Does that work for you guys? + +Tyler Wright: Do you have a range of when you think that demo will be ready? Just so I can map out some time for us to have a loose schedule and then we can narrow it down from there. We're thinking seven days from having a demo or more 14 days. + +Benjamin B: Selection what you think about roughly two weeks a few days before the deadline. It's + +rUqeRT: I'd say maybe. 14 20 days + +Benjamin B: at 14 to 20 days So the deadline is set the end of this month… + +rUqeRT: Yeah, something like that maybe. + +Benjamin B: if I'm not mistake 20 days. It's just a little bit into the next month. You start something that you guys are concerned with. + +Tyler Wright: slightly concerned but I think whatever gets us to the point where again we can share it get some feedback and then Get this share with a larger Community would be ideal, so I understand that you all have other things. So it is what it is. + +Benjamin B: Okay, so somewhere around there and 14 and 20 days and we should be able to meeting them. + +Tyler Wright: Come here follow up with you offline over the next a week or… + +Benjamin B: also + +Tyler Wright: I know we have 10 minutes left. Is there any other questions that anybody has about where we are and some of the next steps? + +Tyler Wright: All right. Benjamin I know you mentioned this at the top of the call, if you could drop in some notes when you get a chance on the product board in the issue that's created around this on the parking engineering board. That would be great. I'll make sure the notes transcript and recording are available as quickly as possible to share with other folks that maybe couldn't make it here today and then I will follow up with you over next seven to 14 days to get a better timeline of when we can get a demo so that folks on this call and in the community have enough time to plan and make sure that sound like a great next course of action. + +Benjamin B: Yeah, that sounds like a good plan. Please also send me the notes in a private deal. So I'm able to have that as an additional reference… + +Tyler Wright: Yes. + +Benjamin B: if I forgot anything. + +Tyler Wright: I'll do that later today when they're available. Thank you all for the demo. + +Benjamin B: Thank you so much. + +Tyler Wright: We'll follow up in the working group for provider audience Channel. If anybody has any questions again, feel free to reach out there or in the specific product that again, project tile that created around this that I'll drop in the chat again for folks. But again Benjamin Sebastian, Thank you all for all the questions and joining here today. I hope everyone has a great rest of the day. + +00:50:00 + +Benjamin B: Thank everyone. Bye. + +Scott Carruthers: Thanks guys. + +Tyler Wright: thank + +Jigar Patel: Thanks. + +Rodri R: that + +Deval Patel: Thank you guys. + +Meeting ended after 00:50:16 👋 + From 6d0870cdf1640b0228a6737767bcc2fb46d005be Mon Sep 17 00:00:00 2001 From: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Date: Sun, 7 Jul 2024 16:11:10 +0000 Subject: [PATCH 46/55] Create meeting notes for Sig-chain #17 (#611) * Create meeting notes for Sig-chain #17 Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> * Update 017-2024-06-11.md add transcript and recording link Signed-off-by: Drinkwater --------- Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Signed-off-by: Drinkwater Co-authored-by: Drinkwater --- sig-chain/meetings/017-2024-06-11.md | 146 +++++++++++++++++++++++++++ 1 file changed, 146 insertions(+) create mode 100644 sig-chain/meetings/017-2024-06-11.md diff --git a/sig-chain/meetings/017-2024-06-11.md b/sig-chain/meetings/017-2024-06-11.md new file mode 100644 index 00000000..9997acc5 --- /dev/null +++ b/sig-chain/meetings/017-2024-06-11.md @@ -0,0 +1,146 @@ +# Akash Network - Chain Special Interest Group (SIG) - Meeting #17 + +## Agenda +- Discussion on Cosmos SDK Upgrade +- Details on Akash Mainnet 12 Upgrade +- Discussion on Akash DAO and Overclock +- Tooling and Snapshots + +## Meeting Details +- Date: Tuesday, June 11th, 2024 +- Time: 08:00 AM PT (Pacific Time) +- [Recording](https://g6qelhldnaj52ry4xc56kge2wjrswqfgxrqs4iduth4cpqpndlfq.arweave.net/N6BFnWNoE91HHLi75RiasmMrQKa8YS4gdJn4J8HtGss) +- [Transcript](#transcript) + + +## Participants +- Artur Troian +- Dimokus +- Gabriel Li +- Julius Haus +- Marc +- Trigs +- Tyler Wright +- Zeke E + + +## Meeting Notes +- **Welcome and Introduction** + - Tyler Wright welcomed attendees and reviewed the purpose of the monthly meetings. + +- **Discussion on Cosmos SDK Upgrade** + - Recap of potential upgrade paths for Cosmos SDK (version 47 or potentially 50). + - The core team is conducting research on the next steps. + - Community members interested in the process are encouraged to participate in discussions and the next Sig Chain meeting. + +- **Details on Akash Mainnet 12 Upgrade** + - An upgrade is scheduled to occur in the next couple of hours. + - A countdown to the upgrade is available in the chat. + - The upgrade addresses an issue around fee grants. + - Proposal which resolves this issue, has passed and the upgrade is scheduled for block height 16708237. + - Attendees were invited to ask questions about the upcoming upgrade. + - [Documentation and resources](https://akash.network/docs/mainnet-12-upgrade/node-upgrade-guide/) were shared in the chat for validators. + +- **Upgrade Process Overview** + - Validators will upgrade first. + - Once the chain is stable and blocks are being made, RPC node upgrades by providers and exchanges will follow. + - Stability checks will be conducted post-upgrade. + +- **Support for Validators** + - Validators and insiders were advised to support others during and after the upgrade. + - The validators' channel on Discord will be closely monitored. + +- **Discussion on Akash DAO and Overclock** + - Marc was acknowledged for his contributions to recent discussions about Akash DAO. + - Ongoing conversations about the evolution of Overclock and the creation of Akash DAO were highlighted. + - Tyler emphasized the community-driven approach and the goal to move towards a more formalized DAO governance structure. + - Discussions about DAO governance continue to be active, with contributions welcomed from all community members. + - Tyler invited Artur and Gabriel to share any additional thoughts on the network upgrade before moving on. + +- **Tooling and Snapshots** + - Zeke discussed a new snapshot tool for Overclock, aimed at creating a more accessible sandbox environment. + - The community can expect pre- and post-upgrade snapshots and further tooling improvements in future meetings. + +- **Upcoming Meetings and Participation** + - Tyler encouraged attendees to mark their calendars for the next Sig Chain meeting. + - He emphasized the importance of community involvement in discussions about Cosmos SDK upgrades and Akash DAO. + +- **Closing Remarks** + - Tyler invited any final topics for discussion. + - He noted that Scott Carruthers, a key team member, is on vacation, so additional community support is needed. + - Tyler thanked attendees for their participation and encouraged them to stay engaged for the upcoming network upgrade. + - The meeting ended with a note of appreciation for everyone's contributions and a wish for a successful network upgrade. + - Tyler emphasized the importance of community support and participation. + - He looked forward to a successful network upgrade and continued discussions post-upgrade. + +## Action Items +- All Validators to upgrade to the new mainnet version at the specified block height. +- Insiders and Vanguards to support validators during and after the upgrade. +- Community Members to participate in ongoing discussions about [Akash DAO on GitHub](https://github.com/orgs/akash-network/discussions/601) and provide feedback. +- Zeke to Continue development and communication about the snapshot tool for Overclock. + +# **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 Sig chain monthly meeting The date is June 11th, 20 During the special interest group for the Akash blockchain that meets every month. Sometimes has been meeting every other month. The group mostly of validators and other just interested members of talk about everything from Network upgrades to Cosmos SDK previously. We've been talking about the upcoming upgrade to Cosmos SDK 47 from 45 where we are right now again, there's also some exploring around going to ask Cosmos SDK 50, but we've had plenty conversations about that during this meeting this week or this meeting. + +Tyler Wright: I know there's a planned upgrade happening now in the next couple of hours again, there's a countdown that you can all get access to drop in the chat for folks, but we're about an hour again 32 maybe a little bit less because this is an approximate timer, but we're a little bit out from Akash main net 12 again. There was a proposal that went on chain last week that helped for version. 0.36 that solves an issue around fee Grant. I'll drop down the chat for folks as well that proposal passed on today. Thank you everyone who voted and got themselves ready? And again with the proposal passing formally on chain yesterday. The upgrade is planned for on the block height that you see in chat 16708. + +Tyler Wright: Two three seven again. We're a little bit out from the upgrade right now. If anybody has any questions about the upgrade and how to upgrade again, feel free to drop them in the chat here today drop in the validators channel if you're a validator. You're not a validator if you are about there, but not about their Channel again. Feel free to ping me and I can give you that validator's role for those in the active set again. I've dropped the documentation in chat. and again people that are using Cosmic advisor should be ready to go and should just be waiting for the block height. Does anyone here have any specific questions about the Akash main net 12 upgrade that is happening sometime soon. + +Tyler Wright: did All right again, I know there's some insiders in vanguards currently. I was call if you see anybody in the validators channel that needs leading up to the upgrade or after the upgrade, Please support them. Again. The changes have been reviewed and are actively in sandbox right now. So there are teams that are working on it. So again much appreciate supporting all those that may need it. + +Tyler Wright: The goal is that again the validators were upgrade first, once the validators have upgraded and the chain is making blocks again. wait a couple minutes like we do check the stability of the network and then we'll have providers do an RPC node upgrade and then we'll just have again exchanges do the same. So that'll be the process as we move through the day. Anyone have any questions there? + +Tyler Wright: All right moving along with the agenda. I know that there's been a couple of conversations that have been happening in sick chain, as of recently, I believe Marc who's one person that's on this call today had actually been having some of those conversations. There's been a discussion that's had around basically in a cash down. I know that there's a member Of the overclock core team that has previously been talking about. + +00:05:00 + +Tyler Wright: + +Tyler Wright: The evolution of overclock and the creation of akashdow, so he's not currently here, but I know he would love to get involved and have them get involved in the GitHub discussion. He actually on paternity leave so that may be less than happening. I saw Archer just during this call. I want to manage his time a little bit Artur. We talked a little bit at the top of the call about the network upgrade Gabriel the documentation said the time with everybody there was no questions at that point. Do you have anything that you want to talk about in terms of network upgrade before we move on you can feel free to drop after we talked about Network upgrade Anyone have any questions for Artur? again, if anybody has any questions until they get closer to the network upgrade, feel free to drop those in the validator channel and Discord that channel will be closely monitored leading up to and directly following the network upgrade like we tend to do. + +Tyler Wright: I will chat out Zeke. + +Tyler Wright: because I think there's gonna be just a quick discussion around Akash Dow + +Tyler Wright: Also again Pikachu will have some staff shots,… + +Tyler Wright: which is an idea that's been floated by a member of the community. + +Tyler Wright: but Zeke has been working on an overclock related snapshot tool to have for again easier sandbox environment the number of easier upgrades and topics topics… + +Tyler Wright: So I just want to see if there's anything that you want to talk specifically about the main Network upgrade before we continue on with + +Tyler Wright: just like a topics An official overclock snapshots cool that can be used by The Wider community in addition to all the work that poked you and others do in providing snapshots. So again, there will be pre and post snapshots available. And then again look out for that tooling that will probably talk about in future meetings. + +Tyler Wright: + +Tyler Wright: Cool leading back to the conversation. We were just talking about around the cast Dow again. I want to make sure Mark did you want to talk about that very briefly about what you're looking or what you're thinking about. One thing. I will say is the idea as a Akash Community continues to grow and mature is that we move in the direction of a cost down. + +Tyler Wright: Really The Specialist groups groups and open group structure that we have here currently is a version of trying to be as transparent and trying to guide the community as much as possible. I think overclock is trying to be a steward in again trying to get as many Community contributions to everybody moving the similar Direction because there's so many things that need to get done but I do want to give you some time to talk briefly about a cost down your mind and I know that there is already been some comments, related to again, there's no smart contracts currently on So just want to let you speak high level if you're able to and then we can continue talking discussions. No worries, Marc different not able to talk. Either way, there is a active discussion that I've dropped in the chat again, feel free to get involved in that discussion. I will give my own viewpoints but again high level I think Dow governance is a great idea. low level, I think that + +Tyler Wright: we're overclock and really the cash Community is trying to accomplish this via The Specialist Group and working group structure in lieu of again, just formalizing a dab, but there's a number of ways for people to get involved to contribute to make the voices heard. It's very decentralized and Democratic and again as we continue to push forward, I think the idea to move in a general direction towards and Akash dab that does a little bit more management and governance over some of these things. If anybody else has any thoughts. Feel free to drop them in the discussion to give feedback to Marc but much appreciate the discussion started. + +Tyler Wright: one other thing I want to mention is again. I talked about a little bit about at the top of the call around Cosmos Upgrade to version 47 or potentially 50 again. There's been a lot of research and work from the core team into what's next there. There's so many features that again will be unlocked via customer SDK upgrade if anybody wants to get involved in that process I ask that + +00:10:00 + +Tyler Wright: your calendars for the next Sig chain meeting and look to get involved in the channel before that. There's already a couple of folks that have been working on other Cosmos projects that have already gone through this process. They're looking to get involved. And so we're looking again as a community looking to get all those people in the same room talk about these things maybe in a working group session or maybe just in the next 16 meeting. But again, if you want to be involved in that process, feel free to just make your voice heard and sick chain, and then we can take next steps there. + +Tyler Wright: does anyone else have any other topics that they wanted to discuss on this call here today? + +Tyler Wright: Again, I imagine this call will be a little bit shorter because folks should be if they're not already getting themselves ready for the network upgrade. But is anything else anybody wants to discuss here today? + +Tyler Wright: if not, thank you all for joining. I'll see many of you all in validators Channel. Sometimes shortly again. Feel free to reach out to me or support each other invalidated channel. If anybody needs help with anything that actually see a couple of comments that may need support the core teams a little bit short-handed this week. We have backup support and obviously a number of people are computer ready but as mentioned In Discord Scott Carruthers who usually is a very Hands-On with upgrades. It's been Hands-On leading up to upgrade and documentation testing all that kind of stuff, but it's currently on vacation. So if anybody else from vanguards insiders can with some help the community, that would be greatly appreciated. + +Tyler Wright: again, we're Again. This is a rough approximate countdown. So please stay close to your computers over the next couple hours knock on wood for another successful Network upgrade to Akash main net 12. And again, we'll continue to talk async about a number of things related to sick chain, but much appreciate everyone's time and energy today Mark much appreciate the discussion. I hope people get involved that discussion and look forward to a successful Network upgrade and then talking to you all post upgrade. But thank you all very much for voting and all the things that y'all do. + +Zeke E: I think everybody. + +Tyler Wright: Have a great day. talk y'all soon. + +Meeting ended after 00:13:04 👋 + + From c1dacfc7de79206acb9e298c7da2c520310ee3fc Mon Sep 17 00:00:00 2001 From: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Date: Sun, 7 Jul 2024 16:18:29 +0000 Subject: [PATCH 47/55] Create meeting notes for sig-chain #16 (#610) * Create meeting notes for sig-chain #16 Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> * Update 016-2024-05-21.md add transcript and recording link Signed-off-by: Drinkwater --------- Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Signed-off-by: Drinkwater Co-authored-by: Drinkwater --- sig-chain/meetings/016-2024-05-21.md | 132 +++++++++++++++++++++++++++ 1 file changed, 132 insertions(+) create mode 100644 sig-chain/meetings/016-2024-05-21.md diff --git a/sig-chain/meetings/016-2024-05-21.md b/sig-chain/meetings/016-2024-05-21.md new file mode 100644 index 00000000..8830f94d --- /dev/null +++ b/sig-chain/meetings/016-2024-05-21.md @@ -0,0 +1,132 @@ +# Akash Network - Chain Special Interest Group (SIG) - Meeting #16 + +## Agenda +- Introduction and overview of recent activities (Tyler Wright) +- Mainnet 11 upgrade discussion +- Validator engagement and communication channels +- Project tracking on GitHub +- Upcoming Cosmos SDK 47 upgrade (Artur Troian) +- Open floor for additional topics + +## Meeting Details + +- Date: Tuesday, May 21, 2024 +- Time: 08:00 AM PT (Pacific Time) +- [Recording](https://t7vun4ttnoelbnwkis4rf7eacagljw7a5tsobsuujmsiycgjdpna.arweave.net/n-tG8nNriLC2ykS5EvyAEAy02-Ds5ODKlEskjAjJG9o) +- [Transcript](#transcript) + + +## Participants +- Artur Troian +- B S +- Javier Su +- Maxime Beauchamp +- Rodri R +- Scott Carruthers +- Tyler Wright + +### Meeting Notes +- **Introduction and Overview:** + - Tyler Wright welcomed everyone to the 16th Sig Chain monthly meeting. + - Overview of the group's purpose: discussing validator operations and network upgrades for the Akash blockchain. + - Recent upgrade to Mainnet 11 was successful. + +- **Mainnet 11 Upgrade:** + - Shout out to all validators for a seamless upgrade process. + - Validators encouraged to stay engaged through Discord, GitHub, or email. + - Emphasis on responsiveness during upgrade processes. + +- **Validator Engagement and Communication Channels:** + - Validators can join a private Discord group for detailed communication. + - Tyler Wright is available to add validators to communication channels. + +- **Project Tracking on GitHub:** + - Projects board in the Akash Network organization tracks ongoing efforts. + - Roadmaps available for product and engineering, as well as community and marketing. + - Bounties and ongoing projects are visible for contributors. + +- **Upcoming Cosmos SDK 47 Upgrade:** + - Artur Troian discussed expedited governance proposals, allowing execution within 24 hours if consensus over 66% is reached. + - Realization that Cosmos SDK 47 already includes this feature led to the decision to migrate to SDK 47. + - Historical usage of a single codebase in the node group now being split into multiple parts (provider and Akash API). + - Migration plan includes: + - Migrating Akash API to the new Cosmos SDK. + - Ensuring proper conversion of data types and implementation of migration. + - Working on blockchain parts and starting testnet to assist clients. + - Significant breaking changes include state, APIs, transaction, and query messages. + - Target timeline: aiming for completion by end of summer, with actual upgrade likely in autumn. + - Preparations for future SDK 50 upgrades also discussed. + - Emphasis on providing reference designs in GoLang and TypeScript for developers. + +- **Additional Updates and Open Floor:** + - Tyler Wright emphasized that updates will continue to be made available via Discord and other channels. + - Opportunities for community involvement in testing will be available. + - Smaller upgrades planned for the end of the year will be on hold. + - Significant post-upgrade improvements expected. + - Encouragement to use the product and engineering roadmap for tracking and communication. + - Monthly meetings will continue, with the duration depending on the updates available. + - Final call for any additional topics or questions. + +## Action Items +1. **Tyler Wright:** + - Add any validators not currently in the Discord group to the validator role. + - Ensure all validators are added to the email list for updates. + +2. **Artur Troian:** + - Provide more specific details on the Cosmos SDK 47 upgrade. + - Outline the prep work and testing plans for the upcoming upgrade. + +# **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 Sig chain monthly meeting number 16. During the special interest group for the blockchain of a cost. This group gets together to talk all things related to validator operations things related to network upgrades, but everything related to the class blockchain believe since our last meeting. We've had a upgrade to main net 11. + +Tyler Wright: And so again, this has been a lot going on. Shout out to all the validators that made that upgrade very very seamless. + +Tyler Wright: If anybody here is a validator. There's a number of ways that you can stay engaged. If you do not want to be in Discord. You can feel free to message me or put a message in GitHub or email me and I can add you to an email list, but you have to make sure you stay up to date there. And then there's also a Discord group that has a validator role that's a private group specifically for validators where again, we manage all things related to network upgrades and just being a cash validator. So if anybody's not in those channels and needs to be again, feel free to reach out to me Tyler, I'll make sure that you're there. But again, thank you to all those that are very responsive leading up to upgrades with voting and also on upgrade day again, please upgrades have been happening faster and faster. So shout out the core team for all the prep that they do on getting those upgrades reading all testing and then again, shout out to the + +Tyler Wright: daters for all the work that they do during the upgrade So we're on Main Network 11 now and again just want to shout out all the work there. + +Tyler Wright: One thing that I believe will be talking about a little bit today. Everybody can go to GitHub. And then again on the projects board in the Akash Network organization. You can track what's going on and many of the efforts that are going on across the organization, especially on the product and Engineering roadmap. They're also is a roadmap for community and marketing you could also see bounties there. I think one thing that we will be talking about at length. Maybe not a link today, but we've already been talking about it for something chain meetings is around the upgrade to Cosmos sdk47 to be a big project that will be worked on by members of the core team throughout the next couple of months. I know what's 47 is up 4 So good number of unlocks that will happen after that. + +Tyler Wright: So again, it's an exciting time, but it is a massive upgrade. So there's a lot of prep work and then testing that will go into this. + +Tyler Wright: If there's anything else that anybody wants to talk about feel free to drop in and an item into the chat that we could talk about as an identity topic. But again, I kind of talked a little bit about that GitHub issue, but I will pass it over to Archer to see if there's anything more specifically he wants to talk about Cosmos sdk47 or anything else chain related. So Artur, I'll take it over to you. + +Artur Troian: Part of the blockchain and a couple of things for example expedited governance proposals. That you would like to have which allows us to execute governance proposal is saying 24 hours if we reach consensus over 66% and sometimes that's quite important, especially for parameters or emergency upgrades and we sort of implementing that and then realize that causes seven does already have it. and we just sort of postponed it for later on and Decided pretty much quite a few weeks ago that we going to move to + +00:05:00 + +Artur Troian: execute migration to sdk47 another decision that sort of maybe to actually directed us towards the upgrade is improvements on the Akash as the SDK + +Artur Troian: historically we used to use All the code base in the nodegroupon that we started splitting it off into multiple Parts. One of them is a provider in the second one is a cash API actually Pi is still a little bit on my side which we are cleaning up quite quickly. + +Artur Troian: The plan is going to be as following because the sdk47 is quite a breaking change and that includes not only state but as well as the apis, I mean the transaction and the query messages. So what we are going to do is we're going to call for Akash SDK and cautious decade very first part will meet my great Akashi API. To the new cosmosis Decay and make sure that all of the data types are properly converted and we have migration implemented. Once we do that, we will start working on the blockchain parts, which is not and as soon as we have blockchain part up and running we will be starting testnet with that will allow us to help clients. + +Artur Troian: That using Cosmos I actually Pi quite significantly and that we have quite a few of them. To pass and start implementing migration on their side that process will be going for probably month or so. So the amount of things you bring into cosmosis Decay is pretty much whatever we have as the business Decay 47 brings itself. That's for example, each store will have our own parameter storage. And as I mentioned earlier, it's going to proposals and IBC upgrade. For example, you will be migrating ABC to V7. Maybe at the time of a great it will be V8. So it's still being discussed. And that will allow us also to prepare for future. + +Artur Troian: SDK 50 I don't know if you're gonna executed this year, but maybe next one. So in terms of timeline, I think this stage we targeting towards and all the summer. and it was like, that's a lot of time but the change itself is massive and once again, Cost of downtime is quite significant. So we have to be really careful on what we are doing and number two is since probably this new year the Akash API is being used by other developers. So we have to Enough time to perform migration. So that means we have to give them reference design for both languages and in golang as well as typescript. And give them a time to test all of the changes. + +Artur Troian: So most likely actual upgrade will be in Autumn time, but I'm not saying that out loud. I'm just trying to give some sort of prospective that time of actual upgrade and that Varian can be quite significant. so this is then probably the biggest massive change for the next few months. and all of the other things related to the blockchain itself, it will be postponent until we get cosmosis Upgrade done and that includes packet forward in and there were some other changes. I don't recall unfortunately, but I believe there are in the sports. So I think that covers it. Anybody have any questions? + +Tyler Wright: Thank you Artur again. As time goes on there will be more updates made available via Discord and other channels. There'll be a number of opportunities for testing Again by The Core team and maybe even bringing in some folks for the community to potentially help with some testing and number of different environments. So again, this is be very much a focus of the core team and we'll make sure that folks in the community are involved when needed and up to date on all things happening there. But again as Artur mentioned some of the other smaller upgrades that we have planned at the end of the year will now be on hold while we just handle this bigger upgrade. We'll have significant post upgrade Improvement to the network usage Etc. + +00:10:00 + +Tyler Wright: Does anyone have any questions about the upgrade again, feel free to drop any questions or comments or thoughts inside of the specific ticket product and Engineering roadmap? That's the best way to kind of track this and again, there will be a number of other smaller issues that I'm sure will be added to the product and Engineering roadmap as well as potential announcements. Where when available. + +Tyler Wright: Are there any other topics of discussion that anybody wants to just talk about related to the blockchain or related to validated on Akash? + +Tyler Wright: If not, then we can certainly end this a little bit earlier again as details become more available. We will keep this a monthly meeting if there's no real updates we can have it be we are in 10 to 15 minutes like we had today if there is a need for folks to talk about some of the things happening as we're testing Costless sdk47 and we can take this time as well. So again, we'll continue to keep this as a monthly meeting to just check in and all things related to the upgrade especially as it is such a massive upgrade again will be the focus of the core engineering team open next few months. So we'll just track it with the state chain meeting on a monthly basis. + +Tyler Wright: All if there's nothing else that anybody wants to talk about again, feel free to ask any questions to have about being in a cash validator and the validator channel and Discord again, if anybody wants me updates via email and they're validator feel free to reach out to me and I'll add you to an email list where we let Val there is know about boats that they should be participating in upgrades Etc. + +Scott Carruthers: Thanks, everyone. + +Tyler Wright: But again much appreciated everyone's participation much appreciate the core team for all to do and again being present here to let the community know what they're working on and we'll continue to talk online. Thank you all very much. Hope everyone has a great rest of their day. + +Tyler Wright: but + +Meeting ended after 00:13:34 👋 + From 7a32a5e85698ee29be651a9b3f949c8039eac788 Mon Sep 17 00:00:00 2001 From: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Date: Sun, 7 Jul 2024 16:22:33 +0000 Subject: [PATCH 48/55] Create meeting notes for Sig-design #17 (#604) * Create meeting notes for Sig-design #17 Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> * Update 017-2024-06-12.md add transcript and recording link Signed-off-by: Drinkwater --------- Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Signed-off-by: Drinkwater Co-authored-by: Drinkwater --- sig-design/meetings/017-2024-06-12.md | 378 ++++++++++++++++++++++++++ 1 file changed, 378 insertions(+) create mode 100644 sig-design/meetings/017-2024-06-12.md diff --git a/sig-design/meetings/017-2024-06-12.md b/sig-design/meetings/017-2024-06-12.md new file mode 100644 index 00000000..52c67956 --- /dev/null +++ b/sig-design/meetings/017-2024-06-12.md @@ -0,0 +1,378 @@ +# Akash Network - Design Special Interest Group (SIG) - Meeting #17 + +## Agenda +- Welcome and Introduction +- Updates from Denis Lelic +- Follow-up from Akash Accelerate +- Need for Additional Design Support +- Website Overhaul and New Features +- Content Contributions +- Project Management and Deliverables +- Open Discussion and Q&A + +## Meeting details +- Date: Wednesday, June 12, 2024 +- Time: 08:00 AM PT (Pacific Time) +- [Recording](https://ifqou2kkf6gqtmise2kelunxe2wc4xrcssgptlx3oh25flm7tcea.arweave.net/QWDqaUovjQmxEiaURdG3JqwuXiKUjPmu-3H10q2fmIg) +- [Transcript](#transcript) + +## Participants +- Denis Lelic +- Gabriel ReyesOrdeix +- Tyler Wright +- Zach Horn + +## Meeting Notes + +**Welcome and Introduction:** +- Tyler Wright welcomed attendees to the monthly SIG design meeting. +- Overview of the meeting’s focus on visual communications, swag, merch design, and marketing materials. + +**Updates from Denis Lelic:** +- Denis provided updates on current design projects. +- Emphasis on the need for additional design support. +- Discussion of efforts around the Akash Accelerate event. + +**Follow-up from Akash Accelerate:** +- Introduction of new t-shirts, stickers, backpacks, and other swag at the event. +- Plans to create a dedicated swag page on the Akash website for better representation and launch planning. + +**Need for Additional Design Support:** +- Tyler highlighted the need for community support to assist Denis. +- Encouragement for community members to get involved in various design and marketing activities. + +**Website Overhaul and New Features:** +- Denis discussed plans to redesign the providers page for a unified experience. +- Proposal to create a unified pricing page to compare Akash costs with other providers. +- Pending redesign of the Community page due to time constraints. +- Recap of work done for Akash Accelerate, including venue branding, giveaways, and a landing page. +- Post-event focus on editing and rolling out video clips from the event sessions. +- Acknowledgment of Gabriel’s portfolio and his potential contributions to various design tasks. +- Mention of product design work related to the merger between Cloudmos and Console, aiming for a seamless user experience with new features in the pipeline. + +**Content Contributions:** +- Zach joined the meeting and discussed content contributions. +- Emphasis on technical blogs, use cases, and case studies. +- Encouragement for community members to contribute written content via the community contributions page or the website. +- Discussion about the brand guide availability for Gabriel and other contributors, with Denis mentioning the basic brand guide available in the footer section of the website. + +**Project Management and Deliverables:** +- Gabriel inquired about the list of deliverables and the organizational structure for project management. +- Denis clarified that needs vary based on events and other requirements, such as graphics for social media and swag for upcoming events like ETHCC in Brussels. +- Tyler explained the process: specific items are documented in GitHub issues, discussed in Discord, and assigned based on availability and deadlines. +- The structure is flexible, accommodating quick turnarounds and allowing for creative contributions. +- Emphasis on a collaborative approach with contributors discussing and deciding on tasks in a democratic manner. + +**Open Discussion and Q&A:** +- Gabriel expressed understanding and readiness to work within the provided structure. +- Tyler and Denis reiterated the importance of GitHub and Discord for project coordination. +- Encouragement for Gabriel to get involved and help scale contributions as the community grows. +- Gabriel clarified his expertise in branding and editorial design, stating he is less interested in web design and video. +- Tyler suggested Gabriel take a look at the marketing repo for ideas and contribute his own suggestions. + +**Closing Remarks:** +- Denis invited Gabriel to connect on Discord for further discussion and to set up a separate meeting if needed. +- Tyler emphasized the importance of community involvement and encouraged Gabriel to bring in any friends or colleagues who might be interested in contributing to Akash. + +### Action Items +**Denis Lelic:** +- Follow up on creating a dedicated swag page on the Akash website. +- Coordinate with Gabriel on upcoming design tasks and clarify any additional questions on Discord. +- Ensure the updated brand guide is accessible to contributors. + +**Tyler Wright:** +- Document specific marketing and design needs in GitHub issues for better project management. + +**Gabriel ReyesOrdeix:** +- Connect with Denis on Discord and set up a meeting if needed. +- Review the marketing repo and contribute suggestions for new projects. +- Consider inviting other potential contributors to join the community efforts. + +# **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 Sig design monthly meeting for It's June 12 2024 during the special interest group for design the Akash Community gets together to discuss all things related to Visual Communications swag Merc design marketing materials Etc. There's been a number of people that have helped support specific swag ideas and brought those live to the store. There's people that have helped with marketing materials that have gone on in real life events and Beyond Denis here is the head of design at overclock labs and has been leading this group and has been again doing a fair amount of design up to this point with support from the community. + +Tyler Wright: Denis has a number of items that he's been working on that. I think he'll share or at least get some progress on today as well as follow-up from Acosta accelerate where there was a number of marketing materials and swagged I think has been shown during steering committee and other meetings. + +Tyler Wright: One action item that I want to bring up is again with denis' time only having 24 hours like the rest of us and there's a number of things that Denis works on across marketing across design as well as across product design for console and other products there was an effort to try to trap Denis in a closet and make him work 24 hours a day his family got in the way and so there's a desire to get some additional support from the community, paid in akt to help with marketing materials, whether it be again in swag social media assets other marketing materials in real life events and digital events. So again, if anybody has any desire to get more involved in the cash and has the background and graphic design or Visual Communications, whether it be animation again, a graphic design or elsewhere there are brand. + +Tyler Wright: Isability we use these meetings as well as conversations in Discord to hopefully bring on some more folks that can help out with some of those Endeavors. So I just wanted to drop that line out there. I think put a message in chat and Gabriel who's on the calls already… + +Denis Lelic: Thanks, Tyler,… + +Tyler Wright: but summoned by Robert Delray Shadow Robert Delray,… + +Denis Lelic: welcome to Sikh design from my and… + +Tyler Wright: but again looking for folks that want to get more involved and… + +Denis Lelic: as well, so just to cover a couple of touch points from our previous sessions. + +Tyler Wright: earn some akt to help with marketing materials and other design deliverables in support of Denis and… + +Denis Lelic: So as Tyler mentioned we've Tried to overhaul the whole Akash swag. + +Tyler Wright: other members of the community. Without further Ado. I'll kick it over to Dennis to see… + +Denis Lelic: So if anyone was at Akash accelerated in Austin through three weeks ago. + +Tyler Wright: if there's anything that he wants to discuss or if there's any question and then we can talk about any questions beyond that. So Denis feel free to take it away. + +Denis Lelic: You probably saw a bunch of new t-shirts stickers. + +Denis Lelic: Backpacks, so there was plenty of new items. and of course one of the + +Denis Lelic: Touchpoints we want to overhaul. Is this what SWAG and the swag + +Denis Lelic: page on the network website. So at the moment we only have a button which leads to our Akash shop, but I feel we could do a dedicated page just to have a better representation of all the swag items out there and all the swag items. We're planning to Launch. So yeah. + +Denis Lelic: Touched the website a little bit. So there's a plenty of new. Issues created there. So besides and having a dedicated swag page. I think we have to rethink and redesign the providers page. We talked about it during the website meetings, and there's another one happening tomorrow so we can continue that because discussion there. so just basically have a unified. providers page where we could talk about all the stats about it like the network capacity and so on because also list all the providers there. + +00:05:00 + +Denis Lelic: all of these Are already alive we just have to make sure. We bring them together. So it's kind of unified experience for providers and it's going to be easier to grasp all this data and information for the users again. Another thing we could rethink and redesign would be the pricing page. Now we have pricing in two different locations one was just like a dedicated pricing page where you can calculate the cost of bringing your deployments to a cash. But then later on we added GPU pricing. So I was just thinking having one unified page where users could easily switch and compare. + +Denis Lelic: between different providers meaning if you want to calculate your cost and compare them to AVS Google Microsoft and there should be an easy switch where users could just have a look at the gpus and GPU listings and GPU price. pricing + +Denis Lelic: one additional point on the website would be the Community page. That's something Tyler has a brought up multiple times, but unfortunately we didn't add time to tackle this issue. So + +Denis Lelic: But hopefully soon trademark + +Denis Lelic: Yeah, there was plenty of work done. and the last month especially around accelerate so there was plenty of Touch points we had to create From the venue branding to all the giveaways. We had a landing page on the website as well. And now after the accelerate we wrapped it up. which means we have to On the business side. Everyone has to take care of the lead and on the marketing side and the design side we have to take care of mostly videos. So the whole stream was about seven hours long, so we chopped it up bring it down to four hours and now we're rolling out all the clips. + +Denis Lelic: For each session. So anyone who's interested can just have a look at one presentation or panel or Q&A and so on. so + +Denis Lelic: Yeah as Tyler mentioned. I just want to welcome Gabriel again for being here. Thanks for sharing your portfolio. So as Tyler mentioned we were looking at bringing someone who's gonna help us out in creating. different kind of Graphics basically everything design related that comes in so It's not going to be like one alley. design, there's gonna be plenty of different kind of designs coming, so from video to social media Graphics blog graphics infographics. + +Denis Lelic: So what else do we have? We have website, of course as I've mentioned so and again. as Tyler mentioned I'm planning to work a bit more on the product side as most of community members are aware a merger happened in the background between Cloud modes and console and we had a new addition of Prater apps which we're just gonna try to unify. all that product experience to make it feel like + +Denis Lelic: seamless and hopefully easy to use for our users next to that. There's plenty of new features in the pipeline like credit card payments adding new templates or redefining the flow of the whole app. So there's going to be plenty of work there. + +00:10:00 + +Denis Lelic: from a very high level. I think I covered pretty much everything. we're planning to do and some of the stuff we did in the past month. + +Denis Lelic: Ty do you want to add anything here? I know Zach's not around but maybe something on the content side because usually on sick design we cover content as well. + +Tyler Wright: Yeah, I know that there's a couple of blogs that have gone out recently. There are a number of teams that are developing content materials like written content. And I know that Zach is always looking for Content contributions. So folks that confined specific ways to contribute to writing blogs. I think it's less so about high level what a cost does. I think there's been a number of pieces to this point that cover that but really some deep dies and how people are using Akash technical Again contributions whether it be to the docs or just again pieces that showcase different use cases case studies all that kind of stuff if anybody wants to contribute in that way. There's a number of ways to contribute both on the community contributions page as well as more formally on the website. + +Tyler Wright: Denis one thing I want to see and I was looking for very briefly. But do you have a brand guide that's available that we can drop in the chat for Gabriel + +Denis Lelic: Yeah, there's one in the footer section. It's called Brandon press and there's download logo kit since the last brand guide with updated couple of things. So. In this logo kit, there's just basic information included. + +Denis Lelic: which all everyone who's willing to work on Akash as a brand there's basic information there basically logo set and I think it's enough for everyone to get started and totally depends. what the task is looking from designer, but + +Denis Lelic: I think it's a good starting point. + +Tyler Wright: Excellent, and then I would also reference a number of the touch points that you can see on social media really like even some of the banners that you see for the special interest groups in working groups about, tight faces and other elements of style that are used across the brand. So if anybody has any questions Gabriel, if you have any specific questions again, feel free to drop those in sick design or you can ping Denis and I Denis I privately but don't feel like anything's off limits and… + +Denis Lelic: Yeah, yeah, that's true. I mean as I said in this page here,… + +Tyler Wright: questions. I know Dennis is done a great job of establishing and continuing to develop a brand around Akash,… + +Denis Lelic: there's basing basic components of Akash as a brand… + +Tyler Wright: I think is professional very very clean and… + +Denis Lelic: but there's some wiggle room where designers can have Some creative canvas to express themselves,… + +Tyler Wright: fairly modern. But again, there is still at the part of brand elements and Denis correct me from wrong, but there is still room and… + +Denis Lelic: but of course they need to consider. + +Tyler Wright: Holiday for elements of style from different designers. + +Denis Lelic: a communicated Akash as a brand and… + +Tyler Wright: That's Again Play up some of the structure that's already in the brand but They're still creative elements,… + +Tyler Wright: + +Denis Lelic: in a cohesive manner,… + +Denis Lelic: so we're just trying to make sure that + +Tyler Wright: and in coordination with a lot of structure as well. + +Denis Lelic: there's a red line between all different touch points that are produced from our side Red Line meaning. I'm not sure if that's used in English. + +00:15:00 + +Denis Lelic: I helped me out. What was the way is that something that's been used in English like red line meaning all the touch points are kind of connecting and unified brand experience. Maybe that's the better expression. yeah. + +Tyler Wright: I don't know the red line expression that context but I like it, but I think it makes sense a lot of sense. + +Denis Lelic: So yeah. Yeah. yeah doesn't matter who works on what item it at the end of the day should somehow feel connected and that it's coming from + +Denis Lelic: one brand Yeah,… + +Tyler Wright: Yeah. + +Denis Lelic: get Gabriel. Go ahead. + +Gabriel ReyesOrdeix: Okay, so I do have a question. Do you have a list of needs slash deliverables that you're looking for or is this effort is it left to whatever the designer wants to contribute with? Zach I from… + +Denis Lelic: Yeah on. + +Gabriel ReyesOrdeix: what I'm hearing there are a lot of needs in even different disciplines video or video editing Graphic Signs Stills social media content Etc. So can you clarify a little bit on what exactly your meeting contributions with? + +Denis Lelic: Yeah on the marketing side everything. Happens sometimes quite fast. So totally depends on the events and stuff that's happening. So let's say there's ease CC happening in one month in Brussels, which means we would need graphics. for social media, And graphics for side events that are happening at the same time and along with that. We always have to think about what team is going to bring with them in what kind of merch so what kind of Swag are they bringing with them and we have to design all of those and + +Denis Lelic: the end of or the video part it's not that specific per event, but it's more like + +Denis Lelic: editing a video for a guide and stuff like that. So We don't usually record all the events in only happened at our own event for Akash accelerate. but it's always great if one person can handle. Just multiple disciplines at the same time. So we don't have to switch between two three people. + +Tyler Wright: Gabriel this for also from a structural standpoint. What we'll do a better job of is putting all the issues as with specific and specs in marketing and GitHub. It's like a public place to put those in will drop those inside of Discord so we can talk about them at a high level of Discord, but really probably be best to drop information inside the GitHub issues if you're familiar with that little structure and again, But the idea is as Denis mentioned there might be specific items that are needed for specific events, like leading up into Brussels. There's number side events and we need + +Tyler Wright: Six different Graphics leading up to and then we'll put a speck in there. We'll drop it in there. We'll see if you have time and then we'll put a deadline around it how long it'll take you and we just move as quickly as possible because sometimes these have a quick turnaround. There might be other times where you're like, hey, I think that we should do some more videos for this kind of audience and then you can just create or hey, I saw some really cool swag. I want to add some items to the Akash store that I know some people would like really like to wear so it's a combination of deliverables that might be time-based versus more ended creative ideas that you can explore. + +Gabriel ReyesOrdeix: That's what I was referring to. maybe a better way of The question I asked is what does the organizational structure looks like with regards to project management? Because I'm starting in zero today today is zero for me. So I want to know how does the team contributors looks like and who gets how quick a turnaround are projects so that helps I'll look into the GitHub. + +00:20:00 + +Tyler Wright: Yeah, and again, there's been an Howie it has to store historically happened is there's been a number of contributors that have been involved at various points depending on their availability with their day job or if they're in between gigs that have had more time and a lot of those conversations have happened in Discord as we look to get more contributions. The idea is again, there will be a contribution might come from overclock Labs might come from a conversation from the Community member might be something you evaluate. The first order of business is to create an issue inside of + +Tyler Wright: GitHub we'll talk about a live if there's not enough time then we'll drop that issue and Discord and we could talk about an async and be like, hey, I think it's really important. This is why I think it's really important or hey, this is something that's needed and there's a specific spec around it. Once that's spec is determined. What if it's coming from overclock Labs. There will be a deadline on it. And if that's something that you can meet you can say hey, this is something that I will look like I like to take and then once you take it then we'll just coordinate with you. either async or we can set up some time to talk a lot to just make sure that everything is line in the right format in the right,… + +Denis Lelic: Yeah a good point. if you're like coming from an agency or… + +Tyler Wright: sizing Etc to be delivered and… + +Denis Lelic: something like design agency or marketing agency the structure here is a bit different. + +Tyler Wright: then again, if you don't want to take it there might be another Community member say,… + +Denis Lelic: So there's a project manager would usually reach out and… + +Tyler Wright: hey, I have the time and availability to take it and we'll kind of work as Democratic group to kind of determine… + +Denis Lelic: brief you about things and here are the deliverables and… + +Tyler Wright: who should take… + +Denis Lelic: here's the deadline so pretty much everything works through GitHub is Tyler mentioned so It's a bit bit of a different structure than usually is in the design world. + +Tyler Wright: what if we get to the point where there's 15 people trying to go for the same issue, which is a good problem to have then we'll determine a little bit better structure. But right now we've had One person here, maybe two or three people here that are contributed one-off thing. + +Gabriel ReyesOrdeix: Yeah, I understand. + +Tyler Wright: So this is something that we're looking to grow and… + +Gabriel ReyesOrdeix: I am I've worked in the sign agencies,… + +Tyler Wright: evolve and you can help us do that as it continues to scale with more creative contributors. + +Gabriel ReyesOrdeix: but I am not coming from design agency. So I have worked quite a bit within the crypto industry. So I'm familiar with GitHub and Discord as the platforms for project requests. So I just wanted to understand the way this particular. project Works Thank you for clarifying. + +Denis Lelic: Hey Zach. Thanks for joining. So we just covered a couple of design related things anything you would want to talk about on the content side. + +Zach Horn: Hey, yeah, so sorry guys. I was jumping over from another meeting. No, there's nothing pressing on content nice to meet you. I caught the cut the tail end of the conversation. nothing. + +Gabriel ReyesOrdeix: likewise + +Zach Horn: Nothing pressing on my side anything else Denis from a Content design standpoint? + +Denis Lelic: I think not really. Yeah, pretty much everything is covered. So + +Denis Lelic: we only had a couple of contributions in the previous month or a month before that. On the blog, but hopefully we'll see more in the future. + +Zach Horn: most definitely + +Denis Lelic: Okay, cool. Gabriel you can. + +Denis Lelic: D and me or send a friend request on Discord so we can have a conversation there. We can also set up a separate meeting if you want to talk about anything. Just unrelated. + +Gabriel ReyesOrdeix: first thing that will do right away. + +Denis Lelic: Okay. cool + +Tyler Wright: And I'll start to drop a couple of ideas in the marketing repo in the issues for some things that I know have been requested by different members to overclock Labs team on behalf of the community just to have a criteria. But again Gabriel as you start to do a little bit auditing exploring before connecting more with Denis, feel free to suggest anything and add an issues there one other element and again, this will be more of a collective but we'll lean on Denis just because he's done a great job of developing the visual components of the brand is from a creative Direction standpoint again, we try to have guidelines, but I think we'll try to be as Democratic with maybe Denis having the final Hammer if you got to the point of whether we want to move forward with something that might be the only caveat that might be a little bit different than traditional. + +00:25:00 + +Tyler Wright: Like agencies or organizations, but that's how we'll try to do it. all of us are Critical thinkers and receptive to constructive feedback. So it should be fairly open and constructive if designs maybe aren't quite where they need to be yet, and we can just talk about that as a group but maybe have Denis have the final say during these Sig design meetings. + +Denis Lelic: Yeah. I agree. I mean everyone can. bring + +Denis Lelic: their own ideas, but we're going to try try to kind of keep it I know Zach is sometimes the brand Shepherd as well so I know he's gonna Have some thoughts there as well, which are welcome. Of course. + +Zach Horn: It seems like every week I get a new title. I got in content King. What was this one brand Shepherd my business. + +Denis Lelic: brand Shepherd + +Zach Horn: I'm gonna need extended length the business cards. + +Denis Lelic: You can just have a whole set with just different titles. + +Zach Horn: But that's Yeah, we'll do a mix, random for each person. + +Tyler Wright: All right, you just like a bookmark. It just like is a long long-ass card. she can't even want. + +Zach Horn: It's funny. + +Denis Lelic: a flyer basically + +Tyler Wright: exactly Gabriel and + +Zach Horn: Have arrived you have your own custom. Collateral for your business card flyers and… + +Denis Lelic: or just a Roll-Up. + +Zach Horn: there's and all that. + +Zach Horn: exactly + +Tyler Wright: This is scroll. He just unwinds it. + +Denis Lelic: Okay. + +Zach Horn: very cool + +Denis Lelic: we covered everything for today I think so it might be time to wrap it up. So Gabriel, I'll talk to you on Discord and thanks again for joining and I'll see you in a month or if you're interested and web design. And website so our cars.network there's another meaning a meeting happening tomorrow. So feel free to join. + +Tyler Wright: Yeah, I was going to say. Okay. + +Gabriel ReyesOrdeix: I am not interested in that. + +Gabriel ReyesOrdeix: Honestly not and maybe I can provide a little bit of background but the areas in which I feel more comfortable with are branding and editorial but web design and video either or animation. So I'm sorry I can't help with that. + +Denis Lelic: Okay. + +Gabriel ReyesOrdeix: But I'm eager to contribute. I really believe in Akash as a project. And as a designer, I want to put whatever I can to help so I'm eager to contribute. + +Denis Lelic: Good to know and thanks for clarifying. I think it's To know what people are interested in and of course. It's good. You're pursuing that direction. + +Gabriel ReyesOrdeix: Yeah, good. + +Tyler Wright: Absolutely. + +Gabriel ReyesOrdeix: You can take a look at my portfolio that's not everything I've done but it's a little bit of how my stuff looks like. But thank you. + +Denis Lelic: cool + +Gabriel ReyesOrdeix: Thank you for the opportunity. + +Tyler Wright: No, thank you Gabriel. + +Denis Lelic: first major + +Tyler Wright: And again, you have friends that are doing content to to write or to do video. I know we already put Robert to work as well. He's a great member of the Akash community and he does a number of things. So if you have anybody else that is top of mind that you can think of that would be a great addition to helping with content. Feel free to send them to me or just send them to Sig design and we can just get to know them a little bit more and connect with them. + +00:30:00 + +Gabriel ReyesOrdeix: I will always think about it. + +Denis Lelic: Cool Thanks for joining again, and we'll see each other soon. + +Gabriel ReyesOrdeix: Okay. Bye. + +Denis Lelic: Bye. Thank you. + +Zach Horn: to address + +Tyler Wright: maybe but + +Meeting ended after 00:30:36 👋 + From f51088bcf555b69b31fa8a826f212a8c7b2045a1 Mon Sep 17 00:00:00 2001 From: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Date: Sun, 7 Jul 2024 16:23:57 +0000 Subject: [PATCH 49/55] Create meeting notes for Sig-providers #17 (#615) * Create meeting notes for Sig-providers #17 Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> * Update 017-2024-05-22.md add transcript chore: add recording link Signed-off-by: Drinkwater * Update 017-2024-05-22.md add transcript and recording linl Signed-off-by: Drinkwater --------- Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Signed-off-by: Drinkwater Co-authored-by: Drinkwater --- sig-providers/meetings/017-2024-05-22.md | 210 +++++++++++++++++++++++ 1 file changed, 210 insertions(+) create mode 100644 sig-providers/meetings/017-2024-05-22.md diff --git a/sig-providers/meetings/017-2024-05-22.md b/sig-providers/meetings/017-2024-05-22.md new file mode 100644 index 00000000..2b33df77 --- /dev/null +++ b/sig-providers/meetings/017-2024-05-22.md @@ -0,0 +1,210 @@ +# Akash Network - Providers Special Interest Group (SIG) - Meeting #17 + +## Agenda +- Update on Provider Features +- Praetor Team Updates +- Discussion on Updated Bid Scripts +- Provider Upgrades to Version 6.2 +- Special Interest Group Participation +- Presentation on Provider Build Path + +## Meeting Details +- Date: Wednesday, May 22, 2024 +- Time: 08:00 AM PT (Pacific Time) +- [Recording](https://a6qm5qjrbhmjkmbmsfldmoqzdspsaxypsgfq26wfw6ysnw3xp7cq.arweave.net/B6DOwTEJ2JUwLJFWNjoZHJ8gXw-Riw16xbexJtt3f8U) +- [Transcript](#transcript) + +## Participants +- Andrew Hare +- Anil Murty +- Deathless +- Deval Patel +- Jigar Patel +- Scott Carruthers +- Tyler Wright + +## Meeting notes + +**Introduction:** +- Tyler Wright welcomed everyone to the providers' monthly meeting number 17. + +**Update on Provider Features:** +- Discussion on provider features following the open-sourcing of Praetor. +- Jigar and Deval gave updates on their work post-acquisition. +- Recent hackathon focused on provider contributions. + +**Praetor Team Updates:** +- Repositories are now open source. +- Recent hackathon encouraged provider side contributions. +- Update on the progress and next steps. + +**Discussion on Updated Bid Scripts:** +- Scott Carruthers working on [updated bid scripts](https://akashengineers.xyz/provider-build-scripts/) in Go. +- Lively discussion on the impact of these scripts on providers. +- Encouragement to follow updates and participate in discussions. + +**Provider Upgrades to Version 6.2:** +- Recent upgrade to provider version 6.2. +- Importance of upgrading to the latest version. +- Instructions and support available for the upgrade process. + +**Special Interest Group Participation:** +- Encouragement to get more involved in specific projects. +- Opportunities to participate in special interest group meetings. + +**Presentation on Provider Build Path:** +- Scott Carruthers has been working on simplifying and speeding up provider builds on Akash. +- Presentation and internal documentation shared for feedback and testing. +- Active community engagement for feedback on the provider build path. + +**Additional Updates:** +- Discussion around the new bid scripts. +- Two new provider horizon upgrades to version 6.1 and 6.2 rolled out. +- Testing K8s multi-node products for improved provider stability. +- Encouragement to contribute to open-source repositories. + +**Hackathon:** +- Hackathon ended on May 17th with a focus on provider tooling and monitoring. +- Judging of projects is ongoing, with more information to be released soon. + +**Provider Reliability and Reputation:** +- Discussion on reputation and provider reliability, initially on Discord and now on [GitHub](https://github.com/orgs/akash-network/discussions/576). +- Encouragement for community involvement in ongoing discussions. + +**Praetor Strategy:** +- [Document](https://github.com/akash-network/community/blob/main/product-strategy/praetor-akash-provider-console-strategy.md) outlining the next steps for the open-source Praetor tooling shared for community review and feedback. + +**Cosmos SDK Upgrade:** +- Ongoing upgrade to Cosmos SDK 47 from 45. +- Significant impact on the codebase requiring extensive testing. +- Community involvement in testing will be sought as the upgrade progresses. + +**Other Announcements:** +- Andrey is on vacation, so please reach out to other team members if needed. +- Akash Accelerate event on May 28th in Austin, with presentations on various parts of the Akash ecosystem, including the provider. + +## Action Items +- Scott Carruthers Continue to work on the provider build path and gather feedback from the community. +- Jigar Patel and Deval to support testing and contributions to open-source repositories. +- Tyler Wright to ensure the [product and engineering roadmap](https://github.com/orgs/akash-network/projects/5/views/1) is shared and accessible. +- Review of Praetor cloud provider console strategy document and provide feedback. +- All Attendees prepare for testing the new Cosmos SDK and provide feedback when requested. + +# **Transcript** + +_This editable transcript was computer generated and might contain errors. People can also change the text after it was created._ + +Tyler Wright: Just all right, welcome everybody to providers monthly meeting number 16. + +Tyler Wright: During these providers on the network. We talked about provider features at the last meeting. We got an update because it was the first meeting after Craig tour was open source, and the pray to our team was acquired by Jigarette and Deval gate a little update. We talked a bit about next steps as we continue to move forward. I will give jigar into all a bit time to give an updates and all the things that they've been working on because I know again the repos are now open source, and there was a recent hackathon where again folks just starting to think about ways to contribute on the provider side. + +Tyler Wright: Also at the last meeting there was a lively discussion around the updated bid scripts. I know that Scott who's here on the call has been working on updated bid scripts and changing the structures. So, I believe it's in go and it's just Lively discussion about how that affect providers. So again a great participation from the group on that last call. Since the last meeting, there's been I believe a couple of Provider upgrades. I believe now. We're on provider versus 6.2 again. If you're not on that most recent version, please look for messages in the provider announcements Channel. And if you have any questions on how to upgrade again, feel free to reach out to somebody or just follow the Specific Instructions that have been outlined by Scott and Andre. + +Tyler Wright: Before I kick it over to the prior team to give it update or really the overclock team now, but to give an update on all things related to Predator. I do want to see Scott if there's anything that you wanted to talk about the bitage and script that the follow-up the last call. + +Tyler Wright: Don't kill obliged. I know that you might be moving around. + +Tyler Wright: excellent + +Tyler Wright: many of these issues are trapped in the product and Engineering roadmap, which I've attached or I've shared in the chat and I'll make sure it's in the notes as well. If anybody has any questions or comments or wants to get more involved in any specific projects again, feel free to drop a comment obviously take this time during the special interest grouper provider and other special interest group meetings to get more involved live one other thing that I want to call out and I believe This is something that jigarette and Deval have been working in tandem along with their prayer related efforts is around Scott has been working with members of the community but has been working for the last couple of months on making it easier for and faster or individuals to build providers on a cash. He's been sharing do + +00:05:00 + +Tyler Wright: presentation which I'll drop in + +Tyler Wright: I'll drop in the chapter folks. That's very Alpha and just like some core engineering Internal Documentation. It's been used again. He's been connecting with members of the community to test out this provider build path get feedback from the community get feedback on documentation. This is something that's being actively worked on by the core team and I know that jigargar and Deval had been supporting with testing again, they'll talk a little bit about it a little bit later… + +Jigar Patel: I sure so to start from the last meeting… + +Tyler Wright: but there is a ticket that Andre Jigger and Deval have all been testing against… + +Jigar Patel: since then. + +Tyler Wright: which I've dropped in the chat right there. + +Jigar Patel: We open source all of our repository in the GitHub. + +Tyler Wright: So again across the provider, there's been a recent upgrade to provider version 6.2 that's been tested and… + +Jigar Patel: So now all the new features… + +Tyler Wright: number of providers have been upgraded to that version again,… + +Jigar Patel: if anyone wants to contribute, it's welcome there. + +Tyler Wright: there was discussion around the big scripts and… + +Jigar Patel: So that's a great thing. And since then we also added two new provider Horizon upgrade the one and… + +Tyler Wright: others at Go version. That is Scott mentioned this quote complete and there will be more information. + +Tyler Wright: Made a relative to the community coming soon and… + +Jigar Patel: Sorry the 6.1 and… + +Tyler Wright: then again something that's been a focus of the core engineering team has been provider stability and… + +Jigar Patel: 6.2 that's also rolled out on the public. + +Tyler Wright: making the provider build process more efficient and… + +Jigar Patel: Currently. We are testing k3 a visibility of the q3s multinode into products and… + +Tyler Wright: that is in testing phases right now with members of the core team as well as a community to get that over the line. So look out for updates there soon. + +Jigar Patel: environment. So once that's done put those into + +Tyler Wright: Jigar, I know I might have stolen a little bit of Thunder from all the updates that you have,… + +Jigar Patel: Basically change the way… + +Tyler Wright: but I want to pass the floor off to you… + +Jigar Patel: how okay3s or… + +Tyler Wright: because you usually do a great job of giving updates and… + +Jigar Patel: sorry all the multinode provider build happens in Predator from K. + +Tyler Wright: all things related to the greater provider cooling. So I just want to see… + +Jigar Patel: Its to k3s because we are already using k3s in a single node. + +Tyler Wright: if there's anything that she wanted to update the community on here today. + +Jigar Patel: That I understand. + +Tyler Wright: Thank you very much again. I believe there's three repos that I've been added by the prior team that now all open source. I dropped in they're all in the constant Network organization. I believe one's p back in prayer front end and then the last one I believe is a greater security. So again as jigar just mentioned if anybody wants to get feel free to chime in and Discord channel for ecosystem Predator again, you can start getting involved and see looking around and specific issues that might be in those repo or feel free to again start a conversation and providers and we'll make sure that the necessary people are tagged and we can continue conversations between meetings there. + +Tyler Wright: thank you very much for that update. + +Tyler Wright: Again, I just want to mention on the hackathon just ended May 17th. There was a track related to provider Cooling and monitoring tooling. So again, there's some projects that are being judged right now. So look out for some more information as time goes on if any of those continue to mature, but again, there was a number of great entries across the hackathon. So again really excited for all those that participated to all of that participated. Thank you to all those that helped people that were to participating in the hackathon and looked out for more information there coming very very soon. + +00:10:00 + +Tyler Wright: Russia all Other than that, we always go through the + +Tyler Wright: Discussions and see if there's any discussions happening. I know that there was a discussion happening around reputation and provide a reliability. It started off in Discord and it ended up in GitHub discussion. I know this is something that's been previously discussed a while back. We didn't move forward with at that time, but I would just ask if anybody has any thoughts opinions here again, feel free to get involved in this discussion. I know Anil has already done. thank you Anil for doing so but if anybody else wants to get involved or again. Please please get involved in those discussions and just get feedback. Just keep those conversations going. + +Tyler Wright: Her anil's response. I do want to drop this in the chat here today. We talked about this at the last meeting, but there is a document that's been put together by jigarette Duvall Anil and the core team around the pratera cloud provider console strategy next steps. If anybody wants to understand at the highest level kind of what the core team is thinking about in terms of next steps for the open source Trader cooling. Please feel free to look at this document. And then again, we can have discussions about this either async in Discord or if anybody has any questions we can have that as an agenda item as we continue to move forward month over month. I'm sure they'll be a lot of progress and updates coming very soon there. + +Tyler Wright: Before I continue on does anyone have any questions about anything that's been discussed thus far. + +Tyler Wright: Does anyone have any additional agenda topics that they want to talk about here today, but haven't added them to the agenda yet. + +Tyler Wright: One thing I will note just because it's been something that it's come up in the past. I know that Andre who's usually on these calls and is usually supporting a number of providers along with Scott Jigger Deval many others in the community. He's taking some personal time. He's on vacation. So if you see less availability from Andy recently, I know in the past people thought, was he sick with the injured? No, because how responsive he is. He's just taking some personal time. So he should be back in a couple weeks or so. I'm more available with more availability. It does have his computer on with him, but I would ask that folks that usually connect with them again. Feel free to reach out to myself and Insider or somebody else in the community over the next a week or so. Andy's on vacation. + +Tyler Wright: those are all of the topics that I wanted to cover for this week against sometimes you have longer meetings where there's a number of folks that are asking specific questions and this month and I might just be a quick update and then we can continue to talk async. Before I let y'all go is there any other topics of discussion that anybody wants to discuss here today? + +00:15:00 + +Tyler Wright: all if not, then I'll let you all go today. I'll make the recording and notes available shortly. And then again if anybody has any questions or comments between meetings, please feel free to drop those in Discord and we will look to get those solved as previously mentioned in the Sig chain meeting yesterday. One of the bigger items for members of the core engineering team is around the continued upgrade to 47 from 45 where we are right now again, that's going to touch all parts of the code base. So on the provider side again, there will be a fair amount of testing over next couple of months. So if anybody, I know some folks on this call certainly have helped with testing the past. So again, we'll be looking to reach out to you as we get closer to testing the new Cosmos SDK and some of the features. + +Tyler Wright: So again, thank you to all those that help out that testing but look out for that coming soon as well. + +Tyler Wright: All Y'all have a great rest of the day again. If you have any questions for me, please feel free to reach out but we will close out this meeting for this month. And then again, I'll see you all next month Akash accelerate is happening a week from yesterday, May 28th. So again, please feel free to join us live in Austin. There will be a number of presentation. I'm sure related to all parts of the Acosta ecosystem including the provider. But again, really looking forward to collaborating and connecting between meetings. And again, if anybody has any questions or comments about anything provider related, please feel free to drop them in the state provider Discord Channel. Hope everyone has a great rest of their day. Thank you very much for joining. We'll talk soon. + +Tyler Wright: Goodbye. + +Meeting ended after 00:15:30 👋 + From 8d521f131a27e7df6462ec7edb845699b04a02c5 Mon Sep 17 00:00:00 2001 From: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Date: Sun, 7 Jul 2024 16:27:22 +0000 Subject: [PATCH 50/55] Create meeting notes for sig-community #16 (#603) * Create meeting notes for sig-community #16 Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> * Update 016-2024-06-11.md update formatting, add transcript, and recording link Signed-off-by: Drinkwater --------- Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Signed-off-by: Drinkwater Co-authored-by: Drinkwater --- sig-community/meetings/016-2024-06-11.md | 243 +++++++++++++++++++++++ 1 file changed, 243 insertions(+) create mode 100644 sig-community/meetings/016-2024-06-11.md diff --git a/sig-community/meetings/016-2024-06-11.md b/sig-community/meetings/016-2024-06-11.md new file mode 100644 index 00000000..c6cc43c8 --- /dev/null +++ b/sig-community/meetings/016-2024-06-11.md @@ -0,0 +1,243 @@ +# Akash Network - Community Special Interest Group (SIG) - Meeting #16 + +## Agenda +- Overview and updates on community initiatives. +- Discussion on recent events: Akash Accelerate and Consensus 2024. +- Q3 events proposal and planning, including ETHCC. +- GitHub discussions and community involvement. +- Hackathon updates and future planning. +- Developer onboarding program update. + +## Meeting Details +- Date: Tuesday, June 11, 2024 +- Time: 11:00 AM PT (Pacific Time) +- [Recording](https://nl4ez6metcnz3sdkdgvxj6b2opl74ywekhhfqfj3smj6m4in3e2a.arweave.net/avhM-YSYm53IahmrdPg6c9f-YsRRzlgVO5MT5nEN2TQ) +- [Transcript](#Transcript) + +## Participants + +- Amanda Keay +- Andrew Gnatyuk +- Joao Luna +- Robert Del Rey +- Tyler Wright +- Zeke E + +## Meeting Notes +**Introduction and Welcome:** +- Tyler Wright welcomed all attendees and introduced the meeting in the absence of Adam Wozni, who is on paternity leave. +- The focus was on discussing community efforts, including hackathons, events, and other initiatives. +- Attendees were encouraged to add agenda items in the chat if they had specific topics to discuss. +- Tyler noted the detailed discussions during the steering committee about Akash Accelerate and Consensus 2024. + +**Q3 Events Proposal:** +- Tyler highlighted that the Q3 events proposal would soon be up for discussion. +- Several events for Q3 and Q4 2024 have been agreed upon by the SIG Community. +- Participants were encouraged to share event ideas in Discord, either in the SIG Community channel or the working group for events 2024. + +**ETHCC Presence:** +- Amanda Keay provided updates on the planned participation in ETHCC in Brussels. +- Akash will have a significant presence, participating in nine separate events. +- Akash will host three of their own events, with Greg and Neil speaking at eight other events. +- Amanda is waiting to hear if Greg's talk was accepted for the main ETHCC conference. +- Akash did not get a sponsorship for the main event but will actively participate by visiting booths and engaging with attendees. +- The goal is to have Akash represented in at least two locations simultaneously during the event period, starting from July 7th. +- Amanda offered to share a document detailing all planned side events. + +**Insider Support for Events:** +- Tyler mentioned that some insiders have applied to support the events, and the finalization of this group is pending. +- Even those without tickets to ETHCC might be able to support side events and programming. +- Announcements will be made in the Insiders channel soon. + +**SIG Economics Announcement:** +- Tyler announced that SIG Economics, usually held the first week of the month, will take place next Tuesday, June 18th. +- Encouraged participation from key stakeholders and community members for discussions on AKT and related topics. + +**GitHub Discussions and Community Involvement:** +- Tyler encouraged attendees to participate in ongoing discussions on GitHub. +- Shout out to Roger and others for their active participation and valuable questions. +- Discussions include topics related to Sig chain cost reduction and an upcoming hackathon opportunity in India. +- Members of the Overclock Labs team and Insiders are coordinating to represent Akash at the hackathon in India. +- Follow-up conversations from the Akash hackathon were also mentioned, with winners announced on Dora Hacks. + +**Hackathon Updates and Future Planning:** +- Tyler and Robert Del Rey discussed the recent hackathon and future opportunities, including a quadratic funding round proposed by Dora Hacks. +- Overclock Labs aims to support smaller hackathons leading up to larger events in the fall/winter. +- Discussion about using community pool funds for hackathons and spreading awareness among builders globally. +- Planning for the next major hackathon should start before late August, with a committee to be formed during the next SIG Community monthly meeting. +- Suggestions for hackathon tracks are encouraged and can be shared in the hackathon channel on Discord. + +**Developer Onboarding Program Update:** +- Tyler gave a shout out to Robert and Piber for their work on the developer onboarding program. +- The wrap-up for the program was shared, and no new missions are currently being opened until discussions are complete. +- Collaborations with other projects like Galaxy 2 are in progress, and future missions might be seen through this collaboration. +- Robert confirmed that most rewards have been paid, with the remaining claims closing by Friday, June 14th. + +**Closing Remarks** +- Attendees were encouraged to drop track suggestions in the SIG Community or Hackathon channels in Discord for discussion. +- Tyler mentioned postponing some of the Zealy meetings for June and highlighted upcoming working group sessions and SIG Economics discussions. +- The next SIG Community call might be adjusted to accommodate those attending Brussels events. + +## Action Items +- All Participants to Suggest additional events for Q3 and Q4 2024 in Discord, either in the SIG Community channel or the working group for events 2024. +- Amanda Keay and Team to coordinate the inclusion of any new event suggestions into the Q3 proposal. +- Tyler Wright to Facilitate ongoing discussions about the Q3 events proposal and ensure all contributions are considered. +- Robert Del Rey to finalize pending reward claims for the developer onboarding program by June 14th. +- Tyler Wright to follow up with hackathon winners via email to discuss next steps and future involvement. +- Tyler Wright and Amanda Keay to finalize the group of insiders supporting the events in Brussels. +- All Participants encourage to start thinking about potential tracks for the next hackathon and drop suggestions in the SIG Community or Hackathon channels. + +# **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 Sig Community on June 11 2024 again this special interest group for Community needs to discuss all things related to Akash Community efforts. I think there's discussions about insiders here around the hackathons around events and a number of other community facing initiatives. If anybody has any agenda items that they want to discuss here, feel free to drop them in the chat. Usually this meeting is led by Adam wozni head of community for overclock labs and really + +Tyler Wright: one of the main Community Builders and the cash ecosystem for some time program of a number of other programs. He is currently on paternity leave while he is out myself and the events lead at overclock Labs. Amanda will do our best to try to fill in give updates on all things events hackathons and all of things going on in the community side again, if anybody has any specific items that they want to discuss here today. Feel free to drop them in the agenda. the last meeting there was a lot of discussion leading up into Akash accelerate and consensus 2024 again, there's been a lot that's gone on. + +Tyler Wright: At those events and obviously you talked in great detail about it during the steering committee. Is there anything that anybody wants to discuss again? That hasn't been discussed on the Akash accelerate or the consensus 2024 said + +Tyler Wright: One thing to look out for and I know there's been a lot of planning in this sig Community around it is Q3 events proposal is going to go up for discussion soon. I know there's been a number of events that have been agreed upon here as a part of the Sig Community for Q3 and Q fuel Q4 2024. And then I'm sure there's the discussions beyond that as well. + +Tyler Wright: again, look out for a discussion happening soon. And please feel free to get involved if there's any events in Q3 or Q4 that have not been talked about that folks want to add potentially to listen and discuss in Discord again, feel free to go into Discord and either in sick Community or the working group for events 2024 to drop in any of those events. I know there's a number of opportunities all over the world that people bring to our cash. So feel free to drop anything that makes sense for there to be representation whether by insiders members of overclock Labs core team or combination of both feel free to drop those in State Community or working group for events. + +Tyler Wright: Cool again, as a part of that Q3 events proposal. I know that there is a lot going on as it pertains to ECC and… + +Amanda Keay: Yeah, thanks Tyler to say we're having a big presence is an understatement. + +Tyler Wright: all the events going on in Brussels during that week the neglers some of those number of other things going on. + +Amanda Keay: I feel we are participating in nine separate events. + +Tyler Wright: I do want to pass it over to Amanda to talk about all the work that's been going on there. + +Amanda Keay: We are hosting three of our own and Greg between Greg and… + +Tyler Wright: I know that there is a huge presence expected in Brussels. + +Amanda Keay: a Neil speaking at the events. + +Tyler Wright: So I'll hand over to Amanda to talk a little bit about what's going on. + +Amanda Keay: We have eight separate events that we're going to be speaking at that's what I should say still waiting to hear on whether or not Greg. + +Amanda Keay: And his talk was accepted for the main CC conference. We will also be walking around that we didn't get a sponsorship for the main event, but we'll be hitting up everyone's booths and stuff at the main conference as well. So I think we're in a good place right now. Our goal is to be everywhere all at once. So at any given time I think a cautious represented in at least two locations. So most of us are gonna be landing on the sixth and then events start ramping up on July 7th. So if anyone is interested in seeing all of the events that we're planning on being at during that day side events wise, I'm happy to share a little document that I put together just pretty much + +00:05:00 + +Tyler Wright: Thank you very much. Does anyone have any questions they want to talk about here right now in terms of anything. Amanda just talked about. + +Tyler Wright: One thing that I will add just for transparency sake is I think Amanda might have alluded to us but there's a number of insiders or not a number but there's some insiders that have applied to support all of these events. We are looking to finalize that group in the next very soon. I know that's waiting on me. And I know Amanda's pushing his harsh as possibly can to get this finalized. One thing that I am trying to see because there are so many events if there's a possibility even if some folks may not be able to go to ECC because a tickets only allocated for certain amount of tickets, but if folks can be there to support in other ways all the side events and programming so again, look for announcements in the Insiders channel for all those that have applied and look to finalize that very shortly following the same process at + +Tyler Wright: Us thank you very much Amanda for that update. Again, look out for that Q3 events proposal that will be going on upper discussion and people can give feedback make sure that everyone's aligned and then go on change shortly after that. + +Tyler Wright: I see Andrew in the crowd here today. I do want to shout out Sig economics, which will be happening next week. I know it normally happens the first week of the month that I know there's a number of topics that are worth discussing. I've seen some of that stuff in general chat as well as in the Sig economics Channel, again want to make sure that number of key stakeholders both in the community and some folks in overclock Labs tea team are able to join and have some Lively discussions there. So I'm doing a Shameless plug for Sig economics, which is moves from again the first week of the month to it'll be happening next week. The date is + +Tyler Wright: Next Tuesday the 18th. So I just want to get put that on people's radar and I'm hoping that Andrew can be there like you normally is to participate in some of those discussions as we continue to move forward things on the akt side as well. + +Tyler Wright: No problem. + +Tyler Wright: Again, there's a couple other things that I specifically wanted to cover. There's a couple of conversations that have been happening around and GitHub discussions. Again, if anybody here on this call can continue to get involved in those discussions. Shout out to Roger and number of other people the community that are, asking great questions and getting some feedback from people that would be great to continue to push and that direction. There's a number of + +Tyler Wright: Conversations we talked about wondering Sig chain around the cost down, but I would love for folks to get involved in that. I know something that Adam is looking to push forward with in the future as the cost Community continues to grow and evolve. But again, there's a number of conversations there on the hackathon side. There is a hack of opportunity in India around with some college students that they've talked about, wanting some Akash representation there. So please get involved in that conversation again members of the overclock lab team has been talking because it is a small amount that they're looking for besides just the presence there and there is a member of the Insiders that currently a couple folks in the Insiders that are currently in India region. And so again, it's a potentially small output + +00:10:00 + +Tyler Wright: that there is a hackathon funds from the community pool available for potentially a number of builders that again could be exposed to Akash with members of the Insiders that can represent Akash there live and in person, so that's something that live in GitHub right now. + +Tyler Wright: As well as I believe that there was some follow-up conversation from the Akash hackathon and obviously those winners have been chosen you can go to Dora hacks to learn more. I'll drop that in the chat for anybody that wants to follow up are about to results. I know that one thing that I want to do is from overclock side is just get to get together with all the people that won or place with any track. So again, I will look to follow up with people via email just to see what their next steps are with various hackathon projects and see how they can get more involved. So again, that's something that I will be doing with some other folks. + +Robert Del Rey: Thanks, and you're human, right? + +Tyler Wright: Robert I know that you are very Hands-On in the hackathon and… + +Robert Del Rey: awesome So here we go. Yes, as you say yesterday. I spoke with George from Dora hacks we discuss. + +Tyler Wright: provided a great summation follow up after talking to Joy from the door hacks team. + +Robert Del Rey: how the hackathon went on their side And yeah. + +Tyler Wright: Did you want to talk about anything here today, or do you want to save it for just online conversation again? + +Robert Del Rey: What I want to give you some context about is that they suggested us a cash. + +Tyler Wright: Feel free to Take the mic and… + +Robert Del Rey: To do a quadratic funding round. + +Tyler Wright: talk a little bit if you so desire. + +Robert Del Rey: That's something that thorax has going on and they asked us… + +Tyler Wright: Yes, I can. + +Robert Del Rey: if you want to do that. We just gotta let them know and yeah. + +Robert Del Rey: basically with the quadratic funding it's like a second chance or hackathon participants to submit their reels and + +Tyler Wright: Thank you very much, again For me, there were a number of great projects and great entries that came through the hackathon. I think Adam mentioned this during steering committee, but there was some reservations about the turnout but in typical, just life. There are a number of entries that came in at the last minute and again, There are a number of entries actually came in after the deadline. So yeah, just something to think about From the overclock side. We want to continue to push the forward some of these smaller hackathons. I think was a number of events happening leading up to + +Tyler Wright: leading up to ECC and all the stuff in Brussels as well as India hack upon we're talking about and then do something significantly larger in the fall slash winter. But again, I would love to have open discussion around what door hacks is offering and just hear from the community. I mention the following up with Pope folks that have participated to see what their thoughts and path forward is so that also potentially going to decision. I saw a hand up, but now it's down. + +00:15:00 + +Tyler Wright: Yeah, so there is an opportunity. I think much of the available community pool spend will be available for the bigger hackathon and September October November maybe that even gets broken up into two smaller hackathons or meet the three criteria again. There are some funds from that pool that can be used for some of these smaller hackathon efforts some hacker events that will be involved in don't even require any funding from us just like spreading the word and awareness but as the Indian hackathon as an example, + +Tyler Wright: The idea as I've thought about it with Huey and some other members of the community is to use, small amounts of money from that larger pool of hackathon funding to support some of these smaller hackathons and spread awareness to builders all around the world. So, again very much up for discussion, but that was a thought process. That I've been thinking about with Huey for some of the available community pool spend used for hackathons. + +Tyler Wright: I believe Zeke put a question in the chat, when will planning start for the big hackathon at the end of the year? It has a great question. I think the idea was to initially wait until late August to start planning. I do think we should start playing a little bit before that and then when potentially Adam comes back there's some things in place. + +Tyler Wright: I would vote that going into the next Sig Community monthly meeting. Maybe we have that and talking point and we can start to put together a committee and start to think about what and end of 2024 or a Q3 or Q4 hackathon to look like and start to put some of the items in place that we know have been successful from the previous two hackathons Zeke. What do you think about that or others on this? Call Robert? I know you've been active in both hackathons. Do you think we should wait until September to get started or do you think there's some planning can start earlier than that? + +Robert Del Rey: pay Tyler + +Tyler Wright: Yes. Yeah, go ahead Robert. + +Robert Del Rey: there was gonna say I agree with you. Maybe we can start it as we can install talking in the next Community monthly call. And from there we can start working on the hackathon. + +Tyler Wright: Excellent. I think Zeke breaks up a good point that I would like the community to be thinking about a little bit more especially insiders in vanguards is what are some tracks that you see that maybe folks aren't building around right now that would add events value to the constant Network whether it be user experience standpoint or just tooling + +Tyler Wright: or anything else, if we can start to think about tracks going into next meeting and then again start to think about a committee and just refining some of those tracks or ideating around some of those tracks. I think that would go a long way because I know historically that's been the most challenging part and the most time consuming part is determining which tracks make the most sense so again if there's anything that you all see on the community side, whether it be tooling or themes on the provider side deployment or elsewhere that you think kids are worthy of a track. Please start to drop those in sick community and we can start to talk about those going into next month. + +Tyler Wright: excellent All Is there anything else that anybody wants to discuss I would someone asking chat. Where do we suggest attracts? I believe there is a hackathon channel. If not, you can also drop them in the Sig Community Channel and then we can start having discussions. I do see a hackathon channel here in Discord again, feel free to drop into Community or hackathon. And what's the threat has begun then we can just continue that thread dropping in tracks. Preferably the working group for their cash hackathon makes the most sense. + +00:20:00 + +Tyler Wright: One other thing and again, we talked about it during the steering committee. shout out to Robert and piber for all the work that they did around the developer onboarding program. They dropped a wrap up yesterday again. I'll drop that in the chat for anybody. there's no more missions at this point. I believe everyone's been paid out. But this is a program that I would like to see continue. I know that again many of the Milestones were hit I know that there's been new members that come in through these kinds of programs of For lack of a better word like mercenary types that are independent contributors are looking for projects where they can earn. + +Tyler Wright: Rewards for their time there have been a number of developers that I have. No at least heard about a class dsili and then have come in shut off their abilities and have been connected as Builders and looking to build again is more building opportunities present themselves, whether it be the maturity of the core code base or whether it be maturity of console 2.0 and other tools, I believe there's gonna be more opportunities for people to contribute. So again, I would love to see this program continue, but I do want to see if Robert has anything he wants to mention here, after the wrap up went out just yesterday, so Robert take it away. + +Robert Del Rey: Sure, just one thing. Yeah, we are not opening new missions for now until we finish the discussions. However, we are working on join collaborations with other projects on C and on Galaxy 2. So maybe the community will be able to see approximations about a cash and missions about other communities through City. So yeah, I just wanted to drop that. yeah. + +Tyler Wright: excellent I know that Again, is there anything else you want to highlight as you continue move forward? We're gonna postpone some of the zealy meetings currently that working group. and then again, I'm sure they'll be further discussions after the wrap up and next steps. But Robert, is there anything that you want to highlight on this call today? + +Robert Del Rey: Thanks, Yeah, that's a great point. We won't be having the weekly call at least during the month of June. And the other thing I wanted to say is that most of the rewards have been paying have been paid however, a few people still have and playing their rewards in the claim window will close this Friday 14. Just wanted to say to + +Tyler Wright: Thank you very much. cool again. Is there anything else that anybody wants to discuss here live? + +Tyler Wright: If not, then I believe prior to the next call many folks including Amanda and others will be in Brussels. If from the time conflicts, we might move this call back a little bit to accommodate that but again as we continue to look forward, I'll be following up with some of the folks related to the hackathon. If anybody has any thoughts or opinions about the quadratic funding from Dora hacks, please make those opinions hurt and sick community. We're going to talk to think about the next That's big Akash hackathon and folks can start to think about tracks and going into our next meeting. we'll spend some time, putting together a committee and getting as much as we can ready in anticipation for again another successful hackathon. + +Tyler Wright: Other than that again, there's a number of things going on the Insiders front again, appreciate all the folks that had watch parties. We talked about that during the steering committee. But again, feel free to get involved. There was a successful update upgrade rather to a cash main net 12. So shout out to all the validators. There will be some more messaging available soon to the providers to upgrade their home charge. So look out for that. But again much appreciated everyone's time. Thank you Amanda for walking us through all the work you've been doing leading up to Brussels. If anybody wants to get it more information on there, please again, drop Amanda message and see Community or elsewhere. Thank you Robert for all the work that you've been doing and pibber as well around. + +00:25:00 + +Tyler Wright: The developer onboarding program as well as a follow-up from the Cosh hackathon. And again, we'll continue to stay up to date in Discord lookout for a number of meetings as a working group for provider audits that's happening this week. I know hybrid def I got some money for his team to do from the community pool spend and so you can track that on product and Engineering road map, but there is a working group session this week as well as again a number of other working group sessions and sigs that you can come to with also highlighting the Sig economics,… + +Robert Del Rey: Thank you so… + +Tyler Wright: which will be very Lively next week with a number of conversations. + +Andrew Gnatyuk: he + +Robert Del Rey: Tyler. Stay safe. + +Tyler Wright: so again We'll be in touch with those that will be going to Brussels very very soon much appreciate everyone's time today. + +oo o: prosper + +Tyler Wright: I hope everyone has a great rest of their day and great rest of the week and we'll talk online. And there's Adam always and she's calls. + +Tyler Wright: Luna I'll follow up with you offline about who's going to Brussels that's still being decided we talked about that the top of the call, but again, I'll follow you online but is Adam always says See you in the metaverse. whatever + +Meeting ended after 00:26:52 👋 + From 3a631c68520b1ef786c9cbfa0ed0afa162083a28 Mon Sep 17 00:00:00 2001 From: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Date: Mon, 8 Jul 2024 23:03:54 +0000 Subject: [PATCH 51/55] Create meeting notes for sig-support #34 (#622) * Create meeting notes for sig-support #34 Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> * Update 034-2024-06-26.md add video recording link Signed-off-by: Drinkwater --------- Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Signed-off-by: Drinkwater Co-authored-by: Drinkwater --- sig-support/meetings/034-2024-06-26.md | 375 +++++++++++++++++++++++++ 1 file changed, 375 insertions(+) create mode 100644 sig-support/meetings/034-2024-06-26.md diff --git a/sig-support/meetings/034-2024-06-26.md b/sig-support/meetings/034-2024-06-26.md new file mode 100644 index 00000000..a785f4ac --- /dev/null +++ b/sig-support/meetings/034-2024-06-26.md @@ -0,0 +1,375 @@ +# Akash Network - Support Special Interest Group (SIG) - Meeting #34 + +## Agenda +- Triaging issues in the support and console repositories. +- Discussing support feedback from Vanguard insiders and community members. +- Restructure of the meeting format. + +## Meeting Details +- Date: Wednesday, June 26th, 2024 +- Time: 07:00 AM PT (Pacific Time) +- [Recording](https://edy24xoc5isqb4ilutntgush3jmsnlcnfjaajdnsr2f5d34caktq.arweave.net/IPGuXcLqJQDxC6TbM1JH2lkmrE0qQASNso6L0e-CAqc) +- [Transcript](#transcript) + +## Participants +- Tyler Wright +- Scott Carruthers +- Andrey Arapov +- Damir Simpovic +- Rodri R + +## Meeting Notes + +- **Introduction:** + - Tyler Wright welcomed everyone to the biweekly support meeting. + - Overview of the agenda items: + - Triage issues in the support repo and console repo. + - Gather feedback from Vanguard insiders and community members to improve support documentation and identify recurring themes. + - Discussion on the restructure of the meeting. + +- **Issue Triage:** + - Scott Carruthers took over to triage issues. + - Only one issue was awaiting triage: + - **Issue:** Kubernetes concern for providers spawning too many processes within a container, affecting the host and potentially crashing it. + - **Discussion:** + - Scott asked if Andrey Arapov had seen the issue before. + - Andrey confirmed it was the first time he saw the issue. + - Scott provided a brief overview and suggested some testing to understand the problem better. + - Andrey agreed to review and test the issue further. + - The issue was assigned to Andrey for initial review and labeled as P2. + +- **Feedback from Discord and Other Channels:** + - Tyler Wright opened the discussion on feedback from active Discord members. + - **Damir Simpovic:** + - Mentioned an increase in new, unknown accounts asking directly for partnerships without proper introduction. + - Suggested a filtering mechanism to avoid tagging core team members without proper context. + - **Tyler Wright:** + - Agreed with Damir and suggested training insiders and community members to ask follow-up questions to filter legitimate requests. + - Highlighted the importance of understanding what the person is looking to do with the Akash Network before tagging core team members. + - **Rodri R:** + - Agreed with the need for a filtering mechanism. + - Mentioned issues with bots starting conversations and sharing scam links. + - **Scott Carruthers:** + - Suggested creating a dedicated channel for new partnerships and integrations. + - Emphasized the need for a structured approach to handle partnership requests. + - **Tyler Wright:** + - Proposed training insiders to ask specific questions to filter out non-serious requests. + - Suggested using a standardized set of questions to streamline the process. + +- **Discussion on Uptick in Activity:** + - Tyler Wright asked if there was an uptick or downtick in provider activities and deployments within the ecosystem. + - Requested continued monitoring of this trend to see if documentation improvements are reducing the number of questions or changing the types of questions being asked. + +- **Meeting Restructure Proposal:** + - Tyler Wright discussed a preliminary idea to combine the support and documentation meetings due to their overlap. + - Proposed having a monthly SIG engineering core meeting focused on blockchain and technical issues, reducing the frequency of the SIG support meeting. + - Emphasized the importance of triaging issues transparently to encourage community participation. + - Acknowledged the learning curve for new contributors and suggested streamlining the process for more effective engagement. + - Asked for initial thoughts, concerns, and feedback on the proposed restructure. + +- **Sig Clients and Console 2.0:** + - Tyler Wright mentioned discussions in the Sig clients meeting about Console 2.0 and its impact on the Praetor team. + - Scott Carruthers has been refining provider build upgrade paths with ongoing internal discussions and community feedback. + - Testing remains a key next step for finalizing these upgrades. + +- **Upcoming Meetings and Working Groups:** + - Tyler reminded attendees of several upcoming meetings: + - Sig Providers meeting in 29 minutes. + - Akash website and documentation working group meeting tomorrow. + - Steering committee meeting tomorrow afternoon. + +- **Documentation and Sig Website Meeting:** + - Scott Carruthers raised concerns about the overlap and relevance of documentation discussions within the Sig website meeting. + - Tyler clarified the hierarchical process for merging documentation items, which involves checks from Scott or Andrey. + - There is no expectation for Scott or Andrey to join every Sig website meeting unless there is a specific agenda item relevant to documentation. + - Tyler emphasized efficient use of core team members' time, ensuring agenda items relevant to them are prioritized. + +**Clarifications:** +- **Participation in Sig Website Meeting:** + - Scott and Andrey are not required to join every Sig website meeting. + - They will join only if there is a specific documentation-related agenda item. + - Tyler will ensure relevant items are scheduled early in the agenda to optimize time management. + + +- **Handling Documentation Updates:** + - Scott Carruthers raised a concern about managing documentation updates, especially when the core team is busy. + - Tyler Wright suggested that if a core team member has the time and willingness, they should handle the updates directly for efficiency. + - If the core team is unable to handle it, creating an issue in the appropriate channel is recommended, allowing community members to pick it up. + - There is a need to ensure community contributions are encouraged without overburdening the core team. + +- **Engaging the Community:** + - Tyler emphasized the importance of community contributions to manage the workload. + - If core team members are too busy, they should still ensure issues are created for community tracking. + - Tyler acknowledged Hero's proactive contributions and encouraged others to follow suit. + - Scott agreed but expressed slight concern over issues potentially falling through the cracks if neither the core team nor the community takes immediate action. + +- **Next Steps:** + - Tyler proposed discussing this further in the working group for the website and documentation meeting tomorrow. + - Emphasized the importance of creating issues for tracking any undocumented discussions or updates in the Insiders chat. +**Closing Remarks:** +- Tyler thanked everyone for their time and contributions, emphasizing the importance of efficient collaboration between the core team and the community. + +## Action Items +- Tyler Wright to add the restructure of the meeting format to the next meeting's agenda. +- Tyler to follow up on creating a standardized set of questions for insiders to use when handling partnership requests. +- Damir Simpovic and Rodri to monitor Discord for partnership requests and apply the filtering mechanism by asking follow-up questions. + + +# **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 six support biweekly the support special interest group goes over. any issues that are in the support repo sometimes in the console repo triage is any issues that are awaiting triage and then the second agenda item is to talk to members of vanguards insiders and other members of the community that are active in Discord and other channels to see how support is generally going to determine if there's anything that needs to get changed in terms of documentation or any themes anybody sees across different support channels I will add an agenda item just about again the restructure of this meeting as we move forward, but I'll save that for the end. + +Tyler Wright: We'll start off by handing over to Scott and Scott will go through any issues that may be awaiting triage. And then again if anybody wants to talk about any issues, feel free to jump in after Scott has done triashing issues. So Scott, I'll kick it over to you. + +Scott Carruthers: All right, so just start is everyone able to hear my audio? I feel I can get in some network degradation is My coming through Okay, I'm gonna thumbs up. + +Tyler Wright: Yes. + +Andrey Arapov: long and clear + +Scott Carruthers: Okay, so the next step is let's see if I Share my screen without any degradation. + +Scott Carruthers: Okay, is everyone able to see my screen? + +Tyler Wright: Yes. + +Scott Carruthers: Okay, so for the purpose of triage issues, this should be very quick today. So as everyone is aware that open issues are created on the Akash Network support repository, and we usually go through an exercise of just going through. items that are away in triage and of course afterwards we can also take any questions on any other issues that are not covered, but currently we only have a single Issue, that's a waiting triage. So I'm going to go into this. Andy, Come across this issue. Previously, have you read through this or is this the first time that you're seeing this issue? + +Andrey Arapov: Let's give some foregone. I think I have never seen this before. + +Scott Carruthers: Yeah, I haven't seen this until I was just some prep for this meeting. I was wondering if maybe initially and I don't know. I don't want to put you on the spot of having to read through this in real time, but Luna opened up a kubernetes concern for providers and spawning. Too many processes within a container and affecting the host and possibly crashing the host. So whether this is a Terraria or not, obviously we could do some testing it. Maybe you can have some initial thoughts. But I was wondering if we could maybe initially take this out of waiting tree out. I'll send it as a P2 and assign to yourself for initial review. + +Scott Carruthers: Yeah. + +Scott Carruthers: Yeah. + +Scott Carruthers: Yeah. + +Scott Carruthers: Yeah I agree with everything that you just said,… + +Andrey Arapov: Yeah, yeah,… + +Scott Carruthers: I doubt based on our limits. + +Andrey Arapov: definitely I can review… + +Scott Carruthers: This is actually a concern. + +Andrey Arapov: but briefly I just explained through it while we were talking. + +Scott Carruthers: But yeah, if we want to go through some testing and… + +Andrey Arapov: So basically it's like,… + +Scott Carruthers: then maybe we can quickly come in and… + +Andrey Arapov: if you deploy some script that like a pork cell or… + +Scott Carruthers: close of the Great. + +Andrey Arapov: something some bump plots they are limited by the amount of memory they are being limited by so basically they like memory it's not only constraints… + +Scott Carruthers: And with that as I said, that was the only thing awaiting triage. So definitely. + +Andrey Arapov: if you neither the only is a process space so that kind of thing we can definitely test… + +Scott Carruthers: Pepito open up the floor and any of the issues that we said that was the only one that we needed to. + +Andrey Arapov: but by default. there I don't remember the number on top of my head,… + +Scott Carruthers: Make assignment and do proper labeling but more than happy to discuss any of the other open issues as well. + +Andrey Arapov: but there is some limited parameter for that so we can just basically run some tests. + +Scott Carruthers: Is there anyone in the audience that would like to discuss any other issues? + +Andrey Arapov: I can count on my provider different assignment for me things. + +Scott Carruthers: that was quick and easy if there's no other questions and that's all we have today. + +Tyler Wright: Thank you Cool, continuing to move along with the agenda. I did want to see could we do have some? Folks that are fairly active in Discord here have there been any themes that anybody wants to call out in Discord or is there any behavior and to score that anybody thinks might be worth sharing related to support here on this call? + +00:05:00 + +Tyler Wright: I'll go ahead damir first and then rodri after. + +Damir Simpovic: so the only thing It's actually like to. mention is there's a lot of completely unknown brand new accounts on Discord asking directly to talk to somebody about my partnership and then there's a number of people specifically. Okay, I don't want to bring up names. It doesn't matter. But they immediately point to Adam or to I don't know you Tyler or somebody else from the core Team without actually even knowing who this person is what they want, brand new account. I mean If you guys are cool with it, I'm cool too. But I think it's a waste of people should really not tag. + +Damir Simpovic: our members of the core team just because somebody is asking, there should be some kind of + +Damir Simpovic: let's say a filter. Yeah. Just yeah my opinion. + +Tyler Wright: I would just chime in before we head over to rodri. I would completely agree with that. + +Tyler Wright: In many cases when I get tagged in something or I see somebody from the core team has been tagged in something and they haven't responded yet because probably there's no been filter process. What I try to do is I try to ask that person in that public Channel what exactly they're looking for that is a filtering mechanism that again people will identify themselves or not and just disappear, but to your point and this is something that maybe we should talk about in the inside or office hours and just in general, I would ask that anybody that sees those kinds of conversations happening instead of again adding specific members of the core team, especially members that are not even online right now, but instead ask them because again Akash network is open source, what they're looking to do with the Akash Network and then from there, those responses can help dictate what next steps may be. so to me, I think you're dead on that and then again, that's something that + +Tyler Wright: If I forget please remind me to bring up in the proper channels moving forward. + +Tyler Wright: Go ahead rodri. + +Rodri R: Yeah, thanks a mirror. Totally agree with him. And with you I've seen those two and I wasn't sure how to handle those either but recently all the music don't want to point any names. But yeah, some people just attack work team. And filter would be great. And besides that also for the last two weeks, there's been these new kinds of bots that they start like, they're all so new accounts and they started conversation between each other. And then they share links which obviously or most likely are leading to scam websites. Not sure how we can get rid of those because they just start a compass conversation between them. + +Tyler Wright: Go ahead, damir. + +00:10:00 + +Rodri R: Perfectly, I'll do that. + +Tyler Wright: Is there anything else that anybody is seeing? Inside Discord or other channels that might be worth sharing go ahead Scott. + +Scott Carruthers: and maybe I missed possible suggestion here, but regarding the overall point of people being integrated interested in integrating with Akash or forming a partnership with so I like the idea of + +Scott Carruthers: filtering out people that are tagging the core team as well, I guess and this is the part that maybe I miss what are we suggesting as a solution to this though is so Discord is If there's a partner in the ecosystem out there that is internet interested in working with Akash a partnership or integration. Discord is probably most likely they're easiest way to initially get in touch with us. So What is the solution and so even if we disallowed them tagging the core team initially and then we allowed insiders to review it. I would think it would end up in the same place. the Insiders would probably have to reach out to Tyler or anneal and ask if this is a partnership that we're interested in so I've just wondering what the solution is here. So the only thing I can think of is we create a partners. + +Scott Carruthers: I don't know what it would be called because obviously we want existing Partners to end up in this channel, but it like new partners or Integrations Channel and then when someone tries to tag the core team we direct them to that channel and then we just release our controlling it all and then one channel, but yeah overall obviously love the idea of disallowing they tagging of core team members, but how do we solve this and allow people that are interested in new Partnerships and Integrations initiate that contact + +Tyler Wright: So my thought process wasn't like actually doing a setting inside Discord that would not allow them to do it, but the thought process was. Up training insiders and other members of the community that maybe don't know what to do right now and give them in Specific Instructions to follow-up questions to that person that said that's asking for the partnership. So instead of just saying instead of Company XYZ coming in Discord hey, I want to partner with Akash and somebody just tagging. Myself a meal or Adam that's the person you need to talk to. + +Tyler Wright: That person that sees it that is actively as active and Discord says what are you looking to do? And if they say I'm looking to integrate, Akash into our company or hey, I'm looking to do a marketing partnership. Then at least that follow-up will allow me to better direct the conversation. I'm still going to have to be speaking for myself. I'm still gonna have to be Hands-On and Discord to read many of these conversations, but there's initial step of just and many times people just blindly say hey, it's mostly a marketing partnership. I want to It's all right, cool. What's the partnership? I don't know. We'll figure out later. But let's start with the Tweet. We can immediately filter those things out, that was the idea. + +Scott Carruthers: All Yeah, yeah. So yeah, the solution that we're suggesting is coming up with a can list of questions so that when you review a Tyler a nail tester review it that one step had a okay. Yeah, that makes sense. + +Tyler Wright: Yeah. + +Tyler Wright: Go ahead rodri. + +Rodri R: Yeah agree with you all what I usually try to do with those is Tyler says ask them about what they want to partner with. But then I'm 60 to 70 percent of people who are asking for a partnership. at least in my Opinion they just looking to do. this listing akt and some decks some other place. And then I just don't Point them out. But if it's a legit company then I'll take someone but yeah. + +Tyler Wright: yeah, I would just Go ahead, damir. + +Damir Simpovic: What I was thinking. Okay, sorry. when I was why I'm pointing in out because people immediately jump, they don't want to put any effort into even introducing themselves. So these are the ones that I'm already on the verge of banning them. I mean immediately when I see, I don't even want to ask when they don't even take the effort to say, I am decent that and we are doing this and that and you would really be nice if we could talk to somebody, if they don't even take that amount of effort that requires just a bit of copy and pasting. + +00:15:00 + +Damir Simpovic: But just immediately jump to who could I talk to from the management about the partnership for instance and that's their first message, ever they just joined. And then there's a number of people that immediately respond to messages like that. ging Adam tagging Tyler tagging anneal tagging Scott's, I mean, it could be an actual legitimate request. + +Damir Simpovic: But 99% of the time those messages are just either scams or waste of time or asking for money or whatever. So what I was thinking was just kind of a higher archetical approach to this a filter. Okay, please introduce yourself, please If you have a request or you want to get in touch with somebody from the core team, that's fine. Just please, introduce your project. Make it so that we don't actually need to so that it doesn't immediately to I don't know. whoever + +Damir Simpovic: so that there's a little bit of effort requires, to actually reach somebody at least some amount of effort that Tells me for instance that this person. is not after just a quick Buck or something, that's + +Tyler Wright: No, I agree with you wholeheartedly. And again Akash is open source. So while a member of the core team is maybe just working in and it's well positioned to provide an answer this is a entire Akash Community that's making these decisions, someone like many cases special with the dexes. We try to point those people to Sig economics and starting conversation, right because they're not just gonna be like, hey, who do we talk to and a member of overclock is going to make a decision? Yes or no. so I agree with the mere wholeheartedly and we'll talk about this more again an appropriate meetings, but I think it's a good thing to call out and the good thing that I know we're seeing a lot more of which is again speaks to the kind of project akashes, but also speaks to some of my general frustration with the space where people just think + +Tyler Wright: tweeting something is a partnership and I think our expectation here as a group of Builders, actually trying to build something real is far beyond that and we need to filter those people out. So A great point damir and again, we'll follow up on that as an action item. Go ahead rodri. + +Tyler Wright: Absolutely. + +Tyler Wright: All Real quick. I'll follow up with that later. + +Tyler Wright: I did want to see maybe this is not something we could take offline, but I did want to see if I know there's been an uptick in potential scammers. I did want to see if you all saw more providers coming into the ecosystem or more people and deployments channel more people looking to get involved. I seen a number of more contributions as of the last couple of months and people looking to contribute to the cash project, but I wanted to see if you all seen an uptick downtick or any sort of + +00:20:00 + +Tyler Wright: Any sort of understanding of what's been happening in terms of folks deploying or providers and have you seen more than in months pass or less than a month's past. But again, we can feel free to take that offline. If you don't have an accurate figure, but that's something I would ask that folks here continue to monitor as we continue to move forward to see if documentation is continuing to improve and so people have less questions because they're getting everything that they need or people are asking different kinds of questions that maybe again should Be answered elsewhere. And I guess that is a good segue into the last agenda item that I was going to talk about it again, if anybody has any open discussion items related to support that they want to talk about here today. Feel free, but one thing that + +Tyler Wright: That this is kind of alpha that want to talk about in terms of the structure of this group. I know that originally this was a monthly meeting and it changed to a biweekly meeting as we were looking to get more folks to see again the triage process and then hopefully get involved in contributing to the core code base. Obviously anybody can contribute to the core code base and the repos are open, but we have found over time that there's just been a learning curve with people getting up to date and helping to solve some of these support issues in the support repo. + +Tyler Wright: There has been an idea basically to have a monthly again. This is just a preliminary idea that's been floated. a monthly like a Sig engineering core meeting which would be a combination of support and chain, where conversation would happen about, blockchain next steps, there's a cosmos SDK upgrade to 47 or 50. There's a lot of work that happens there. So again that will be talked about in addition to issues and it'll be a chance for any member of the community to remember to meet with members of the core engineering team and talk about anything and that would happen on a monthly basis and that would mean that this six support me meeting would not have to meet as frequently and the goal of this meeting would be to focus on support in the community how insiders and vanguards are doing that kind of stuff. + +Tyler Wright: I may actually be thinking about combining the support and the documentation meeting because again + +Tyler Wright: Much of what goes on with the documentation has been turned into the working group for the website and documentation. because the docs are under the website folks that are contributing to the documentation we'll meet biweekly to talk about anything related to docs working group for the Akash website and documentation. And then there's a separate special interest group around documentation as looking to meet less frequently and that's just to check in on all things going on with the working group all things related to documentation and seeing if we need to meet more frequently. My thought process was to combine six support and Sig documentation because they are very similar and a lot of things that we see potentially in support might have an effect on documentation. But the idea is that these meetings will meet less frequently. We hope that more insiders and vanguards and members of community can come and talk about what's going on and Discord telegram other channels as well. As things that maybe they've seen from the + +Tyler Wright: in terms of updates needed to documentation pain points frequently asked questions Etc, but it would meet less frequently and then + +Tyler Wright: There'd be again another meeting. That would be more engineering focused that would bring in people that of They're asking more technical questions. So I just wanted to float that idea to this group as we continue to refine and fine-tune, these six and working groups. The goal is that there's as many participants and as much Lively conversation when we do I know some of these meetings where we might be meeting very frequently, but again, very people are very busy. So there might be less active participation on a regular basis. We just want to make sure we're maximizing everyone's time. So I just wanted to float that to the community. I'm of the belief that there's still a great deal of importance in triaging issues transparently so that people from the community can ask questions people could look to get involved because again, there is a goal over time that there go developers out there that will want to contribute whether it's teams or individual. + +00:25:00 + +Tyler Wright: companies that say I really believe in It is in our best interest to help with the core product and they look to get involved in some of these conversations. But again to this point we found that number of people have come to these meetings. Try to get involved with support issues, but then whether or not they read the engineering documentation, they're is just learning curve. That folks. have had an issues with especially as they make a living doing other things with a nine to five job so Just want to see if there was any initial thoughts concerns about. This idea again. I'll float it again in Discord, but I just want to see if there's any thing that anybody want to talk about live in terms of objections the grill thoughts questions Etc. + +Tyler Wright: I see a bunch of thumbs up. So it sounds like everyone's kind of on the same page. And again, this is not yet determined and finalized but it will continue out to continue to talk to members of the community and then also members of engineering team and we'll take next steps from there. + +Damir Simpovic: I have a sorry to steal your show. Andrey there's a number of providers that can be signed. + +Tyler Wright: Cool that there's nothing else then again. I'll remind folks that there's Sig providers meeting happening in 29 minutes damir's got some stuff that I know he wants to talk about. + +Tyler Wright: + +Damir Simpovic: And tagging you. But you probably missed it. + +Tyler Wright: We'll have some follow-up discussions related to you… + +Damir Simpovic: So just that's a reminder. + +Tyler Wright: some discussion happened Sig clients yesterday around console 2.0 and… + +Damir Simpovic: That's all. + +Tyler Wright: what that looks like for the prior team and I know Scott has been refining the provider build upgrade paths and there's been some talks internally and… + +Damir Simpovic: Should I like the Emmy or? + +Tyler Wright: again with members of community about just some finalized testing that needs to get done as Next Step. So we'll talk about that during sick providers and then tomorrow again, there's a working group for the Akash website as well as documentation. So if anybody wants to contribute to the website contribute to documentation, feel free to join that working group tomorrow, and then they're also as a steering committee which will meet again at tomorrow afternoon. Go ahead Scott. + +Scott Carruthers: Yeah, just sorry since we have some time Tower. I know that we've talked about this before but I wonder… + +Tyler Wright: So a couple meetings to + +Scott Carruthers: if it is useful for the people on this call to have a clear understanding about this as well this so it documentation. + +Tyler Wright: For but much appreciate the conversation today much appreciate everyone's time. And again, we'll follow up with some of these conversations online. + +Scott Carruthers: Kind of focus so much support related. So again people I candy and… + +Tyler Wright: all thank you Scott. Go ahead damir. + +Scott Carruthers: Damir, and in rodri and probably others on the call that are involved in documentation. + +Tyler Wright: You're good. + +Scott Carruthers: I know that we talked about this before and you also just said that maybe some of this is influx of as well. Maybe there would be an idea of combining the six support and Sig documentation meeting. So I also understand that again, it could be influx, but I'm still not sure that I'm clear. And so I want to make sure that everyone else on the call is clear with the idea of getting rid of the Sig documentation. Biweekly or monthly meeting. However, frequently that met in a lot of those discussions are under Sig website, which makes sense that documentation is now on the Akash website, but they're Seemingly very different topics of so a lot of the conversation and the website Sigma made in. + +Scott Carruthers: a majority of the people on this call. Don't join that because a lot of it is design discussion and other things with the actual functioning of the website. and it sounds like right now because documentation is under the website where possibly any documentation conversation of Interest would happen in that Sig. So I guess I'm still not clear and maybe for the other members of the call is people that are involved in documentation at this point should be joining the Sig website or only On request. So again, my overall concern is that probably a majority of that meeting isn't really relevant to us, but If a documentation topic comes up then obviously we need representation or we should be involved. So I'm just want to make sure that everyone is clear on how to navigate that based on the current meeting structures. + +00:30:00 + +Tyler Wright: Yeah, so it is very much again in flux. What we found is there's been a number of community contributions from folks that are looking to do both, contribute to documentation and the website from a hierarchical standpoint. the idea is before any documentation items get merged. there is a check from either Andrey or Scott and so that can be done async if we start to find that there's a number of Actual discussions that need to happen then I will ask Scott Andre to join the meeting and we can talk about as an agenda item as we prepare, but that's not something that I would require. + +Tyler Wright: either of you to join I would ask an obviously anybody from the community is welcome to join but + +Tyler Wright: Before there is a hierarchy. Between members of that working group and piyush about how documentation PRS are merged and that involves again in most cases a member of Scott either you are Andre, but as we move forward we can look to fine-tune the idea. The goal is that again members of the core team who are very busy don't have to feel like they have to join three or four sigs and working groups. But again, there's + +Tyler Wright: So much going on and so much that the core team is involved in that. We just have to figure it out as we go along I guess in the short term. + +Scott Carruthers: Yeah, definitely fine figuring out as we go along and again understand that some of its influx so I think Maybe the number one thing I was looking for there is and you've set this in the past. I'm just making sure that everyone is clear you want to really expect. people Andy and myself, who are Responsible for documentation specifically to join the Sig website call and would probably only join it if there's a request interesting item that's going to be discussing that session so we'll join on request. But again, I just want to make sure that there wasn't any expectation that we're going to start joining the sick website meeting and it doesn't sound like there is that expectation, so + +Tyler Wright: No expectation. And again, we'll make sure that an agenda is set out for every meeting and there's anything specific that might call upon you then I'll coordinate with you all to make sure that you're available and then make sure that your time is utilized. and as an example, if We have a number of items to cover. I'll make sure that documentation item is on the earlier side the agenda so that you're not helping to spend time working on things that maybe are less interest to you. I'll make it clear prior to the meeting. + +Scott Carruthers: Yeah, sounds good. And I want to turn this into a documentation made in but just another item that I think possibly could be of interest as entire I'm sure you have some thoughts on this and I don't think it's anything. Like severe that I think we're handling this all very well reasonably. at this point but Sometimes there's things that come up in documentation like this morning. There was a Insider conversation about provider Audits and if we have that process docume So the thing I think is interesting in here as it's just by my nature. I instantly think I'm just gonna go into documentation and make that update. But if we should be relying more on the + +Scott Carruthers: Community like what that's going to look like over time. Sometimes it just happens naturally and somebody will raise their hand within the Discord discussion saying yeah, I'll take that on but short of that. Yeah, how do we not navigate that should we? Lean towards in that circumstance if I want to handle it. I'll just handle it myself or is a way for the community become more involved in documentation. We shouldn't lean that way and if we don't lean that way how to win something comes up in Discord. So obviously create an issue I suppose. But yeah, I'm just wondering how we navigate that going forward and making sure that items of Interest are handled without the core team necessary paneling them themselves. + +00:35:00 + +Tyler Wright: I mean, yes, my two cents on this is if a member of the core team has the time and the desire knock it out, and what and we could just keep it moving. Other than that, I would ask that and we'll talk about more about this in entire calls and other calls is have those people take the appropriate measures to make an issues and then I know that there's members of the community. There's one on this call hero that does a great job of identifying issues and solving those issues as quickly as possible. So there's a number of people that are waiting in the wings to help contribute, but I would say in order of operation standpoint. I think the idea is + +Tyler Wright: Obviously, there's so much going on with the Akash Network that there needs to be Community contributions and we need to push people to contributing more but there's already plenty of places for people to contribute. So I don't want that to be a deterrent for you maybe I shouldn't do this because somebody from the community should do this, but if it makes sense and it's efficient for you to do it, then I would say do it. Otherwise again, you can just stay heads down and we can make sure that an issues created by somebody else and then it gets solved. There's plenty to get solved so I would say short answer. If you want to do it, if you don't and you have the time to make an issue and we'll go from there, but don't feel like you're taking contributions away from somebody else because again, there's plenty for folks to get involved in. + +Scott Carruthers: Yeah, sounds good. I don't think that's any great concern. I have a little bit of a concern in that circumstance today in the Insiders. So if I am busy Doing devworker or other things. And I don't handle it myself and I don't create an issue and then nobody opens an issue for it. So, like I said, I don't bring this up as a severe concern, but I think there's that possibility that exists. + +Tyler Wright: Yeah. + +Tyler Wright: No, I think it's a good point in something. We can continue to monitor. We'll talk about that in the working group for the website and docs tomorrow and then also on the Insiders call. + +Scott Carruthers: Yeah, and it could just be as simple as the people that were in the discussion this morning our default response that is please open an issue for tracking. + +Tyler Wright: Yes, exactly. + +Scott Carruthers: Okay, sounds good. + +Tyler Wright: Is there anything else that anybody wants to talk about on the support front? + +Tyler Wright: If not then all I appreciate conversation again. I'll follow up with next steps in terms of the structure of these meetings be a Discord but much appreciate the Hope to see many of you and Sig providers. Thank you all very much. + +Andrey Arapov: Thank you. everyone + +Scott Carruthers: Thanks. + +Rodri R: Thank you. + +oo o: lived on a prosp + +Meeting ended after 00:38:50 👋 + From 761dddcc5273a2289697474145e1309233b60e5c Mon Sep 17 00:00:00 2001 From: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Date: Fri, 12 Jul 2024 20:50:57 +0000 Subject: [PATCH 52/55] Create meeting notes for sig client #15 (#627) * Create meeting m=notes for sig client #15 Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> * Update 015-2024-04-24.md add recording link and transcript Signed-off-by: Drinkwater --------- Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Signed-off-by: Drinkwater Co-authored-by: Drinkwater --- sig-clients/meetings/015-2024-04-24.md | 298 +++++++++++++++++++++++++ 1 file changed, 298 insertions(+) create mode 100644 sig-clients/meetings/015-2024-04-24.md diff --git a/sig-clients/meetings/015-2024-04-24.md b/sig-clients/meetings/015-2024-04-24.md new file mode 100644 index 00000000..e15e229e --- /dev/null +++ b/sig-clients/meetings/015-2024-04-24.md @@ -0,0 +1,298 @@ +# Akash Network - Clients Special Interest Group (SIG) - Meeting #15 + +## Agenda +1. Welcome and Introduction +2. Updates on Akash Clients and Projects +3. Discussion on Meeting Cadence +4. Updates on Terraform Open Sourcing +5. Cloudmos Updates +6. Human HQ Team's Automated Pipeline Project +7. Demo by Chaitanya Rai +8. Open Floor for Questions and Comments +9. Overview of Console 2.0 Plans by Anil Murty + + +## Meeting Details +- Date: Wednesday, April 24, 2024 +- Time: 08:30 AM PT (Pacific Time) +- [Recording](https://j3gehsinfdsmtozvozl7ne3dv2w255mnewbmwe3unblpiayao3ya.arweave.net/TsxDyQ0o5Mm7NXZX9pNjrq2u9Y0lgssTdGhW9AMAdvA) +- [Transcript](#transcript) + +## Participants +- Anil Murty +- Bold Panther +- Chaitanya Rai +- envy | Neta DAO +- Nicolas +- Maxime Beauchamp +- Scott Carruthers +- Tyler Wright + +## Meetings notes + +- **Tyler Wright:** + - Welcomed everyone to the SIG Clients monthly meeting for April 2024. + - Mentioned the group focuses on anything related to Akash clients or those building solutions on top of Akash. + - Proposed changing the meeting cadence from monthly to every two months to improve attendance and participation. + - Requested feedback on the proposed change in meeting cadence. + - Highlighted the ongoing coordination with Luna to open source Terraform, which is expected to be completed soon. + - Mentioned the efforts to push teams into public channels for better visibility and communication. + - Discussed the Human HQ team's work on an automated pipeline project in collaboration with Neta DAO, Cloudmos, and Overclock Labs. + +- **Maxime Beauchamp:** + - Provided updates on Cloudmos, including the refactor and rebrand from Cloudmos to Console. + - Mentioned the work on improving features based on new chain additions, such as storage classes for AI workloads and private registry support. + - Discussed improvements in TypeScript type generation in the Akash API to streamline JavaScript client operations. + - Announced the onboarding of a new team member, Yarrow. + +- **Bold Panther:** + - Updated on the progress of the Human HQ team's automated pipeline project. + - Mentioned meetings with the Overclock Labs team and Cloudmos team to define the project scope. + - Described the implementation of the base container to handle automated deployments and integration with GitHub webhooks. + - Offered to provide a demo of the project's current progress and requested feedback and participation from other teams. + +- **Chaitanya Rai:** + - Demonstrated the automated pipeline project by showing the SDL file configuration. + - Explained how the SDL file includes image, environment variables, repository, port number, node version, build command, and build directory. + - Demonstrated the process of cloning a repository, building it on the provider's machine, and deploying the application. + - Showed a diagram explaining the workflow: cloning the repo, installing dependencies, running the build command, transferring build artifacts, and serving the application. + - Emphasized the use of a lightweight Alpine Linux container image to minimize overhead and costs. + +- **Anil Murty:** + - Commented on the code commits related to the core repositories and network upgrade scheduled for next week, enabling data people inside services. + - Mentioned a draft document on workflow improvements and offered to share it with the team for feedback and collaboration. + - Provided a quick overview of plans for Console 2.0, which will start once the rebrand and support for private registries are completed. + - Encouraged the Human HQ team to continue developing and integrating their work with Cloudmos and Akash Console. + +**Discussion on Console 2.0 Plans:** + +- **Anil Murty:** + - Presented a draft document on the Console 2.0 project, highlighting several key goals: + - Eliminate the need for interacting with crypto or obtaining AKT. + - Allow users to try Akash services without spending money, similar to free trials offered by public clouds. + - Simplify provider selection by offering instance-based selections. + - Improve notifications for lease closures, low funds, and billing. + - Enhance log and event management by saving historical logs. + - Enable SSH access to VM instances similar to public cloud services, with reliable connection and command line access. + - Provide pre-built Linux images for common distributions and versions, allowing easy customization. + - Automate HTTPS setup and custom domain configuration. + - Explained the proposed workflow, including login options via Kepler Wallet or GitHub, and the creation of custodial wallets for users. + - Mentioned an existing solution involving a Telegram bot for notifications and expressed interest in exploring its integration. + +- **Bold Panther:** + - Offered to share information on the Telegram bot project for notifications. + +- **Tyler Wright:** + - Thanked Anil for the overview and expressed excitement for the upcoming Console 2.0 features. + - Encouraged continued tracking and discussion of these features as they are developed. +### Clossing Remarks +- **Tyler Wright:** + - Expressed gratitude for the updates from Max, Anil, and the Human HQ team. + - Confirmed work with Luna next week to finalize the open sourcing of Terraform, with an announcement to follow. + - Noted Human HQ team will add more information to their discussion, and he will supplement it with the meeting video. + - Reminded everyone about the ongoing Akashathon hackathon, ending on May 17th with over $200,000 in prizes. + - Shared the link to the hackathon for those interested in participating. + - Announced the rescheduling of the steering committee meeting to May 2nd and the planned network upgrade also set for May 2nd, pending a vote. + - Invited everyone to stay engaged via public roadmaps and Discord for any questions or further involvement. + +## Action Items +1. **Tyler Wright:** + - Post the question regarding changing the meeting cadence to the SIG Clients Discord Channel. + - Collect and review feedback from the Discord Channel on the proposed cadence change. + - Announce the final decision on the meeting cadence based on the collected feedback. + - Coordinate with Luna and Andrey to ensure the open sourcing of Terraform is completed before the next SIG Clients meeting. + +2. **Group:** + - Provide updates and announcements in the SIG Clients Discord Channel if unable to attend the bi-monthly meetings. + - Participate in the discussion on the proposed change of meeting cadence in the Discord Channel. + - Report any Cloudmos-related issues in the Cloudmos repo issues area or the Cloudmos channel in Discord. + +3. **Maxime Beauchamp:** + - Continue to provide updates on Cloudmos/Console development and new features in the relevant public channels and meetings. + +4. **Bold Panther:** + - Share a detailed update and next steps for the automated pipeline project in the SIG Clients discussion and Discord Channel. + - Provide a demo of the project's progress and invite feedback and participation from other teams. + - Share information on the Telegram bot project for notifications. + +5. **Chaitanya Rai:** + - Share the demo details and workflow diagram in the SIG Clients discussion and Discord Channel for further feedback and collaboration. + +6. **Anil Murty:** + - Share the draft document on workflow improvements in the communication channel for feedback and collaboration. + - Provide updates on the network upgrade and its implications for the project in the next meeting. + +# **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 say clients monthly meeting for April 2024. During the special interest group for clients. The group goes over anything related to Akash clients or those that are Building Solutions on top inside the sick clients repo you can track various teams that are working on again various initiative building on top of Akash. Usually we get updates from teams that join this call and we ask all other teams to leave a message in sick clients. + +Tyler Wright: I know that folks have been very busy and It has been difficult to get folks to join these meetings. I know there's teams building all over the world. And so again a number of people have historically said, yeah, I can make it and then have not been able to make it for various reasons. The plan potentially for this sig is to maybe change a Cadence of it instead of it being every month. There is some discussion and I want to pose it to this group to change it to every two months similarly to Sig analytics. Hopefully with slightly less than a Cadence it'll drive people to take the time every two months to get updates and then we can continue to attract. again other updates via a announcements from those various teams or again updates inside of Discord before we move on with the agenda. Does anybody have any issue with? + +Tyler Wright: And I'll post this question also in the state clients Discord Channel, but does anyone have any issue at this time with lessening the Cadence for this meeting? + +Tyler Wright: I'll take that silence is nobody has any issue. One thing that we talked about last meeting that is still not done. I'm trying to coordinate with Luna is the open sourcing of terraform. There was a discussion that Luna brought forth. He did receive some community pool funding for + +Tyler Wright: Terraform provider and again, I believe his work is completing. He's going to open source that and add that to the Akash Network organization. I will add it as an action item and I work with Andre offline to make sure this is done before the next state clients' meeting. And then again, we'll make an announcement in Sid clients and in Discord in general just where the new app is and how people can use it. So that's one thing that again Luna and I have talked about offline but need to get over the finish line. + +Tyler Wright: Again, there are a number of teams that I try to push into public channels, but I know that myself Anil and others have been talking to various teams that are building clients that building their own Solutions on top of a cost. + +Tyler Wright: cool one person that we usually get update from is from Max who just joined the call. you can also track updates many of the updates happening on the cloud most public road map inside the product and Engineering roadmap again any issues that are in the cloud both repo that are public facing or our actively being worked on rather get added to this roadmap. I know that Max and the most team had been working diligently on the cloud most deploy refactor and Rebrand from voice Cloud most console. + +Tyler Wright: I'll give Max a little bit of time to give an update on all the work that they've already done. But again, I know that he has been working consistently to refactor a number of items that are available in Cloud most that will now be a part of console and part and as a part of that reason. Max don't feel like to go in detail because I know that you give an updates often and various other special interest group calls and as well as steering committee, but do you want to give a short update on some of the wins from cloud most of our last month? And what's next? + +Maxime Beauchamp: Yeah, we've been working on a lot of different issues that I mentioned in this board. So yeah, like you mentioned I've been working on the refactoring Rebrand. It's a very close to being done and So that's gonna be rolled out in the coming months. We are also improving in or adding features based on what is being added on the Chain. So the storage around class that is to support. + +00:05:00 + +Maxime Beauchamp: some AI workload that need to have this type of storage class. So we have also private registry. Support that is gonna come out soon. We're improving the typescript per above types generation in a cache API. So that will make it. better streamline for a Cassius or any clients just doing stuff with JavaScript. So yeah, that's the stuff going on and I think everything's going in the decent pace and we have the new team member that we onboarded yarrow you can see the board. + +Tyler Wright: Thank you Max. Again, if anybody has any Cloud most related issues as we're leading up into that transition, you can always drop them inside of the cloud most repo in the issues area as well as in the ecosystem Cloud most Channel inside a Discord the max it do a great job of being very responsive. + +Tyler Wright: Max one other thing we talked about the top of the call is and I'd much appreciate the time that you take there are a number of other teams, as you know that are building on top of Akash. They have an open invite and many of them are invited literally on the event to these meetings and between meetings tell me that they're going to come but when it comes time for the meeting for whatever reason or not able to join. There was discussion around changing the Cadence of the sick clients meeting to every two months. So maybe that with lots of vacations folks will be more driven to join that meeting and give updates every two months. just continue to update folks more regularly inside a Discord. Did you have any initial concern with changing the Cadence? + +Tyler Wright: If you do have concerns feel free to speak. Otherwise, you can just thumbs up or stay muted. + +Maxime Beauchamp: I think it's fine. I mean currently today other than how those clients who else is here to talk about clients. + +Tyler Wright: No, nobody. + +Maxime Beauchamp: So yeah, I guess that makes sense to move it to every two months. I'll see an issue there. + +Tyler Wright: Again, we'll still look to track updates and obviously the updates on the cloud on the side are reflected in this roadmap, but I'll still look to track updates from other teams and happen put them in a public place. If not, I'll start throwing them in a public place and protagon people to correct me. + +Tyler Wright: in addition. to those Cloud most efforts at the last declines meeting there was discussion around some work that the human HQ team wanted to do around again making easy for people to deploy and create an Implement to blind automated pipeline. I know the human HQ team has been working with the net of Dao team on this kind of work. + +Tyler Wright: Homemade HQ team was able to meet with the cloud most team as well as the overclock Labs core team and you can track the discussion on where progress has gone since those conversations. I know that members of the human HQ team are here today. if anybody wants to get involved since discussion, please get involved, but I do want to see if anyone from the human HQ team wants to talk about progress made since those meetings with the clouds and over with the clients clean on next steps here. + +00:10:00 + +Bold Panther: Yeah, so yeah, thank you for the interest. So I saw the last meeting the last six clients. We are made with the world clock lab screen as well as the Carlos team. So complete the scope that is defined in our proposal was to ask that I would have required some changes in the code base of console, but + +Bold Panther: To test out the plan that we have invented. So we have been guided into basically first implement the less Scott person of and he will be building and still Park and behind the scenes with the base container of we will be handling the guitar presentation that the Deploy on the cloud onto the cost. So the base continuous will have the capabilities of other handling obviously able to fetch the wheels like George using and automate the process of building onto the providers machine. + +Bold Panther: Yeah, I thank you so much for a great. Yeah, so obviously basically you can Bachelors about what all the JavaScript Frameworks and also ash as soon as the new pull requests or new push happens on to GitHub web books. We will figure the really deployments of respect or the guitars of this case to the pride and machine. so yeah, that's the plan and we have progressing good. So we were writing some test cases. So if anyone wants to see the demo that we have made I would love to presentation. + +Tyler Wright: Thank you Pierce if you're able to drop a note because you were speaking a little bit fast. I got 85% of it and I believe I got the gist but if you can drop a quick comment inside this discussion on next steps, that would be great. And then maybe even drop the demo in there too. Just so we're all aligned. + +Bold Panther: Yeah, so to conclude the things that I said, so the movement is we were testing some test cases which can basically fetch all retails about the guitarists that has been provided by the users to be deployed on Akash and our basically script all the base container industrial power will be able to get what JavaScript framework sorry post is using and it can deploy and grown and run the scripts directly onto the provider machines. And as soon as the new push happens on the guitar proposes, this logic is being reaching basically redeployed applications onto the provider machines being push to the main branch. So we also take it some good quality demo, so Of Japanese to share the skin and presentation. + +Chaitanya Rai: Yeah, thank you for handing it over. So I'll be showing you guys the demo. So I'm sharing my screen. + +Chaitanya Rai: Yeah, I hope I'm Audible and my screen is visible. + +Tyler Wright: You are Audible and your screen is coming up right now. Your screen is visible. + +Chaitanya Rai: Thank you for confirming so we have created an SGL file which has the image. So you just go in here upload this sdl file. And so this is how it looks so it has this image and in the environment variables you can specify the repository that you want to deploy the port number the node version as well. Some people might be using different node version than our base image and then a build command and then a bill directory but these three options are not necessary. You can even go ahead and omit them. If you don't need them. We have the most commonly used things as the default settings for them. So the idea is just we can get this Rippling from the environment variables and we do the container and it will just deploy + +Chaitanya Rai: So it will keep on rechecking whether some changes have been made if the changes have been made it is going to pull them and show the new changes show the new version. So I'll go ahead and quickly show the demo. + +Chaitanya Rai: So currently our idea is just making this sdl file as good as possible and as good in handling as possible and I'm using only a single one to basically be enough for all the JavaScript Frameworks out there Because we're giving them so many options of what node version to use if they have a different build directory or if they have a different build command, so by using this we will be able to mimic a render kind of experience on a cash. + +00:15:00 + +Chaitanya Rai: Yeah, so one started container service one. We can go ahead in the logs Yeah, so you can see that it is cloning. Okay, so it was a relatively small Ripple so it's done so it clone the o. It build it here on the providers machine only and then it ran the serve package that we have in here. And if I go in here and I do this you'll be able to see the library. Yeah, so that is kind of the vision that we have and I would quickly also like to show you the quick diagram that I made for how this thing is working. So basically we have a GitH remote repo and we are using first and foremost is going to do a good clone using this shell script. So basically + +Chaitanya Rai: All we are doing is running this shell script inside this Docker container. And as soon as the change is found it pulls the change The needed nbm packages runs the build command transfer build artifacts into the directory to be served and we are serving using G server HTT server, whatever is best suited and the image is Alpine is the container image the node images and Alpine version of Linux, which is very light. So we don't think that is going to create that much extra overhead over the hardware of the provider and it will keep the cost as minimal and as minimal as possible and with all the functionalities So yeah, this was all. + +Bold Panther: ation + +Chaitanya Rai: Thank you. + +Tyler Wright: Thank you very much as much as you can share of that inside of the discussion would be great for folks and I'll drop in the link to this client meeting. So folks can also have access to live demo. Does anyone here have any questions or initial thoughts about the demo just put forth by whom an HQ team go ahead and deal. + +Anil Murty: Yeah, chaitanya and MPS. That's Very cool. I guess just one or maybe two comments one is if you follow Some of the code commits on the core repositories you may have noticed that there was a code Commitment Report Industries So I just pasted the link to that as well. that's in the code, but it requires us to do the network upgrade which is scheduled for next week. So once that is done, then you'll be able to specify the credentials for the data people inside the services and it'll be awesome for you guys to test that out once it's in the code along with your cloning sdl + +Bold Panther: Yeah, I think that looks cool and it can be great. step forward + +Anil Murty: Yeah, and then the other thing I was going to mention was I know last time when we spoke about this after you posted the discussion we talked about making sure that any workflow that you build subsequent to this. So this is obviously just a template but they eventually goes I have a workflow in console itself. one of the actions on us was to discuss with you the workflow that we are thinking about in terms of other things that we want to solve. I have a draft document on that I can share with you on the channel that you have communication. and we can certainly take it from there. But if you want I can just provide a quick overview of that as well. + +Bold Panther: Yeah, yeah for sure. You can share I think this is the first question that we are developing and as we progress more I think that problem stream as well as a period team to build things tightly on the ground most or maybe and now gosh console and I think that would be cool like that. I use other signing into GitHub and justifying that application style to the cash without having to worry about right industry fights. So I think that can be a dedicated clone on cloud nodes or console. Which the data. + +Bold Panther: Atmos and us are together can Implement if and the version that we had everything is a success for all the JavaScript Frameworks. So we are still writing some of the test cases where it has the L handling capacities and also can detect what jobs can pay books are using and we were all six exploring your suggestions about build packs. how we can build a systems are directly to get actions build artifacts on YouTube actions and then use those artifacts directly to plan to the party emissions. So the exploring multiple waste so our proposal and I hope to push the proposal regarding this what we actually are related to the first versions pretty soon. + +00:20:00 + +Anil Murty: specifically if we have time, I'm happy to give a really quick update on what we're thinking in terms of the new experience for Various calling it console 2.0 which is something that we hope to start working on. Once the Rebrand and the support for secret money or support for private Registries is done. I'm happy to do that as well. + +Tyler Wright: Sorry Anil. Are you suggesting doing that right now during this call or doing it at a later time? Yes,… + +Anil Murty: right now if this thing + +Tyler Wright: is there any before we jump into? + +Tyler Wright: Just update from Anil. Is there any other thoughts on? the presentation from the human HQ team + +Tyler Wright: again If you all can just add to that discussion much appreciate all the efforts that you all are putting in and pushing this forward and really excited for you connecting with the net of Dao team coming up with the idea sharing it getting some feedback and continuing to fight soon. So appreciate you all. + +Tyler Wright: cool + +Bold Panther: Thank you. + +Anil Murty: Yeah, so this is understate this document. It's not complete at this point. It's still a draft and I've also drop this in the communication channel that we have with you guys. But our goal essentially with this console 2.0 is to solve a bunch of problems. We may not solve all of these in the very first go in the MVP version of this but ultimately the goal is to try to solve a bunch of problems the main problems. We have identified so far a kind of called out in this list here. Most of these should be pretty obvious. I think a lot of people have thought about these problems that are thinking about building clients. So, the first two are eliminating the need for interacting with crypto. basically obtaining it with the wallet or having to obtain akt the third one is be able to try the service or try a cash without having to spend any money. So, being able to basically get a free trial similar to what? + +Anil Murty: Public clouds to give you a hundred dollars or two hundred dollars of money that you can use to stand on AWS or gcp Etc. The fourth is not needing to select a bunch of providers from a list of providers if you don't want to so, offering people the concept of an instance if you will and just being able to Say I want to get one of these instances as opposed to saying here's a bunch of providers and pick your own. So that's kind of number four. notifications for when at least is closed or when you're running low and funds or if there's billing then when you get build here. + +Anil Murty: Dealing with logs and events better. So today if you have a bunch of logs and even said came out and then you release closed. There's no way for you to go inspect those later. So having some sort of historical saving of logs will probably go a long way because we hear from customers all the time that they have no idea what happened and why a certain thing closed and then the seventh one is probably the most relevant here, which is one of the biggest problems today is that customers that are coming from public clouds like AWS so gcp they're used to the mode of being able to just get a VM instance and get an SSH into that. We have instance and the expect to be able to do the same thing in And there's two challenges there one is while we do have that lease shell in console today. + +Anil Murty: The least Channel because of a bug that exists in core code base is not reliable every time the Provider Services restart, you lose a connection to the least yet. And then also in general developers want to be able to just SSH from their own command line. So right now the thinking is we can potentially solve this one of two ways or offer essentially both the ways. One is follow what the public clouds do which is Linux images for the most common Linux distros as well as versions. So if you go for example do gcp or AWS, you might find you wouldn't do sync OS Susie, maybe another the next favor and you will do NTS 22 or something and then one version older one version you are then that And you can pick those and give you a vanilla Linux image that you can then install anything. You want to? + +00:25:00 + +Anil Murty: so that's one option is to build refer these images and have them available that are user can select from and be able to have that instance file along with dropping Their public key so that we can load that on into the Container as well. And then the second one is what you guys are working towards which is building that custom image from the user's GitHub repository in case the user happens to be reactive or a JavaScript user and is informative with infrastructure. And then the last one here is once the services fun up then dealing with the issue of setting up https and a custom domain which today requires a lot of interactions outside of the core workflow. + +Anil Murty: a lot of understanding of other services typically configured in cloudflare and stuff like that. So those are kind of main problems. This probably other ones that will come up with as well. But the ultimate goal here is to be able to get from the GPA pricing page on our cash Network slash GPU. Use the clicks on that and then ultimately ends up with their own command line SSH into the running container instance. That is either a plane Linux instance or their own custom build application of Any questions so far on that? + +Anil Murty: but I think that you + +Bold Panther: in the directly email logins + +Anil Murty: Yeah, great question. So you jumped a little bit ahead in the dark. So basically the share the workflow that again this is not hundred percent second stone or final but this kind of the general thinking right now is we would have both of these options. So everything on the right side is what is supported already in consoles Nationals today. The one on the left is what we would have to implement. So you comes in and we give them the option of logging in with Kepler. Wallet or with GitHub And I didn't get up Then we would create a wallet on the user. We have essentially a custodial wallet and manage it for them and take it. Both options would be supportive. + +Bold Panther: and there is a fourth point where you said the lack of notifications. So if I remember in last it's on there was one participant who kind of solve this problem by creating a telegram board. which was kind of notifying anything what's happening with their deployments if they are running on low, if you on the fundings they can get a notification library on the telegram. So if I clearly remember there was a one project I was getting that on because they could notification itself and I think I can search about that and share with + +Anil Murty: Yeah, that'd be great. Would love to learn what they have and how we can potentially use that if we can. + +Bold Panther: Here it shows. + +Anil Murty: Yeah, I just want to give you kind of a preview of what we were thinking in terms of this. I'll share this document with you on the channel that we have established with you. + +Bold Panther: Yes, sure. + +Anil Murty: Thanks. + +Tyler Wright: Thank you very much Anil for walking us through that a little bit again. I'm sure a number of those items will get added to a pack and Engineering roadmap over time which continued track them and talk about them as I get bills, but very exciting things ahead for cloud. Most less console console 2.0. + +Tyler Wright: Is there anything else that anybody wants to discuss that hasn't been discussed already? + +Tyler Wright: again much appreciate the updates from Max from Anil from the human HQ team. I think we have a number of action items all around. I know that Luna is traveling right now going to work with Luna over next week to make sure to terraform is open source. And again announcement will come out there soon. Human HQ team will drop a comment in the discussion that they're created with some additional information. I'll add to that with again video from this Sid clients meeting. + +00:30:00 + +Tyler Wright: + +Tyler Wright: But yeah, I get much appreciated everyone's time and effort today. And then again, we'll talk over the next maybe 10 to 15 days about changing the Cadence. It sounds like nobody on this call currently has any issue with that said I again Mo most likely change the Cadence, but I'll reach out to a couple more folks and get some more input again much appreciative once time today in the update. + +Bold Panther: But They said yeah,… + +Tyler Wright: Go ahead pierced. + +Bold Panther: I found the notification Bell that was submitted in the last of town. So this is the bill that is being created by I think Nicki Harper. So there's something like kind of notifications that we can. Think of using it and also each other anyways interested to contribute. + +Tyler Wright: Yes, Feel free to reach out to ping me if you need any support there. + +Tyler Wright: That's a great shout to that if anybody here or anybody listening to is called later the akashathon the hackathon is underway believe it ends in the middle of May. So there's still a number of weeks to get involved. I will drop the link to the hackathon in the chat and I'll drop in the notes for people. But again, it ends May 17th with over 200,000 in prices in akt, so I'll drop that link in but again much appreciated from time the updates today and we'll talk online again. No steering committee meeting tomorrow steering committee meeting has been moved to next Thursday May 2nd. There is also a planned Network upgrade. that's up for both right now that is scheduled for May 2nd pending that vote, but we'll just stay in tune online. And again, please feel free to look at the public roadmaps or get involved in Discord if you have any additional questions in between + +Tyler Wright: Thank you all have a great rest of the day. + +Bold Panther: And I would never buy. + +Anil Murty: Thanks, sir. + +Tyler Wright: Bye. + +Maxime Beauchamp: Thank you. + +Meeting ended after 00:34:04 👋 + From 333025ef2c4dcc7e68d454a9070d5220eef69a8b Mon Sep 17 00:00:00 2001 From: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Date: Fri, 12 Jul 2024 20:55:40 +0000 Subject: [PATCH 53/55] Create meeting notes for wg-website #31 (#607) * Create meeting notes for wg-website #31 Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> * Update 031-2024-06-13.md add video recording link and transcript Signed-off-by: Drinkwater --------- Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Signed-off-by: Drinkwater Co-authored-by: Drinkwater --- wg-akash-website/meetings/031-2024-06-13.md | 434 ++++++++++++++++++++ 1 file changed, 434 insertions(+) create mode 100644 wg-akash-website/meetings/031-2024-06-13.md diff --git a/wg-akash-website/meetings/031-2024-06-13.md b/wg-akash-website/meetings/031-2024-06-13.md new file mode 100644 index 00000000..9f6ff260 --- /dev/null +++ b/wg-akash-website/meetings/031-2024-06-13.md @@ -0,0 +1,434 @@ +# Akash Network - Akash Website Working Group (WG) - Meeting #31 + +## Agenda +- Review issues in the GitHub website repository. +- Open discussion for any website-related topics. +- Discuss the proposal to combine Akash website working group with SIG documentation. + +## Meeting Details +- Date: Friday, June 13, 2024 +- Time: 6:30 AM PT (Pacific Time) +- [Recording](https://urav5nq4ipj2qxxrryzspu67zqhcsvxc7iuv6mk7wkniixznkkmq.arweave.net/pEFethxD06he8Y4zJ9PfzA4pVuL6KV8xX7KahF8tUpk) +- [Transcript](#Transcript) + +## Participants + +- Bold Panther +- Denis Lelic +- Fenil Modi +- Hiroyuki's AI Notetaker (from Otter.ai) +- Rodri R +- Tyler Wright +- Zach Horn + +## Meeting Notes + +- **Introduction** + - Tyler Wright welcomed attendees and set the agenda for the meeting. + +- **GitHub Website Repository Issues** + - Tyler shared his screen to review current issues in the website repo. + - Tyler emphasized the importance of closing resolved issues. + - Bold Panther confirmed there are no unnecessary open issues and will monitor for any that need closing. + - Issues related to documentation are labeled for easy tracking. + - Insiders and Akash Community members have shown interest in contributing to documentation. + +- **Discussion on Combining Working Groups** + - Tyler Wright proposed combining the Akash website working group with SIG documentation. + - The combined group would meet weekly to discuss high-level documentation items and contributions to the documentation site and website. + - The goal is to have a more cohesive approach to managing both website and documentation updates. + - The new combined meeting would be called the "Akash Website and Docs Working Group." + - The purpose is to streamline discussions and encourage more participation. + - Tyler noted that the current working group has good participation and sees potential for more involvement from those who couldn't attend today. + +- **Praetor App Documentation** + - Discussion on the Praetor app documentation, which is not currently on the Akash Network docs. + - Plans to integrate Praetor app documentation with upcoming changes in the Console 2.0 product strategy. + - Denis Lelic will connect with relevant team members to discuss migrating or adapting Praetor docs. + +- **New and Ongoing Issues** + - New issues mainly concern documentation. + - Tyler and Denis highlighted the importance of addressing older issues as well. + - Encouragement for community members to get involved in resolving these issues. + - Denis is available on Discord to assist anyone interested in contributing. +- **Community Involvement** + - Tyler and Denis reiterated the call for more community contributions. + - Denis is available on Discord to assist anyone interested in contributing. + - Information will be divided into development and community pages. + - Bold Panther offered to take on the implementation. + + - **Provider Page Experience and Pricing Page:** + - Denis will revive the issue on provider pages and provide solutions. + - Key views: provider grid map and locality map need to be more accessible. + - Denis and Zach will work on improving the website navigation to make these views easily reachable. + - Combine general pricing and GPU pricing into a single page. + - Utilize hashtag functionality to direct users to specific sections. + - Zach emphasized the importance of clear pricing information, especially for comparison with other cloud providers. + - Bold Panther will mock up the combined pricing page on a staging site for review. + +- **Website Content Updates and Analytics:** + - Zach plans to make copy updates directly through PRs. + - This will not affect MPS as changes will sync with the main website before contributing. + - Bold Panther to discuss with Zach offline about cleaning up data sources. + - Focus on pulling active data sources from active properties and structuring GA. + +- **GPU Announcements and Contact Page:** + - Consider adding 4090 GPUs to the announcement bar due to high demand. + - Zach noted the rule of three for the announcement bar and suggested integrating 4090s if it doesn't disrupt the existing structure. + - Tyler and Zach discussed the flow and support for a contact page. + - Agreement to mock up a defined modal for the contact page and test it on a staging site. + + - **Ongoing Pull Requests:** + - Piyush mentioned an issue needing icon names for menu items. + - Denis to provide the necessary names. + - A new PR from a community member to add instructions for importing existing wallets needs minor fixes before merging. + - Piyush emphasized maintaining high-quality contributions to the website and is open to fixing issues himself if contributors are unable to. + - Tyler mentioned an influx of new contributors from the community. + - Emphasized maintaining the website's high standards and providing constructive feedback. + +**Action Items:** +- Tyler Wright to send a reminder message on Discord about the new combined meeting structure. +- Denis Lelic to follow up with the team about migrating Praetor app documentation. +- Denis Lelic and Bold Panther to work on streamlining information between development and community pages. +- Denis Lelic to revisit and improve the unified experience for providers and pricing page, with input from Zach Horn. + +# **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 working group for the Akashi website. This is a weekly working group. Today is June 13th, 20.4. Thank you to all that have joined. + +Tyler Wright: There's a couple of agenda items that I want to discuss today. Usually we go through the issues in the GitHub website repo folks can bring up anything that they want to discuss rage the website and then we can continue on one thing that I wanted to discuss and people can show thumbs up or thumbs down if they want but there's been recent discussion in save documentation about combining the working group for their class website and the working and elements of sync documentation. So I think the idea is that we would have is say documentation meeting once every other month to talk about high level documentation items. But anything related to the doc site and contributions to docs would be a part of the working group for the class website. So maybe we change a name to work and go for their cost website and docs being now all the work that bold Panther. + +Tyler Wright: Team have done on the website revamp and being at the Docks are under the website. The idea was to have a combined weekly meeting where we talked about all things cs and website related. If we need more than the hour, then we would figure out what that looks like. But again, this will be a time for people to talk about contributions. They want to make to documentation site to the website in general. So this is idea that was floated in sync documentation. I would like to move forward with this idea because again, I think this working group has a lot of participation. There's a number of people that are looking to get more involved and may not be able to make this meeting today but want to get more involved in supporting the website. So again, I think there's a lot of participation here and should be meeting every other week so we can stay as up to date on all things website and documentation related as possible does anyone + +Tyler Wright: Concerned about having some folks from the documentation working or a Sig going this weekly meeting and just having a combined website and documentation meeting. + +Tyler Wright: Okay, I see one So I don't see any thumbs down that's leading to believe that nobody has any issue with that. Cool starting in two weeks again. I'll drop a message and Discord just to remind folks but I think starting in two weeks. We'll start to have more folks in the documentation side here as well to go over documentation updates improvements Etc. + +Tyler Wright: continuing to move along. I know this is something that we use as a source of Truth. So I'm happy to share my screen actually real fast, but there are a number of issues in the website repo. I've tried my best to close issues that I believe are done, but does anybody see any issues In the website repo that do not need to be here anymore or is there any issues that are live right now that? Anybody wants to discuss. + +Tyler Wright: Here's I know that you are talking to me about closing some of these issues. Is there any issues if you still see here a close a couple recently that I saw PR's were already merged for and reference but for some of these other issues, I didn't see any PRS attached so led me to believe in the work hasn't been done, but I could be wrong about that. + +Bold Panther: setting it's fine so far. I don't see any issues That are pending to be closed. So I think everything is closed and all the issues that are open right now are open issues. So if I find any I will close the ones later + +Tyler Wright: Okay, excellent. there are a couple of issues that have been added again. I've been for issues that are related to docs. I've been trying to put a label or documentation just so it's easier for people to see and track. + +00:05:00 + +Tyler Wright: Are an Insider and Akash Community member has been talking to me about ways. They want to get involved with documentation. + +Bold Panther: Okay. + +Tyler Wright: I think they've already submitted a PR and we'll continue to submit more PRS. There's a couple of actually insiders that have showed interest as of recently and getting involved with documentation. So again, there are a number of people that'll look to get involved with documentation the website but one of the issues is around the Prater act with the acquisition the Prater app documentation isn't currently on the constant Network docs. I know there's going to be significant changes to the way the Prager app looks and feels in the future as a part of the console 2.0 product strategy, but there is some thought about at least having their current state today. Just so people can find a documentation one place. Does anyone have any thoughts concerns about this particular issue? Go ahead Denis. + +Tyler Wright: + +Denis Lelic: Thanks, I've briefly talked about greater dogs with the voluntar. + +Tyler Wright: Before we look to continue to assign it to somebody and get the work done. + +Denis Lelic: I'm just gonna connect again with them to see if they have any plans to migrate those dogs or at least adopt those dogs to match the console So we have a clear Direction on this thing. + +Tyler Wright: Yeah, if you could show them this issue and let them know that there is a team member willing to do it if they feel like it might be too difficult. Then we can have this Community member work on something else. There's also another member of the parade or team that's not part of the overclock team. that is an Insider about Saul that may be able to help with this as well because I believe he's previously done ux work and continue to do ux work for Crater. So there's something to also talk about but if you can Follow up with bigger and default I'd be amazing. + +Denis Lelic: Cool. Yeah. + +Denis Lelic: Yeah, so there's a bunch of new issues mostly regarding the docs. + +Denis Lelic: Just going through them. Yeah. + +Tyler Wright: There's also a couple of old issues that I would love to see. worked on I know that Denis is working on 9 million things. + +Denis Lelic: the number one + +Tyler Wright: Just the number one. + +Tyler Wright: But there are a number issues. And again, in Sig design, we had some conversations about folks that want to get more involved with helping again design some of these experiences so that they can be implemented. But yeah, I just want to shout out that again. There's anybody wants to get involved and some of these things that feel free to + +Denis Lelic: Yeah. Thanks time anyone who's interested can also M me on Discord. I'll be happy to take you through all this stuff. We've been working on and continue to work on. + +Bold Panther: So I think at this point we should address the number one issues that is about streamlining. That's the information related to the community and development. So we divide the problem information between these two pages a development or related content being in development page and the community related things in being in the community page. So I think this is something if the otms busy this is something that I can. Data ui4 and can start taking it forward for the implementations. + +Denis Lelic: Yeah from my side tie. I feel let me I'll just go back as well to couple of other issues. + +Denis Lelic: One is like this unified experience for providers. I think that was created by Zach so in the next couple of days + +Denis Lelic: I'll try to. Bring that issue back to life and just provide some ideas Solutions there. I think I already did a couple of weeks ago, but I'll just go through it again to see what other options there and how can we improve that? page and the same goes for + +00:10:00 + +Denis Lelic: Pricing I know Zach I think after accelerate happened, we should do something about the pricing page. The information is a bit kind of scattered and behind a couple of curtains. So just try to bring that up front. So it's informational easy to reach and so on and so on so maybe from top of my head just like those two issues. And of course the community number one issue as well always on my mind. + +Zach Horn: Yeah, both of those would be great… + +Bold Panther: Yeah. + +Zach Horn: which is the provider issue you're mentioning is that the old issue that was created a long time ago kind of towards the bottom of the list. + +Denis Lelic: Yeah, I just found it. + +Bold Panther: No. So no,… + +Denis Lelic: Here it is. + +Bold Panther: so it's related to the issue that's been created by one of the community members. I think yesterday. It's extreme in the information about the provider on the tops. + +Denis Lelic: not + +Denis Lelic: No, no, it's not the docs related this one. It was created by Zach. So yeah you're right. It was way back in February, so what we kind of discussed this in the comment section here in the GitHub and in the threads and so on but I'll just try to keep this thing alive until we reach something. Everyone is happy with and it's ready to implement. + +Zach Horn: Yeah, I would love to move on this and just at least put some work behind it. And Denis you're not gonna chat offline if you need anything for me on it because there's two main things one is we need to streamline the provider pages. So essentially when somebody lands on the website, they should be able to easily see who are the providers on the network and if you jump into that issue the one that tennis linked these two screens are the most important by long way. So we just need to make sure that people can get to these two visualizations as quickly as possible because this is what people want to see it's like ing. This provider map with the grid which is excellent. And then the locality map you can see where the providers are around the world. So they're a little buried at this point and that's I mean we did a lot of work to just get the website off the ground. Yeah. Thanks time. + +Zach Horn: We did a ton of work to get the website off the ground, but my one piece of feedback is the things are a little bit scattered at this point, things are buried behind layers of navigation. So some of that's okay in certain instances, but I do think for some of these very important views that people want to see right away. We should just bring them closer to the surface. so yeah, I'm with you Dennis. let's move on this and just get it done. What was the other issue that you brought up? There was a provider streamlining and then the pricing right? right + +Denis Lelic: Pricing we kind of talked through mostly DMS and I think there was no yeah,… + +Bold Panther: slide + +Denis Lelic: I think Pierce was involved there as well. So + +Zach Horn: I'll Do you mind Denis by just give you my one piece of the context of why that even came up at all? So I was at consensus with a couple weeks ago Greg did a presentation. + +Denis Lelic: Yeah. + +Zach Horn: On one of the side stages and he was doing a workshop and he ran into the same issue that I've actually run into a couple times, which is you're looking for not the GPU pricing page. That's obviously in the nav that's very easy to find but the one that compares to the other large Cloud providers, the one I'm talking about where you can enter your resources and it shows that it's 85% less or whatever the percentage is. that one is pretty hard to find on the website and Greg was having trouble finding it. I've actually had done the same thing when I'm talking to somebody. I just can't find it. So anyway, those are the three. + +Zach Horn: The provider grid map the locality map and then the GPU pricing Pages obviously very important. But also that other one that's gonna be one that we should lean into strongly going forward because I can just tell you from talking to a ton of people at these events. That's the thing that catches people's eyes. They're like, okay, I can tell you kind of resources. I want to run. How do you compare on price? So All that to say I'm with you Denis, let's move on this and just claim this huge. + +Bold Panther: Yeah, so I have a thought on how we can tackle this issues while also keeping the GPU pricing CPA top of the network. + +Zach Horn: Okay. + +Bold Panther: So what we can do is we can combine both the sections in first talk. We keep the general pricing in the second half we can keep the GPU pricing whenever the user clicks on GPU pricing. We have the hashtag functionality. which takes them to the pricing phase and automatically scroll down to the chipazing section. So I think this is something that we can do from the ux perspective. This will solve all the issues accessing the general pricing ways. Also the GPU pricing at the same time. + +00:15:00 + +Zach Horn: Okay, that sounds great. let's move forward and just mock it up on a staging site and then I'll get that In front of Greg because he feels very strongly about the GPU pricing page. So I just want to make sure he's aware of any changes that we're gonna make to it. But that sounds great to me. I think one place makes a lot of sense. + +Bold Panther: And in that case we can like in the pricing base. + +Denis Lelic: yeah, I + +Bold Panther: What we can do is as well be combining both the sections into a single page and it's going to be a dedicated page. We will not keep the site navigation that is present about which so it will be a complete pricing page in the first half days of pricing comparisons in the second update is GPU price. So it will also make it visually more appealing and also it will not break the Aesthetics about the current price in Pages if someone clicks on HP pricing City + +Zach Horn: That sounds good to me. let's mock it up, but it on a staging site and go from there. + +Bold Panther: Yes, sure. + +Zach Horn: The other thing views that I'm just gonna run by you this shouldn't affect anybody but for some of these pages, I think I'm just gonna jump in and do some PRS that they copy. Is that going to affect anything on your MPS just in there updating stuff. I think I can navigate the code base well enough, so I think there's some of this that I can just do as opposed to, having us to coordinate. + +Bold Panther: So can you elaborate a bit when someone contributes and copies to PR or something like? + +Zach Horn: No, no, I mean update the copy the words on the page for some of these. I want to go and I just change some of the language around. + +Bold Panther: Yeah, no worries. you can change it. So whenever we contribute to the website we first sync in with the main website and then only we start Computing so it will not create an issues for a scale. + +Zach Horn: Okay, sounds good. + +Bold Panther: + +Denis Lelic: Yeah, I agree with you guys. I would only suggest we kind of create an issue for this. So we just have something everyone can track or visit to see What are we working on and… + +Zach Horn: Yeah, great. + +Denis Lelic: so on and so on? + +Zach Horn: It's a tire you sharing screen right now. If so, could you scroll down and just put the price comparison on screen? The one right above it. That's action right there. + +Zach Horn: Is this okay? So it's funny that we're talking about this now. is this the one I'm thinking of I thought there was a modal where you could enter your Resource information, is that a different one or is That's okay. + +Denis Lelic: Yeah, it's this one at the top. + +Zach Horn: I see got It was offer a second. Okay, perfect. Yeah, this is great. I mean you could use a little bit of a redesign but + +Denis Lelic: Yeah, I agree with that. We actually had pierced… + +Zach Horn: Yeah. + +Denis Lelic: you remember we had a design with sliders but at the moment. back then Let me just try to recall it. I think it was not possible with the API. + +Denis Lelic: so the slider meaning CPUs memory and storage would be just with a slider so you can just easily change the number so you don't have to so it would go 1 to 100 really fast or thousand whatever we limit. each of the + +Bold Panther: It's possible. I think we did within discussed about this. I can't recall but I think there is no issue with the API. Even if you remember the slider we have nothing but change a bit slider. We are nothing but changing the numbers behind the scenes. So there is no limitations of the API. We can implement the slightest. It's required. + +Denis Lelic: Okay, cool. Yeah, I have some ideas here. So maybe we just continued this discussion and + +Denis Lelic: And the issue we're about to create. + +Tyler Wright: Yeah, that would be great. + +Denis Lelic: stupendous + +Zach Horn: come on Ty give us an adjective. You got a one-up student on this. + +Tyler Wright: I can't it's too good. + +Zach Horn: alright. + +Tyler Wright: I'm not the content King Zach. + +Zach Horn: that prayer + +Tyler Wright: I don't have that ability, + +Zach Horn: It was my title from yesterday. I have content King and was the other one. the branch. + +Denis Lelic: Brian Shepherd + +Zach Horn: My business card gets longer every day. + +00:20:00 + +Denis Lelic: Yes. I mean we gotta collect those. + +Zach Horn: Okay. + +Denis Lelic: Yeah back to the website. + +Zach Horn: I think for microspective if we get those two views, in the first issue plus this pricing model integrated with the GPU pricing page and then we get all of that surfaced. That to me is the highest priority thing we can do with the website. There's some things on the content side that we need to do as well. But that's more of my plate than anybody else's. + +Zach Horn: But what really an ideating just a little bit that we can move on. is if we surface those views the ones we just mentioned. We can get to a place where we're actually starting to address really tangible pain points for people and this comes from talking to people at events. it all comes back to how many providers do you have on the network? Where are those providers in the world? What is your pricing? can I see my pricing on Akash relative to some of these other Cloud providers? So we start to build all that out and we can even do some work on the homepage of the site to lead people through that flow that we're essentially checking against people prospects when we're talking to them in person. I think we're in a different place a better place. + +Bold Panther: if I + +Denis Lelic: Yeah, I agree. + +Zach Horn: That's it for my side on that we can move along. + +Tyler Wright: I think these are all great points. I just want to confirm Denis. Are you gonna own creating the issues that we just discussed here so we can continue to track them or was it Peter? She was gonna do it. I just want to see who's gonna own. It just go we can continue tracking because I think we're on the same page as what the priority and the next order of operations for is for and I appreciate exactly talking about The Real World experience and how these things play out during events and elsewhere, but I just want to make sure we're continuing to crack it and then deliver on it, + +Denis Lelic: Yeah. I can create it. So no worries. + +Denis Lelic: Okay. + +Bold Panther: So I have a question for So as a Zach shared the data sheet about the website analytics. So I just have a few questions. So as I share I dropped in the link where we can have a visual saw the general website analytics the users Etc training more refined manner. As Jack pointed out. So I just want to ask what you want specifically what modifications to invade in the default version of it. + +Zach Horn: So let's chat offline about that. There are some. + +Bold Panther: Yes. + +Zach Horn: There's some thoughts there. They're going a couple of different directions basically at the highest level. all that we need for the first phase of what I was mentioning the other day is That we just need to clean up some of our data sources so that everything is current. We're only pulling active data sources from active properties and then just start to structure out GA and then we have some of these liquor reports that need to reflect the accurate information. it's not too much like technical GA work. It's really just data cleanup more than anything for this first phase,… + +Bold Panther: that + +Zach Horn: but I'll drop you a note right after this weekend get into that. + +Tyler Wright: Cool, are there any other? Website items that anybody wants to discuss this might be actually small time small fries. And I know this is something that we could change but I was wondering if it makes sense to add 40 90s to this announcement bar at the top being that they get so much traction on the network even relatives to the a6000s again. I was just looking for the website for two seconds and just thought about that. So it may not be anything that anybody cares about or may not be that necessary, but just want to shout it out in the website. + +Zach Horn: Yeah, the only on a technical level the utility absolutely we're getting crazy demand for forty nineties. I mean really like shocking demand. On the copy side. it's just the rule of three so you have to either a place one of those or break the rule. Not opposed to it. you'd have to go h100 a100 a6000 and 40 90 which is kind of clunky, but from the utility of it should be surface 4090s that absolutely + +Tyler Wright: I think that's a good point content King. So I was just again putting out that however, we decided to move forward I'm fine with but as we mentioned 40 90s are Hot Springs. + +00:25:00 + +Zach Horn: They are they are. + +Denis Lelic: Yeah, just content King. Zach here one of those Game of Thrones guys where when they introduced them and they go with a bunch of names like + +Zach Horn: man, that's too funny. Yeah, exactly. that's precisely going for some Lord of Westeros ruler of the whatever. Yeah content King ever. + +Denis Lelic: the branch Shepherd + +Denis Lelic: Okay. + +Zach Horn: Yeah. + +Tyler Wright: here something actually an issue that know. The hero was looking at as well and talking about but I know we've moved it down the priority list so we can keep it there is around contact page. I know they actually hero is going to be helping contribute to console as well and how getting acclimated there. But I just want to say if that's something this issue the contact page is still something that's on hold obviously is with the priority than the GPU provider. + +Tyler Wright: Stuff that we're talking about earlier, but I just wanted to see if there's something that can be moved forward Tandem with all the stuff that's being done. Maybe hero could take us on or if this is something that we should just continue to put on pause for the time being. + +Zach Horn: What Tyler can you scroll down to Heroes lower in the thread here the mock-up. Yeah. + +Zach Horn: So the two questions one, where does this go? I probably took a catch all email. + +Denis Lelic: Yeah. + +Zach Horn: Type, okay. + +Tyler Wright: Believe that's the intent. Yeah, or I believe there's an option where you can have a number of emails you can have a BD email billing email whatever and… + +Zach Horn: right + +Tyler Wright: then it'll go to the respective email. + +Zach Horn: we can continue this in the discussion. If we want to, idea async on this. + +Zach Horn: Entire unit talked about this little bit offline. I'm not opposed to this in any way. + +Tyler Wright: Yeah, yeah. + +Zach Horn: The only question is what is the flow? So I do understand there's lots of people, that they're used to the kind of web to it for lack of a better term flow where they land on a website. They want to see a contact page. They're just used to doing this and dealing an On the flip side. The question is support for that email address and I think you felt strongly that that's not going to be an issue. you'll fail that way? + +Tyler Wright: Yeah, I do still feel that way. And if we find that any of these become an issue, then we can I remove it from this contact page. I think for now if there's more than one point of failure, so if it's going with the email is going to one person. I think that would be less than optimal. But I think in many cases these will be going for a number of different people can make sure that everything followed up on… + +Zach Horn: You sure. + +Tyler Wright: but I do understand your hesitancy because then they'll be another touch point that has to be managed and maybe things get lost in. but it's a set of balancing act of to your other point. Some people are used to doing this and then may not be even willing to do the Discord telegram route, … + +Zach Horn: Right. Yeah. + +Tyler Wright: or get home. + +Zach Horn: I don't disagree with that in any way. I would say s similar to the other thing. What's mock up like a defined modal for this figure out where we want to put it on the site get it in staging and set up the infrastructure for it and then go from there and see if we can buy-in from that for folks internally. + +Tyler Wright: cool that makes it I'll drop a comment in there and hero maybe just keep on looking at it when you have some time. + +Tyler Wright: That's all I had of things on issues. And again the structure of the working group as we move forward that I wanted to discuss. Is there anything Pearce in terms of pull requests that haven't been merged yet that you want to talk about are there some of these that just need additional notes or have you given comments and just waiting for people to follow up? + +00:30:00 + +Bold Panther: So there is one issue like that is open for quite some type. So as you can see the second we are at icons to the menu item networks. So The second pair so I just want the next to just provide the name of the icons that are present in the UI. So hero can just edit those icons in this. Yeah. + +Denis Lelic: And I consider the menu. Okay, I see. Yeah, sure. + +Denis Lelic: Sounds good. + +Bold Panther: That's all and this is one new issue. There's been created by things engine and the pr is being created by one of the community members at the dogs with the instructions to import the existing wallets the latest fear. So it's just a small mistake. So I have permitted the town domestic to fix once it is fixed. I will just most of you. + +Denis Lelic: cool + +Tyler Wright: Thank Again peers, there's a number of people that reached out to me publicly and privately from the inside of just generally new community members that want to get involved with the docs and the website. I push them towards a readme file. So they learn how to contribute and they're doing it the right way, but I believe is going to be a number of new contributions from people that will start joining this meeting sometime a next couple of weeks. So again, feel free to continue to give the constructive quality feedback as we've all talked about with the website revamp. We want to keep it to the same standard is right now, so if people aren't meeting that standard just continually comments until they follow through and exactly where they need to before merging. I think Hero has done a good job of that. I think there's other people in the community and then a good job of that and that's why there's their PR so that merge so we'll keep that consistent. + +Bold Panther: If I always make sure that the priests are coming to the websites are of high quality. If there are issues with the code or implementations all the pr might fail and if the pr creators or the contributors weren't able to fix the issues. So in some of the cases I do myself and then most of yours if they are of high quality and great additions to the website, but yeah, this is the process. I follow before Modi any of the peers to the website. + +Denis Lelic: Sounds good. + +Tyler Wright: Excellent. Thank you. + +Denis Lelic: So I think Pretty much went through all of the issues and we got some new coming up. So. The pricing issue I'll create that one and I'll follow up on the providers issue Zach created a while ago. So those are mine two action items. + +Denis Lelic: yeah, that's it for my side I guess so if anyone else has Something at least. Yeah, we still have some time. So if anyone else has some many questions or would like to know something about the website or the working group. Feel free. to ask or to talk + +Denis Lelic: Okay video just drop. Yes, not so. + +Denis Lelic: Yeah, but I think we can wrap it up for today. + +Tyler Wright: Yeah, think we're good. But I think it's a very productive meeting and we'll take next steps on those priorities for the website that Zach had mentioned and continue to go from there. + +Denis Lelic: + +Denis Lelic: So thanks everyone for joining today. I think we'll see each other in two weeks from now in a slightly different format. It's actually the same we're just adding a topic of Akash talks. So we'll see how that goes. Maybe we split the meeting first everything about docs content and so on and the other half we can talk about the UI ux + +Denis Lelic: Yeah bold instant action item pricing and provider. Yeah, that's right. Yeah, so we'll see each other in two weeks. So thanks again for joining today. + +Tyler Wright: Thank… + +Bold Panther: thanks. + +Tyler Wright: Talk to you guys soon. + +Zach Horn: thanks guys take + +Denis Lelic: Thanks. Bye. + +00:35:00 + +Rodri R: bye guys + +Meeting ended after 00:46:25 👋 + + + + + From 61c58fda62be56844b9b814c23b942badf731819 Mon Sep 17 00:00:00 2001 From: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Date: Fri, 12 Jul 2024 21:01:55 +0000 Subject: [PATCH 54/55] Create meeting notes for wg-website #30 (#596) * Create meeting notes for wg-website #30 Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> * Update 030-2024-05-16.md add transcript and video recording Signed-off-by: Drinkwater --------- Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Signed-off-by: Drinkwater Co-authored-by: Drinkwater --- wg-akash-website/meetings/030-2024-05-16.md | 627 ++++++++++++++++++++ 1 file changed, 627 insertions(+) create mode 100644 wg-akash-website/meetings/030-2024-05-16.md diff --git a/wg-akash-website/meetings/030-2024-05-16.md b/wg-akash-website/meetings/030-2024-05-16.md new file mode 100644 index 00000000..85e11b4f --- /dev/null +++ b/wg-akash-website/meetings/030-2024-05-16.md @@ -0,0 +1,627 @@ +# Akash Network - Akash Website Working Group (WG) - Meeting #30 + +## Agenda +- Akash Accelerate Page and Speaker Order +- Visual Updates and Accessibility Improvements +- New Issue: Contact Page Feedback +- Documentation Issues and Improvements +- Additional Issues and Assignments + + +## Meeting details +- Date: Tuesday, May 16, 2024 +- Time: 08:00 AM PT (Pacific Time) +- [Recording](https://dpisfxnpneb3dvtssughllgmsyn6a7qasqh62lwtpuvm3xaomcnq.arweave.net/G9Ei3a9pA7HWcpUMdazMlhvgfgCUD-0u030qzdwOYJs) +- [Transcript](#transcript) + +## Participants +- Bold Panther +- Denis Lelic +- Tyler Wright +- Zach Horn + +## Meeting Note + +- **Introduction:** + - Tyler Wright welcomed everyone to the bi-weekly working group session for the Akash website. + - Emphasized the importance of these sessions for discussing and improving the website. + - Encouraged participation through the Akash website channel on Discord. + +- **Speaker Order for Akash Accelerate Page:** + - Denis Lelic brought up the need to order the speakers on the Akash Accelerate page. + - Suggested Eric and Greg should be prioritized but asked for further input. + - Zach Horn offered to rank the names and send the list to Denis for adjustments. + +- **Updates on Portraits and Titles:** + - Denis mentioned ongoing corrections to new portraits, with some specific issues highlighted. + - Missing title for David Johnson noted; a placeholder title "CEO of bread Dev" used temporarily. + - Zach stressed the importance of confirming titles directly with individuals and avoiding assumptions. + - Amanda is actively verifying speaker information via emails. + +- **Feedback on Team Titles:** + - Zach proposed a title change for Neo and Chang to "VP of Product and Engineering" with an ampersand. + - Suggested the title "Core Team Akash Network" over "Creators of Akash Network" for consistency. + - Sought external feedback from Bold Panther, who confirmed "Core Team Akash Network" is clear and appropriate. + +- **Design and Update Process for Akash Accelerate Page:** + - Denis updated Piyush on the timeline for receiving updated information and illustrations. + - Discussed the need to finalize the run of show and suggested it might be ready by the end of the week. + - Zach agreed on the importance of updating the schedule and ensuring it's visible, even if it changes later. + - Confirmed Amanda as the MC for the day. + +- **New Issue: Contact Page for the Website:** + - Denis mentioned a new issue raised about the difficulty of contacting the core team through the website. + - Piyush suggested implementing a simple contact form accessible from the footer, allowing messages to be sent to different departments. + - Zach expressed concerns about the potential for spam and the complexity of managing emails, suggesting Discord as a more responsive channel. + - Tyler proposed a contact page with dropdowns for specific queries (e.g., Business Development) that could send emails, while technical support queries could be redirected to Discord. + - Bold Panther suggested a common contact page with sections for different types of support and outreach, integrating existing support elements and social profiles. + - Agreement to map out the contact page more thoroughly and prioritize it lower for now, considering the other ongoing high-priority tasks. +- **Presentation of New Visuals for Documentation Integration:** + - Bold Panther presented visuals for two new documentation issues: Quick start section for "How to integrate with the Akash Network" and "Deploy Hello World in five minutes or less." + - Tyler emphasized the need for a clear and accessible guide for projects to integrate with Akash Network. + - Zach supported the importance of case studies and prioritizing them in documentation. + - Discussion on managing bandwidth and prioritizing tasks. + +- **Discussion on Quick Start Guide for Deployment:** + - Tyler emphasized the need for a one-pager or video guide on deploying via CLI and console. + - Zach agreed on the importance of a simple and quick guide for new users. + - Bold Panther suggested having someone with experience in Akash create the content. + - Tyler proposed assigning the task and prioritizing it higher than the contact page. + - Agreement to possibly add the quick start guide to the Essentials tab on the website. + +**Implementation of New Effects on Icons:** +- Hero initiated changes to icon hover effects, making the color change to red. +- Denis appreciated the initiative, confirming that the changes are pending final approval and merge. +- Bold Panther is addressing bugs noticed in Hero's pull request before merging. + +**Documentation Issues and Improvements:** +- Bold Panther discussed improvements to the documentation pages, such as auto-opening the first page when clicking on sections. +- Noted a bug where refreshing the page defaults to the homepage, which is being fixed. +- Hero’s pull request is under testing before being merged. Bold Panther is ensuring all issues are resolved. + +**Additional Issues and Assignments:** +- Tyler proposed inviting Hero to these meetings for better coordination, despite language barriers. +- Bold Panther emphasized Hero's daily contributions and active engagement in resolving issues. +- Tyler mentioned a new issue regarding updates to the console page, to be created and managed on Discord. If Thomas cannot handle it, the task will be outsourced to the community. +- Denis, Zach, and Bold Panther confirmed there were no additional issues to discuss. + +## Action Items +**Denis Lelic:** +- Review and finalize the speaker order based on Zach's rankings. +- Follow up on portraits and titles for Akash Accelerate speakers. +- Provide Piyush with the necessary information and illustrations for the Akash Accelerate page. +- Continue improving accessibility graphics for the Engineer Docs. + +**Zach Horn:** +- Assist Denis with the ranked list of speakers. +- Help finalize the run of show and ensure it is updated. +- Provide feedback on the contact page idea and help map it out. + +**Tyler Wright:** +- Create a new issue for the console page updates and manage it via Discord. +- Discuss the new issue with Thomas and reassign if necessary. +- Ensure consistent use of "Core Team Akash Network" in all documents. +- Invite Hero to future meetings and ensure he is informed about meeting schedules. + +**Bold Panther:** +- Continue addressing bugs in Hero's pull request and ensure it is merged after thorough testing. +- Work on visual updates and accessibility improvements for the documentation. +- Coordinate with Hero on daily contributions and ensure all issues are properly addressed before merging. +- Develop and refine the quick start guide for deployment with input from experienced team members. + +# **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 working group for the Akash website. It is May 16th 2024 during these working group sessions that happened by weekly the group gets together to go over any issues in the website talk about anything that needs to be improved or updated. Again. The website is the main Hub past that Network for all things related to Akashi Network the docs also live under this website repo. So again, if anybody wants to participate in finding issues or helping improve the website, feel free to join this working group session that meets weekly around this time as well as get involved in Discord the working group of cost website Channel. There's a number of issues that I would like to discuss today, but I'm going to kick it over. + +Tyler Wright: To boss man Denis to see if there's anything he wants to covered agenda wise before we get into some of these issues. + +Denis Lelic: Yeah. Thanks one thing really quickly + +Denis Lelic: regarding the page Akash accelerate. So I was just wondering about the speakers And what order should we present? So I didn't really put much thought so I was just thinking like Eric. + +Denis Lelic: Probably should be on top somewhere like the first line maybe Greg but For the rest of them. maybe Zach you have the most awareness who's the I don't want to say most important but Who do we want to present first Maybe? + +Zach Horn: Yeah, that's right. I mean we do have to order these. Would it be easiest if I just rank the names and then you can adjust? Okay. + +Denis Lelic: Yeah, maybe you can just DM me the list. So we got the first batch of these portraits. + +Zach Horn: Yep. + +Denis Lelic: There's an extra round of Corrections going on at probably now as we speak or so + +Zach Horn: I was going to mention that as well do we know which ones are being worked on? + +Denis Lelic: Pretty much all of them. from The New Batch, so Maybe Lexus Some of them I have two thick limes and stuff like that. + +Zach Horn: Yeah. + +Denis Lelic: So David needs some work here. + +Denis Lelic: Yeah, so I just forgotten name The illustrator to make thing Corrections, so I'm hoping I'll receive those today next to that I have. I'm missing a title for David Johnson. And we're still kind of waiting for a couple of them. So another I just put CEO of bread Dev. but we're still waiting for his information + +Zach Horn: Yeah. That is correct. But yes, we do need to confirm. And just while we're on the topic. going forward for these just know assumptions on titles. I had to talk with Greg about that the other day we just have to confirm with these people directly. It's a little bit of a pain because we have to go through and contact people if we don't know, but we just have to do it if you need me for anything on that. Just let me know. I can push things along. + +Denis Lelic: Yeah, Great. Yeah, I know Amanda has been sending emails and stuff like that or the speakers Just to verify all the information we got from them. So yeah. + +Zach Horn: One which is what we're looking at this page one quick change we could make is for our team titles. So a Neo and Chang title titles are correct a Neil's preferred as a VP of product and… + +Denis Lelic: Yeah. + +Zach Horn: Engineering so you can just do VPN product and Engineering overclock Labs do an ampersand for hand. + +Zach Horn: And then this is the tricky part. I would suggest core team Akash Network. Like we're doing for the business cards that whole the hype in creators of I just don't love but this is minor we can talk about it. Later. Just thinking out loud while I'm looking at the page. + +00:05:00 + +Zach Horn: I don't want to derail at all but huge while we have you just a little feedback. I'm honestly curious when you see core team Akash Network like that. does that make sense to you? do you think that'll make sense to people that aren't us, like what that means. + +Bold Panther: Can you repeat the first word? what did you say when you say Decap? + +Zach Horn: Yeah. Yeah, you see where it says core team Akash Network in a title there. + +Bold Panther: mmm + +Zach Horn: I'm curious. does that make sense to you and you think it'll make sense to people outside of the overclock Labs team? That's what something we've been talking about. I'm just looking for a little outside feedback. + +Bold Panther: So yeah, I think that's pretty clear. when we say creators of team Akash Network. It doesn't make sense these request belongs like These are the speakers who are the gold team of Akash, and then we are mentioning the roles of others as well in a particular organization. + +Zach Horn: Yeah. + +Bold Panther: So, I think it just makes sense you For me, both were dealings make sense, either creators of core team Akash network, but as we are mentioning core team everywhere. So I think coding doesn't make no sense as compared to creators of akashion. + +Zach Horn: Okay, perfect. Yeah, but I feel better. At least we have one point of a outside feedback. + +Denis Lelic: yeah, it's Yeah,… + +Zach Horn: Alright, so sorry Denis back to you take it away. + +Denis Lelic: so Pierce, I know you've been waiting. + +Denis Lelic: On this design just to update the page. So as soon as I have all the information regarding, titles and updating those updated illustrations all dmu. It's not probably going to take much effort in time to do the update. + +Bold Panther: Yeah. + +Denis Lelic: Everything is pretty much there. So we just need to populate with proper and… + +Bold Panther: Yeah. + +Denis Lelic: correct information. + +Denis Lelic: Yeah. + +Bold Panther: So I as soon as I get it will be hardly truths of daily thing. So just driving on the film and + +Denis Lelic: Okay, Yeah. The other thing is we don't have the final. Run of show yet. So I was just thinking if we should leave it. this kind of blurred a little bit because we're still kind of trying to figure out the + +Denis Lelic: Who's going to talk at which time and so on and so on and so on? So, what do you guys think? we can do first batch updating the speakers and second batch. I'm not sure if this is gonna happen this week, but in the beginning of the next week, we should update the Run of show. + +Denis Lelic: What do you think guys? + +Denis Lelic: Zach I know you've been involved in all of this stuff + +Zach Horn: Yeah for what I would say Is that there's some changes going on currently, so I'm in two minds about it one. We can update as it comes in and just understand that it may change and that's probably fine. I do agree that we can't have a coming soon forever. yeah, I'm Exactly. + +Denis Lelic: Yeah, I mean next week. + +Zach Horn: Yeah coming soon until the day before. + +Zach Horn: Yeah, let me do this because there's some conversations going in the background around what the order of some of these things are going to be and there's some shifts happening at the moment. Let's see if we can get to a roughly finalize schedule by the end of today. Let's call it the end of the week. Just be safe under the day tomorrow and… + +Denis Lelic: Yeah. + +Zach Horn: then if some of the major things that we're working on now get sorted we can just update and make it visible is if it has to shift from there. that's probably fine. I don't think anyone's gonna be like, keeping receipts on this or anything so + +Denis Lelic: Yeah. Okay, cool. + +Zach Horn: One quick thing for MC of the day that's going to be Amanda and… + +Denis Lelic: Yeah. + +Zach Horn: that's locked in so we can just update that. So that's an easy one we could switch. + +00:10:00 + +Denis Lelic: Okay, cool, so, I think that's everything and that's happening on this front of Akash accelerate so I think that. next action items are updating all of the information portraits illustration and so on and hopefully tomorrow we're gonna have a run of show + +Denis Lelic: And some shape or form maybe not final but yeah. getting that + +Denis Lelic: one sack + +Denis Lelic: just want to run through the latest. issues so website repo + +Denis Lelic: Okay, the new issue has been created by fresh 44 minutes ago. So users have mentioned that it's difficult to contact the core team through the website was wondering if we can add a simple contact page to send messages to different departments. This would be a quick thing. It can be a page accessible from the footer. We can Implement and we got Piers here replying. we can Implement a functionality that allows users to send messages to record via email through a simple forms Mission. We do also have a support page to reach out. Okay. + +Zach Horn: Okay, let me jump in. + +Denis Lelic: Yeah. + +Zach Horn: I was waiting for this one. I was stretching and prepping. + +Zach Horn: so good feedback. + +Zach Horn: Here are the two issues. one I get that some people are more comfortable with email than with this chord or Twitter and all that. that said those channels are gonna be 1,000 times more responsive than catch all email addresses the obvious thing that's gonna happen with this is we're going to put in a bunch of emails and they're gonna get unlimited much spam. And there will be some legitimate messages in there, but then it comes down to our people checking the email who's owning the threads in the email. So what we're proposing here is going to create a ton of fractionalization of Outreach. I've been of the mind up to this point that although we're forcing some people who would rather email to go to Discord that keeps it in one place and we have support there. So that's my feeling on it. I'm not. + +Zach Horn: I'm not going to throw all my weight against this but it's not quite as simple as it was made out in the internal discussions and here. I'm open to finding a solution but I go ahead because I'm clear. I'm curious what you guys think. + +Tyler Wright: I agree with many of your points. So here's how I have it going, in my mind. Basically have a contact page that has a couple of drop-downs some of those being Business Development, and then it lends you lets you send an email if you're looking for technical support. It won't let you send an email and it pushes you into Discord. + +Bold Panther: actually just + +Tyler Wright: So it would be specific things and then on the email front like we do with a number of different emails. What I think should happen is these emails whether it be Business Development or whatever other ones we let people send messages through it goes to a number of people within the core team. + +Tyler Wright: and then as an ownership standpoint again, we could either this is something that I would see I'm always looking at those emails anyway, and I can continue to push those forward in different directions or somebody else could but I understand exactly what you're saying My only pushback is there are a number of web2 folks that don't seem to be able to hop over that hurdle as easy as it is, and if there's a way to catch some more of those and to your point about spam if there's a way to kind of Filter that out through some sort of a simple robot system or something. That would be great because I do think that would be an issue. But I'm of the mind that it may just be worth it for that web to audience that I know. + +00:15:00 + +Tyler Wright: Many people within the Cosh Community have talked about trying to capture and I think it's a challenge, I mean, it's not technically speaking. It's not a challenge for somebody big. Alright, I just got to go and Discord and then I can get my question answered in two seconds, but it seems to be a hurdle that people from traditional web to can't seem to hop over. + +Zach Horn: I'm with you on that. I mean obviously it is but here's the thing. if that's the cohort that we're talking about that is going to be the first of 50 hurdles. so it's like okay, we're going to get them over the first hurdle and then 49 more hurdles. So I agree with you. none of this is me be doing this but We do. + +Tyler Wright: Yeah. + +Zach Horn: The way it's being presented at this point. It's just not that simple and I don't + +Zach Horn: I don't want to take us down a path where? We put this in place and it just creates a ton of complexity that we've already done a great job of Outsourcing to the community via the vanguards. So What I would say is let's not rush on this one. Frankly. This is not priority to me. especially in the next two weeks we Call it 10 other things that are priority. This is not one of them. + +Zach Horn: The other thing that we will run into with this is the Evergreen issue of it's a decentralized network So when you say contact us, who are you contacting? You could get around that by saying the core team. But then that needs to be defined so if you land on Akash Network and you say you're contacting the core team, who is that? So that's an issue that's been on the table for quite a while. + +Tyler Wright: I agree with that point. + +Tyler Wright: I'm fine to slow this down for a couple of weeks. I just want to at least think about the problem. + +Zach Horn: Yeah. + +Bold Panther: out there Yeah. + +Tyler Wright: I know it's like a challenging problem Zach. I've not disagreeing with any of the points that you're saying, but I would just argue. Yes, it's gonna be 49 other hurdles. + +Bold Panther: of + +Tyler Wright: I agree with that wholeheartedly, but If we can eliminate the first one to at least we can get talking to them. And we can carry them over those hurdles or right now. It seems like they can't even carry themselves or understand to move around into discourse, and again,… + +Zach Horn: Yeah. right + +Tyler Wright: I'm only talking about some of that audience that we seem like we want to get everybody in the community like web 2 do you think come over the web 3 everybody seems to be talking about that same thing and then + +Tyler Wright: Yeah not. + +Zach Horn: Yeah, I got it. But an email address is not going to solve that although I do feel strongly about it as well. + +Tyler Wright: Yeah. + +Bold Panther: first + +Denis Lelic: Yeah. + +Zach Horn: Okay, let's do this because this go ahead push and I'm curious what you think as well. + +Bold Panther: So I think there is a lot of our lab between the support page and the contact page that we are thinking. So what here we can do is we can create a common contact us page which has all the support elements like we mentioned with proper cards for reaching out on Discord. There is an explanations and also another social profiles and for business developments as Tyler said we can have a small section where people are looking for business development Partnerships and all the form. So the state we can have a dedicated page for reaching out on socials and more like dedicated things. We can have small sections in here we can have just business development for the needs technical support and all we can just mention the socials that we already have and by inside this and gods + +Tyler Wright: Fish I think that makes sense to Zach's point. Maybe we should just spend a little bit of time mapping it out in the comments section here. I know that Denis has been busy and I know that have the structure of the site down. So maybe this is something that you can like kind of loosely again. This is probably gonna fall lower priorities and some of the other issues I have in here, but when the time is right, you can kind of map it out and we can have a discussion here. My only feedback is I believe that currently is a form and there was push back on the form is too many questions, So again like to Zach's point, maybe this is not something that we should be trying to prioritize because there's so many + +00:20:00 + +Tyler Wright: Something that seems seemingly is so easy to overcome things to be like a challenge for the audience that we're going after. + +Zach Horn: One thing… + +Denis Lelic: better but + +Bold Panther: should + +Zach Horn: what type form is even being referred to here. I'm on the home page of the website now. + +Tyler Wright: So this might be something we have to think through a little bit more over a period of time. So that I was trying to look for that last night. + +Zach Horn: Good. Yeah. + +Tyler Wright: would say if you have any thoughts about But yeah,… + +Tyler Wright: the support page and maybe the contact page come together drop those in here and I don't know. + +Tyler Wright: + +Zach Horn: So let's do this. + +Zach Horn: Let me take a run at this internally… + +Tyler Wright: maybe even do support some with some figma files… + +Zach Horn: because … + +Tyler Wright: because I know that again you have design resources on your team. + +Zach Horn: it's not getting into it on this call. But anyway, I'm not even sure what type form is being referred to here. + +Tyler Wright: I think Denis is working nine million things ahead of Akash accelerate… + +Zach Horn: And if you look on the home page. + +Tyler Wright: but unhappy to slow this down over next couple of weeks and… + +Zach Horn: We have joined the community with four links to channels to contact us. So yeah,… + +Tyler Wright: think it through more fully and… + +Zach Horn: let's just vet this internally a little bit. Let's slow it down for the moment. + +Tyler Wright: just have more time to think about it. Yeah. + +Zach Horn: It's a good idea, but we need to just be clear about how it gets implemented. + +Denis Lelic: Yeah, one thing regarding that feedback, I kind of laughed because whoever said that we've been trying to reach you for months, + +Zach Horn: Right, right. That was my thought as well. It's like, you've been trying to reach us for months and there's multiple contact channels right here. I mean that speaks to let me stop myself before I go too far. Yeah. + +Tyler Wright: Yes that I were all the same page there. That's why I keep on saying the web 2 audience seems to not be able to hop over a simple hurdle or… + +Zach Horn: Yeah. + +Zach Horn: … + +Tyler Wright: at least some folks that we heard from + +Zach Horn: web 2 but here's a link to Twitter right here. Do you know what the DM feature is, have you heard of that and want to anyway,… + +Tyler Wright: Yeah, yeah. + +Zach Horn: let's table it. + +Denis Lelic: Wait until they hear about crypto wallets. + +Zach Horn: Yeah, I'm with just it's a good idea. I do get that some people are just more comfortable with email and that's totally valid. We should solve for it, but This is I mean man, we have some high priority things on the table. So it let's just slow roll it for a couple weeks. And once we get back from a consensus, let's figure out how to do it. + +Denis Lelic: Agree, and I agree with Tyler and maybe we just keep this discussion alive here and under this issue If you have time in research to drop some ideas, I'm gonna have a look at this thing as well. + +Bold Panther: If you guys don't mind can I so I'm pretty much aware about … + +Denis Lelic: + +Bold Panther: the issues so it could be great if I can share other CNN share some of the study paid for the other issues. Welcome. + +Denis Lelic: Yeah, sure. + +Bold Panther: So yeah, I'm sharing machine. + +Bold Panther: So these are the two issues that is being opened by a type one is related to a little relevantages of shares for streamlining the first language understanding of integration with Akash Network. Another is a simple yet meaningful explanation could apply hello Industrial in five minutes or less with Some mentions on the blocks. So accordingly I prepared some visuals like how we can implement this. So on the docks on page we could have this quick start section where we just create two tiles how to integrate with the cost Network referencing a cost. Yes, and secondly deploy hello world is still in five minutes or less. So with the explanations, so I just want to get something back on this what you guys think about this. + +Tyler Wright: I start menu. I don't know how it differs from Essentials. But I guess it's faster. I can give some perspective on these if anybody needs those and why I created them if that helps. + +Tyler Wright: Okay, on how to integrate with Akash, there's a number of projects that reach out to us all the time and say that they've looked at our documentation and our Akashi, s is a repo and that's how a number of folks are integrating with Akash are also using Akash API. But it's not readily accessible on how they can integrate so that they have to have a conversation with us and then they find out about Akash and then they have to go back and do some due diligence to get up to speed and usually it's everything that they need. So we have a number of projects that are building or integrating with the Class via that way I'm not sure this necessarily needs to be on the home page. I actually liked what PS is put together. So I'll say that my personal opinion is I like those two tiles on the home page, but my thought process for this page was + +00:25:00 + +Tyler Wright: + +Tyler Wright: Just a page and documentation that somebody can see and… + +Bold Panther: just + +Tyler Wright: it's just simple copy, we kind of talked about some documentation where we have some header Pages. Whereas it's like if you want to be a provider and this is something more rely on Zach for just a higher level copy that leads into more technical copy, but it'd be great to have a page and documentation. That's just like if you are a project that's looking to integrate with Akash and leverage, deploy or be able to build providers. Here's how a number of projects are doing. They're using akashias repo. Here's They're using Akash API. Here's how you access it. And so now we maybe don't follow up with us. They just know they can go to documentation and This is the next steps and then they can go into specific channels and Discord or they can reach out to us for further help. So that was my thought process on the first one. So I'll stop there and then we can talk about the scl and five minutes. + +Tyler Wright: Less Dynasty I have questions. + +Tyler Wright: I love the idea of a case study as I talked to individuals. + +Zach Horn: Yeah. + +Tyler Wright: I always try to push them to. once you're done with the integration, it would be great to do a case study and then obviously our connect on the Zach as soon as possible, but just from a user experience standpoint. I do think a number of Engineers go to the documentation first before they go to other sections of the website to look for this kind of information. So I'm not saying you're just saying it shouldn't live there but at the very least I think some of these elements should live pretty high up in cumeation. easily searchable + +Denis Lelic: Yeah, I think I saw handwren up. + +Tyler Wright: I don't know if Zach had something. + +Zach Horn: No, I didn't but I end up. Yeah, which one of the four of us this gigantic crowd? Yeah. + +Tyler Wright: Okay. + +Denis Lelic: Maybe it was my hand. + +Tyler Wright: Yeah. + +Zach Horn: Yeah, I love I mean just real quick. + +Tyler Wright: and then + +Zach Horn: I case studies are great. I mean that is absolutely something we should be doing on the website even with sections on the website. how other unnamed large Cloud providers do it where they basically service people that are using, their resources and how they're using them and make it super easy to see who's building that's fantastic to be quite honest. It comes down a little bit to a band with issue, but that can be reprioritized. So I would say if we want to get into that. we just need to decide how that's what the team. Because everyone's just pressed for time. + +Denis Lelic: Yeah. + +Tyler Wright: Yeah. + +Denis Lelic: If you want to share anything else. + +00:30:00 + +Bold Panther: No, I don't have anything specific right now. + +Tyler Wright: I + +Tyler Wright: So this is the second issue based upon I guess feedback that members of the core team have talked about previously again. I think there's a number of on the website, but it'd be great to have a one-pager and maybe that also has a video in it. That's just like here's how you deploy and it will give you how to deploy via CLI with a couple of commands and then also give you how to deploy via the console maybe with a video and hopefully I'll make it very very easy for new users to in a couple of clicks be able to at least deploy hello world, and then they can just + +Tyler Wright: Scale up from there. I know it's something we previously had on the website. We previously talked about in five minutes or less. I don't know if we want to use that language. I leave that up to the content King Zach, but this is just an idea that I think should just be more prevalent and just an easier guide for new users. Just here's how to do the simplest thing. And quit very quickly and then people can scale up from there. + +Zach Horn: I agree with that. Yes, we should do that aside on a lighter note with all these titles, content King, not to derail, but kings an ancient way back Louie the 15th or whatever they'd have 15 titles. That's a little bit what I feel like it's like head of marketing content King, give me some more I'll take as many titles as I can get. + +Tyler Wright: Will do. + +Zach Horn: anyway Yeah. + +Tyler Wright: Good. + +Zach Horn: No, I agree with that point. + +Tyler Wright: Peers I would say this is higher priority than that contact page by a significant margin, + +Bold Panther: So yeah,… + +Zach Horn: Yeah. + +Bold Panther: this looks great. So for Hello World Series or something that we can do for the cost. Yes. I need someone who is working with akashias for long so will be easier basically we need a proper explanations of how to integrate with the cost using and all if someone is working with the costumes And can create something a proper content would be great for this section. + +Tyler Wright: but Yeah, I will have so maybe one the first one to yourself and I'll sign the second one to somebody else. assign the second one to me, I guess and then I will sign to somebody else. But if you can assign that one to yourself and prioritize this page, that would be stupendous because again, I know this is something that works members of internal team if we can update this and make it quite easy. Yeah. There we go, then yeah, that'd be great. And I have no problem with that quick start menu, but it may be if you're very Fast in being able to make those changes which would be great. Maybe we could just add it to the essentials tab for now because it seems like there's one area that's open. + +Tyler Wright: And maybe we could put what is Akash Network and then move the sdl down to and with tokens and wallets and then we can just move how to deploy in five minutes or less, to that top block. I wasn't preparing my screen the entire time,… + +Bold Panther: yeah, + +Tyler Wright: but I think you know what I'm talking about. + +Bold Panther: Yeah. + +Bold Panther: purpose Then we have this issue. + +Tyler Wright: I'll go ahead. + +Bold Panther: So it's all here for the past issues. + +Tyler Wright: Yes. I was gonna bring up a new issue that I'm gonna create but we talked about previously so you go ahead and I'll just add that issue. + +Bold Panther: So this is something that is created by 0 so, implemented some more effects on we have the taste. So I requested the feedback from him. He also provided the link probably so. The holy we affects are previously we had the red as you can see when I over it becomes said it was not there for the state say implemented the thing for this year. So + +Bold Panther: so probably as link is not on the latest one but implemented the whole effect for these three icons and also the icons for the putter. So this is something that will be more. So when I work as you can see the color is not changing to red as some like this one so it will be something that is implemented. So it will be most soon to the + +00:35:00 + +Denis Lelic: Is that something he just? done self-initiated + +Bold Panther: Yeah, he initiated this thing. Yeah. Then this is something that is spending from Tom. + +Denis Lelic: Okay, that's nice. + +Bold Panther: So accessibility that is So it's also pending so we will just have to provide the graphics. So as we can see. in it + +Bold Panther: So engineer dogs, there are some graphics which are not that great. the text can be improved a bit to increase the visualization issues. So yeah, I'm working on it. I will provide the graphics to you update it. so I think We did it here for one. + +Denis Lelic: an article + +Bold Panther: So yeah, I will check over it. + +Denis Lelic: cool + +Bold Panther: This is something that is on the discussion. So this is something that has been created by so the issue was this + +Bold Panther: When we go to the docs and when we click over it, it's not opening any of the pages. So the solution was this which is being a bring up by Tom that when we click over this it should open up the first page automatically like this. So when I click on get started Edition automatically open the cost of the first page similarly when I open up the drop of any of these drop down, let's say providers. It should automatically open the first page that is this instead of clicking on sale drops around that we have so I think this is a great improvements and the US governments and I think hero worked on this issue and there are few books that I noticed in history. So I'm fixing those issues. There are issues in each the other day not least one of the issue was like When we are on this page. and when we will clicking the refresh button it was + +Bold Panther: Making the dogfish widely for it was taking the dog space to the default version that is homepage, which is not the case in the current version. So these are few shoes to they were two books in his PR. So I'm just fixing those books and most accordingly As you can see this is the pr that has been created. So it's under testing and we are testing internally before merging it to the official site. now other issues are kind of like Okay, this is something that is also being updated by Hero. + +Tyler Wright: I think that would be a great Improvement. + +Bold Panther: As you can see like it… + +Tyler Wright: I know we talked about it here and… + +Bold Panther: what they show us stated by energy to add this traffic. + +Tyler Wright: cs. thank you pierce and… + +Bold Panther: So he created the pr And I requested the feedback from Android and Yeah. + +Tyler Wright: let us know if you need anything before merging that would be amazing. + +Bold Panther: he provided some of the feedbacks and… + +Denis Lelic: A one more thing. + +Bold Panther: accordingly hero iterated. + +Denis Lelic: Would it make sense to invite hero to these meetings? + +Bold Panther: so I think + +Bold Panther: Right now I also requested few of the changes that. He probably just fixed and I will just recheck the issues and after finalizing things that we have will be much so, Yes, probably he missed out on meeting. I notified in that meeting is happening. So, let me see the message again. + +Bold Panther: + +Tyler Wright: Here previously and… + +Bold Panther: that's all. + +Tyler Wright: he knows that they exist. I think he's sometimes doing some other stuff… + +Bold Panther: son + +Tyler Wright: but I keep in contact with them a number of times during the week and… + +Denis Lelic: cool + +Tyler Wright: I know I can continue to get more involved so We'll make sure that if he can he comes to Future meetings. I know he' Maybe has a couple of languages. There's a maybe better able to communicate via messaging, but I'll ask them to join. + +Denis Lelic: Cool, It's just nice to see people getting involved in these issues and + +00:40:00 + +Denis Lelic: communities growing cool + +Bold Panther: yeah, so yes also here is everyday brings me up in the morning. So because about the issues that are pending so I don't guide them that you can work on this issues and all and then after he creates a PR there is a constructive feedback within our team also the court sometimes in this case, so I try to make sure that everything is properly done before getting it most of the site. So yeah, I'm also I would all say Heroes predictive a daily in contributing to the cost Network site or possible weeks. + +Denis Lelic: Okay. + +Denis Lelic: I think with touched some of these issues in our previous sessions, so hopefully when this accelerate thing is behind us, I'm gonna find some more time to go through this issues and just provide assets and whatever it's necessary. so + +Denis Lelic: yeah, I think we went pretty much through the whole thing. Unless you want to talk about something else. + +Zach Horn: Nothing on my side. I think we're pretty good. + +Bold Panther: just + +Denis Lelic: cool Okay, cool. + +Tyler Wright: Me too. Thank you all. + +Bold Panther: So there was no issues. So that was talking about we will create an issues. + +Tyler Wright: Yeah, I'll create Offline and then I'll drop it in Discord. It's just an issue we talked about previously related to making updates to the console page. I believe Thomas is going to work on that. But if Thomas doesn't have the bandwidth and I'm just gonna Outsource it to somebody else in the community. And again, we just have to pull images from + +Tyler Wright: a new beta version which I'll give folks access to but should be very quick and easy. And that's his life right now. But I'll create an issue for that and I thought with Thomas if Thomas can't handle it then again. I will see if anybody else from the community can handle it, but we'll look to get that done over the next couple of days. + +Denis Lelic: I was good. + +Tyler Wright: All… + +Denis Lelic: Okay, cool. + +Tyler Wright: y'all. Yeah,… + +Denis Lelic: Thanks for joining. + +Tyler Wright: thank you very much. Enjoy these meetings. I'll talk to you all in two weeks. If not before async,… + +Bold Panther: have + +Tyler Wright: but let me know. If you have any questions about the deploy in five minutes, and we can just keep that pushing. + +Bold Panther: So yeah, I will let you know. + +Tyler Wright: awesome Thank you. + +Denis Lelic: Thanks guys. + +Zach Horn: Thanks guys. Take care. + +Bold Panther: Thank you. + +00:45:00 + +Tyler Wright: We're getting a tourism. + +Tyler Wright: Thank you. + +Tyler Wright: Boy owner has something to say. Good. + +Tyler Wright: for seven years ago, but he was setting what your deal so + +Tyler Wright: in a salary so retain ing Bird, right but after this agent also representing Kevin Garnett baptisms He is full condition from that contract and that is how the contract Behavior. As a result the commission. ER David sturt to spend a typical + +00:50:00 + +Tyler Wright: art one year. He also find the team. 3.5 million dollars and most importantly presentation of or other next five first round draft picks completing the franchise building a championship and around that just as he was entering the proud of his. + +Tyler Wright: I + +Tyler Wright: put the savior. + +Meeting ended after 00:53:23 👋 + From 9ea6e1694d084742a74b7b3c7edcf2102138fb73 Mon Sep 17 00:00:00 2001 From: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Date: Fri, 12 Jul 2024 21:10:57 +0000 Subject: [PATCH 55/55] Create meeting notes for wg-zealy #12 (#593) * Create meeting notes for wg-zealy #12 Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> * Update 012-2024-04-29.md add recording link and transcript Signed-off-by: Drinkwater --------- Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Signed-off-by: Drinkwater Co-authored-by: Drinkwater --- wg-zealy/meetings/012-2024-04-29.md | 268 ++++++++++++++++++++++++++++ 1 file changed, 268 insertions(+) create mode 100644 wg-zealy/meetings/012-2024-04-29.md diff --git a/wg-zealy/meetings/012-2024-04-29.md b/wg-zealy/meetings/012-2024-04-29.md new file mode 100644 index 00000000..6ec58acd --- /dev/null +++ b/wg-zealy/meetings/012-2024-04-29.md @@ -0,0 +1,268 @@ +# Akash Network - Zealy Working Group (WG) - Meeting #12 + +## Agenda +- Discuss current and upcoming missions. +- Resources for mission creation. +- Share some analytics and community growth data. +- Discussions on potential continuation of the program and the process for securing further funding. + +## Meeting Details +- Date: Monday, April 29, 2024 +- Time: 6:00 AM PT (Pacific Time) +- [Recording](https://rfo5d4qnnddwhhwyncat6u6gjone7ohuotiv6op3rvzu3va5glpq.arweave.net/iV3R8g1ox2Oe2GiBP1PGS5pPuPR00V85-41zTdQdMt8) +- [Transcript](#transcript) + +## Participants +- Benjamin B. +- Robert Del Rey +- Tyler Wright + +## Meeting Notes +- The meeting focused on the progress of Sprint #2, plans for Sprint #3, and existing missions rolling over. + +**Key Points:** +- **Sprint #2 Recap:** + - Sprint #2 ended on April 27th. + - Benjamin will review and export the leaderboard data to determine the winners. + - Sprint #2 had fewer missions, resulting in fewer points compared to Sprint #1. + +- **Sprint #3 Overview:** + - This will be the final month of the initial campaign. + - Decision to extend or end the campaign will depend on the results. + +- **New Missions for Sprint #3:** + - **Text-to-Speech (TTS) Solution on Akash:** + - Inspired by a question on Akash Discord. + - Similar to the deployment of Lama 3 on Akash Network. + - Encourages users to deploy TTS solutions for rewards. + - **Content Creation Mission:** + - Create a 10-15 minute video on the history of cloud computing and Akash's role. + - Only one winner, potential to feature the video on Akash EDU. + - **GitHub Discussions:** + - Unpaid mission to teach users how to create discussions on Akash GitHub. + - **Akash Bounties:** + - Overview mission to direct users to Akash bounties on Discord. + - Unpaid mission. + - **Newsletter Subscription:** + - Template mission to subscribe to the Akash newsletter. + - Unpaid but offers XP points. + +- **Existing Missions Rolling Over to Sprint #3:** + - **Deploy Persistent Storage on Akash:** + - Helps users interact with Akash using any available hardware. + - Initially launched in Sprint #1, rolled over due to time constraints. + - Some providers have not set up correctly and are not approved. + - **Provide Compute on Akash:** + - Similar purpose and feedback as the Persistent Storage mission. + - **Join Akash Insiders:** + - Unpaid mission to join Akash Insiders, with 7 people clicking the link. + - **Invite Friends to Akash Zealy:** + - Unpaid mission, rewards XP points, involves inviting friends to join Akash Zealy. + +#### Community Growth and Feedback +##### Robert: + - In the last three months, nearly 300 new members joined. + - After removing initial pilot members, 208 new members were acquired. + - Positive growth trend since March, with increasing community engagement. + - Feedback to Zealy: Improve the quality of analytics provided. + +**Feedback on Program Success:** +- The meeting continued with discussions the success of the initial sprints, the potential continuation of the program, and feedback on program performance. +- Tyler Wright highlighted the success of the pilot and the first two sprints, noting the growth and positive reception. +- Tyler expressed support for continuing the program, suggesting a new funding proposal if necessary. + +**Discussion on Program Continuation:** +- Benjamin B. mentioned previous discussions with Robert Del Rey about continuing the program and seeking additional community funding. +- Robert Del Rey asked about the process of reopening threads on GitHub for proposal discussions. +- Tyler Wright confirmed that new proposals should be made for each new period and suggested referencing the old proposals in new threads. + +**Community and Leadership Support:** +- Tyler Wright conveyed strong community support for the program and endorsed the leadership's efforts. +- Robert Del Rey and Benjamin B. appreciated the support and expressed their satisfaction with the program's progress and their collaboration. + +#### AI Video Submission: +- Robert Del Rey shared a short AI video submitted to YouTube, promoting Akash Network. +- The video highlighted the concept and benefits of the Akash Network, presenting it as a revolutionary decentralized cloud solution. +- Tyler Wright and others reacted positively to the video, finding it exciting and effective in promoting Akash Network. + +**Budget Allocation for Sprint #3:** +- Benjamin B. suggested allocating additional funds for larger missions due to an unexpected donation from Greg. +- Estimated spending for Sprint #2 is around 300-350 AKT, final review pending. +- Robert Del Rey agreed to include the equity paid in rewards in the next community update. + +**Mission Ideas and Branding:** +- Tyler Wright suggested incorporating the "super cloud" concept more prominently in missions, especially in video content. +- Tyler highlighted the importance of clear branding to differentiate Akash's offerings beyond just GPUs. + +**Next Steps:** +- Tyler proposed discussing the leftover funds and potential mission extensions in future meetings. +- Tyler will follow up online and be available for further discussions in the Zealy channel. +- Tyler will participate in future discussions and provide further input on mission extensions and budget allocation. + +**Conclusion:** +- The meeting concluded with positive feedback on the program's progress and a commitment to further discussions and improvements. +- Participants expressed satisfaction with the direction of the campaign and the collaborative efforts involved. + +**Action Items:** +- Benjamin B to review and export the leaderboard data for Sprint #2. +- Robert Del Rey to finalize and publish the new missions for Sprint #3. +- Robert Del Rey to coordinate with Adam to review potential content for Akash EDU. +- Benjamin B. & Robert Del Rey to discuss and finalize the details for a new proposal to continue the program. +- Benjamin B. & Robert Del Rey to consider creating a new GitHub thread for the proposal, referencing previous proposals for context. + +# **Transcript** + +_This editable transcript was computer generated and might contain errors. People can also change the text after it was created._ + +Robert Del Rey: All Happy Monday and happy labor day at least in Latin America. Thank you so much for joining to this cold life and those listening to the recording later. This is the cash silly working group. by weekly call So here we discuss all things silly. + +Robert Del Rey: and yeah, what's next about really? So, let me jump right into it a sprint number two. Just end it last 27th of April. I haven't seen any of the results, but we have time to check that out. So Benjamin, I will go ahead and go over the leaderboard export the data and see what were the winners for Sprint number two. Yes, I will add now a sprint number two was a bit different than a sprint. Number one, I guess with the fewer missions and that's why you see fewer points than then then the first Sprint. That's okay. You live and learn as I say. + +Robert Del Rey: And today's agenda. I would like to go over the missions. We are thinking about for a sprint number three the third and last month of this initial campaign. Let's see. after this campaign we continue with a few more months or if we just settle this down and move forward with something else. Let's see. The results are gonna speak on that. So let me share my screen real quickly. + +Robert Del Rey: That's quite important people join these calls because you get access to early Alpha. And maybe we prepare for what's coming. So Let's go half a cash, Great. Let me know if you can see my screen Benjamin you. + +Robert Del Rey: awesome Sold the offering we have for these upcoming Sprint It's a combination of New Missions. And existing missions rolling over to this Sprint. + +Robert Del Rey: Dimensions of the top there was a little hype with them during I would say the last week. lo Texas speech Solution on a cache. This one came up for a question that I saw on a cash Discord and I wanted to turn it into a mission and it's very similar to Lama 3 on a cash Network. For those listening now, I'm sure and for those listening to the recording later, maybe you might know you might not know. + +Robert Del Rey: Last week Lama 3 was deployed on a cash Network and CJ. One of the Akash insiders great guy props to him. He posted a small threat guy on how to deploy Lama Tree on a cache and I was impressed man that tweet got over 12,000 impressions. which is huge, so I'm trying to take not some Advantage but Try to use that. + +Robert Del Rey: Try to use that reach and that impression and maybe try to bring some people to deploy Lama Tree on a cache. through silly They come to Seeley. They see the mission deploy Elementary on a cash. They do the mission and they will get reward for it. That's the main difference between the Seagate post and these ghosts people that did it using the CJ guide didn't get anything. So on a cash silly people will be able to get some prices to the employer TTS solution and deployment through on a cash Network, which is almost the same as kind of two for one mission in my opinion. let me see here some people join the call. Hey, Tyler welcome and happy Monday. + +00:05:00 + +Robert Del Rey: Literally good man. No worries. Thanks for joining. We are just wrapping up the Sprint number two, and now going over the missions available for a spring number three just to give too long didn't read. So let me continue then this mission is cool. This is the attached document or this is the only content creation mission that we're gonna have during a sprint number three. and this one is about content this one is about creating a long 10 to 15 minute video. Talking about the history of cloud computing and what is the role of a cash Network in this market the cloud computing Market? + +Robert Del Rey: There is only going to be one winner for this mission. Which I believe is going to help us getting the best content. Hopefully the winners submission. + +Robert Del Rey: Hopefully know what I'm planning to do with the winner besides giving akt price. I also wanted to talk with Adam to see if the video is good enough. Maybe we can use that same video to add it to a cash EDU. Used to give a little context. I cash edu. It's like a beer tall platform. So people can get education about a cash and having a video about the history of cloud computing and a cash role in it. I think it's a pretty nice piece of information depends on the submitters. Let's see what the submitters come with. So moving on take it to GitHub. This mission is on paid. No rewards for this mission. + +Robert Del Rey: Because I want people to learn what is the process of creating a discussion on a cash GitHub? how the mission look like Is that you have the link you have the best practices and the mission tells you you want to create a listing proposal. You want to Market in proposal you want a funding proposal you want an x y c proposal take it to GitHub. And in the mission, the people will see the steps to create a discussion that's gonna be an unpaid Mission, but hopefully we can Teach people coming to see how to open up discussions and get involved in their cash GitHub. + +Robert Del Rey: And the last of the New Missions is the Akash bounties. This one has the question mark. Because I haven't done it yet. It's just like an idea. And it similar to take it to GitHub. It's gonna be on paid but it's gonna have an overview about the cash bounties and where people can find those bounties. I see it as a complement to the cash Bounty Hunter's channel on Discord. In the last one. Sorry, I jumped over this one. It's the newsletter subscriber. this one is a template that silly has in their page. And you just add the link. So people can subscribe and people just add the link and they subscribe to whatever newsletter you want them to subscribe. So I added the cash newsletter link to the mission. + +Robert Del Rey: and people that want to get up to speed on a cash can subscribe from the newsletter and do this Mission? It's gonna be unpaid but it's still people gonna get XP points to do them missions. And yeah, those are the new offering we're gonna have on a Sprint number three before I go to the existing missions rolling over to a Sprint number three, are there any questions so far? + +Robert Del Rey: All right. I see a thumbs down. I'm gonna take that as I know. Give me one second guys. + +Robert Del Rey: All right. so existing missions rolling over to a Sprint number three These two are very popular in my opinion deploy persistent storage on a cash and provide compute on a cash. Yeah, we know a cash is trying to get of the best test hard work. So people bring those to a cash market place, but there are some people that don't have The Best of the Best Equipment, but still they want to get involved in a cash. They want to connect whatever resource they have just to get their feet on the water. so I think this missions + +00:10:00 + +Robert Del Rey: help people get involved without having to think much about the hard work. They need to be a super serious and super profitable provider. so this gives the chance to people to interact on a cache with whatever Hardware they have get some XP points and Main I get paid we launched this mission on a Sprint number one the feedback we have Is that people didn't have much time to do this mission? So that's why we decided to roll it over to In a month number two, if I'm not mistaken, maybe Benji can help me a little bit in this area more people did the mission and actually get to spend a longer time. + +Robert Del Rey: Providing on a cash and having a persistent storage on a cash. I messed up a quick second. Maybe when you want to add something about these two missions that be amazing just for the recording. If not, that's okay. + +Benjamin B: Now I've been looking a little bit on this right now and we've had some providers trying to start. I'm not going to name many people here. But the last person I checked and where they have set up to provider. They haven't done it correctly. So they will not be approved in this Mission. I'm not sure if we've seen money and you providers here, but we've seen quite a few people and crying. + +Robert Del Rey: Got it, Thank you so much. let's see. We have the third and last month. Hopefully more people jumped in. And the other two are on paid missions to it's during the cash insiders so far seven people have click on this link. I don't know if they did the application. I will need to ask Adam. And they invite three friends to a cash silly this one. It's unpaid it gives you XP points though, but doesn't pay you any akt and some people have done it too and not just decided. It doesn't hurt to leave these two open for the remaining of the campaign. + +Robert Del Rey: I have here reminder for the steering monthly call all this I'm just practicing now, right because all this information I'm planning on sharing in the steering monthly call which is gonna happen these Thursday if I'm not mistaken. So the broader Community can know more about what we are doing in the cash, And some stats that I wanted to share with you here. It says the last three months. We had almost 300 members, which I find amazing. If you remove the people we got from the first pilot we did on November December. If you remove that people. you left us with 208. + +Robert Del Rey: members so on month number three a month number two We were able to get 208 new members in a cash City. You can see the graphic here. This is the beginning of March when we started the first Sprint, that's where you can see this we went parabolic, right? And then you can see how we slowly are still increasing in community members. We shall find really cool one very big feedback that I gave Sealy. I was able to speak with them two three weeks ago. And is that this analytics is too poor in my opinion? I've been able to see other kinds of Analytics. + +Robert Del Rey: and I feel somewhat limited with this. So that's something to keep in mind for future discussions the quality of the analytics that we get from Seeley. That's just a personal thought that I'm sharing right now. So yeah, this is the members amount and the top countries where most of the members are based. Which I find really cool. The last time we saw this we had five members from India But now you can see we have nine members from France ate from the Six from Indian Russia and many more this one maybe doesn't say much but I like to see that we are. + +00:15:00 + +Robert Del Rey: How Global this is honestly, sometimes we are in the chat and you cannot believe everybody it's space either on Europe or in the US. and it's cool to see this information. That's why I added here. And some submissions I wanted to share with you and this is too close it out and then we can open up to comments or questions if you have any let me stop present in here. Wow, okay. let me + +Robert Del Rey: I can wear life. Go ahead time. + +Tyler Wright: my only question is it seems like the pilot was very successful. the first three or the first two sprints have been successful and there seems to be a fair amount of growth. I believe we're coming up correct me from wrong, but I believe that we might be coming up on the last or towards the end of this program. if that is in fact the case I would be of the thought process that this is something that should continue on. Have you all thought about Hosting another discussion or just going back to community pool for some more funding or what? That kind of looks like go ahead Benjamin. + +Benjamin B: Thank We discussed this me in Robert's per for you joined them before we started recording. We don't have any details yet, but we can definitely start talking about this topic now and we have plans to Trying to ask the community pool to continue this program, but for the details. We have yet to discuss if you want to make an enlarger changes or anything. Maybe Robert has some ideas. + +Robert Del Rey: Yeah, just to add to that. We were discussing exactly that Tyler before you jumped in like Benji said and something we were discussing is that if we should open up a new thread on GitHub and add the information we have or if we should reopen the original Thread about this campaign that original thread it's close already. Honestly don't know if you can reopen close threats. So I'm honestly asking you. + +Tyler Wright: Yes. Yes, you can I would say maybe make a new thread,… + +Robert Del Rey: Okay. + +Tyler Wright: somewhere away in the past overclock has done proposals for events, and every time it's a new quarter a new period they just make a new proposal. So I just think you can make a new proposal and reference the old proposal. + +Robert Del Rey: Got it. okay. Thank you so much. + +Tyler Wright: But at the highest level I and… + +Robert Del Rey: All right. + +Tyler Wright: many other people within the community that I've talked to and overclock Labs have been very happy with the leadership and with the progress of this program, so I would put one vote in representing Tyler to have you all continue this program. + +Robert Del Rey: Thank you that's great to hear and your support your escort and everybody else has been Super Paramount. Honestly, honestly, Benji and I are super happy. We both learned a lot on this we learned about the work and we also learned about each other and yeah, I'm happy to hear that. You guys liked it and would support in case we want to continue. So amazing man amazing. + +Robert Del Rey: Thank you for your endorsement menu. So the last thing I want to share is just one submission. This is an AI video that someone did. and uploaded to YouTube. It doesn't have many views But just wanted to share it. It's a few seconds long. Let me know if you can see it. + +Benjamin B: I can see. + +Robert Del Rey's Presentation: in the realm of digital Innovation the Future is already here. + +Robert Del Rey: Can you hear to? + +00:20:00 + +Robert Del Rey's Presentation: It's called the Akash Network. + +Benjamin B: Yes. + +Robert Del Rey's Presentation: Imagine a super cloud infrastructure. That's not just a service but a revolution it's about time. We started thinking bigger dreaming Bolder. Our world is becoming increasingly interconnected. And with that comes the need for more powerful decentralized Cloud Solutions. Enter a cash Network a game changer a disrupter. It's the world's first decentralized open source cloud, and it's here to redefine the future of cloud computing imagine. Having the power to run any application anywhere anytime. This is the promise of a cash Network get ready to unlock a world of possibilities where the sky is not the limit, but the starting point Welcome to a cash Network. + +Tyler Wright: Damn, that seemed like a hype video. + +Robert Del Rey: All right. + +Tyler Wright: I got me excited. + +Robert Del Rey: Yeah, yeah, you do feeling me I saw this on Saturday and I was super happy about the video because It goes straight to the point. But at the same time it kind of promotes a cash Network. so yeah, just gonna take sure that with you that is one of the submissions we got in the Sprint number two. So yeah. Yeah, that's all I have for the agenda. We did an overview of the offering we're gonna have for the Communist Sprint number three. The screen number three is going to happen. It's going to start on Wednesday first and go all the way on to I believe it was Monday 27. I got to check that one out. But yeah, we shared the missions. We share some analytics and we also spoke about + +Robert Del Rey: The future of this campaign with that being said, is there anything else you want to add to the conversation guys or any questions comment? + +Robert Del Rey: Go ahead Benjamin. + +Benjamin B: Yeah, I want to say that for the third month. Maybe we should consider having some larger missions we got. a big donation from Greg for their High School, which I'm guessing we're gonna send back to the community pool. unless we use it and we can really try to figure out some great missions we can use that money on because right now the first Sprint we spend approximately the calculator This print I think we spent a little less. and then this third month, I think we should try to overspend a little just because we got some extra funds within calculate for I think we're about 300 to 350 Katie for this Sprint, but I'm not quite sure yet. We haven't + +Benjamin B: reviewed everything yet. + +Robert Del Rey: Yeah, okay. Let's check that out. And if you can… + +Benjamin B: Yeah. + +Robert Del Rey: then just me that info so we can share it in the city in comedical. That is another metric that is good to share the equity paid in Rewards. + +Benjamin B: Yeah. + +Robert Del Rey: So yeah, thanks for bringing that nice catch 30 forgot about it. + +Benjamin B: The Tyler is the other thing, please go ahead. + +Tyler Wright: I have to run to another meeting but I can follow up with you all online again. I think this is moving and the right direction. let's have a sink if there is extra spend left over we can talk about either adding a discussion to say that hey can we extended we'll just keep these tokens and then we can go discussion after that, but I'll follow up with you offline. And there's other one thing I want to talk about is if we can include some Mission especially if it's a video because I really like the way that video is going back. We talked about super cloud. I do think that we need to + +Tyler Wright: mention that more, from a branding perspective. I think it's something that folks that don't understand the caution is called compute Marketing in general and think you got this just have gpus it's a lot more than that. So if we can start to incorporate super cloud, I think that would go a long way. But just hit me up in the zealy channel. If you need me and we can continue to talk there between now and the next meeting but much appreciate you all and I'll follow up with some of you about other items and I'll see you all at steering committee. If not before but let me know if you need anything prior to steering committee, but I'll leave some time for you all as a part of the projects list to talk about zealy. + +00:25:00 + +Robert Del Rey: Thank you so much that you sure Have a nice day, too. + +Benjamin B: Thank you so much for joining. + +Robert Del Rey: All… + +Benjamin B: And with that,… + +Robert Del Rey: All right. + +Benjamin B: I think this meeting is concluded or do you have anything else? + +Robert Del Rey: I don't have anything else to add bro. I'm just the Stoke about how things are going and it's great to hear when a third party like an outsider like Tyler say that things are going good from their perspective. So I think that says a lot about what we're doing All right. + +Benjamin B: Yeah. Super happy to work on this. + +Robert Del Rey: Absolutely, So Benjamin, we're gonna catch up later this week, but for now you see you on the other side. Alright? + +Benjamin B: Yeah. Have a nice rest of your day Robert. See you around. Bye. + +Robert Del Rey: YouTuber stay safe + +Meeting ended after 00:26:03 👋 +