From c0a7853a0359e1768caf22b6abcd51e1ded62818 Mon Sep 17 00:00:00 2001 From: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Date: Fri, 23 Aug 2024 01:41:55 +0000 Subject: [PATCH 1/9] Create meeting notes for sig-Analytics #13 (#663) * Create meeting notes for sig-Analytics #13 Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> * Update 013-2024-08-15.md add transcript Chore: add recording link Signed-off-by: Drinkwater * Update 013-2024-08-15.md added 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-analytics/meetings/013-2024-08-15.md | 192 +++++++++++++++++++++++ 1 file changed, 192 insertions(+) create mode 100644 sig-analytics/meetings/013-2024-08-15.md diff --git a/sig-analytics/meetings/013-2024-08-15.md b/sig-analytics/meetings/013-2024-08-15.md new file mode 100644 index 00000000..686a528f --- /dev/null +++ b/sig-analytics/meetings/013-2024-08-15.md @@ -0,0 +1,192 @@ +# Akash Network - Analytics Special Interest Group (SIG) - Meeting #13 + +## **Agenda** +- Introduction and overview of the Analytics Interest Group +- Updates on the open-source indexer solution +- Feedback from the community +- Open floor for additional topics + +## **Meeting Details** +- Date: Thursday, August 15th, 2024 +- Time: 09:00 AM PT (Pacific Time) +- [Recording](https://j3ac6jsjcqd3hmfii6dophi4gunxiuqqxdeslkehhz6fpnvvgkta.arweave.net/TsAvJkkUB7OwqEeG550cNRt0UhC4ySWohz58V7a1MqY) +- [Transcript](#transcript) + +## **Participants** + +- B S +- Maxime Beauchamp +- Maxime Cyr +- Robert Del Rey +- Rodri R +- Tyler Wright + +## **Meeting Notes** + +**Introduction and Overview of the Analytics Interest Group (Tyler Wright)** +- Tyler Wright introduced the meeting as part of the ongoing efforts of the Analytics Interest Group. +- He highlighted the group's historical focus on developing an open-source indexer solution, which is now available as open-source. +- Tyler mentioned that updates on the indexer and other relevant topics would be discussed, with community feedback encouraged. +- He informed participants that information from the index service is available on [stats.Akash.network](https://stats.akash.network/) for tracking and monitoring. + +**Updates on the Open-Source Indexer Solution (Maxime Cyr)** +- Maxime Cyr provided an update on recent changes to the indexer: + - The team added tracking for persistent storage alongside FML storage. Currently, persistent storage is combined in the UI, but it will be separated into its own graph in the future. + - The retry interval for time checks on providers was reduced, enabling providers to come back online sooner after a failure. + - A small bug was found and fixed in the indexer, which affected only 0.0001% of the value, having no significant impact on the statistics. +- Tyler Wright asked Maxime Cyr to share a [link](https://github.com/akash-network/console/tree/main/apps/indexer) where people can track these changes for visibility. + +**Community Feedback and Discussion (Tyler Wright, Maxime Beauchamp)** +- Tyler Wright shared feedback from a Telegram user regarding the daily USD chart on the stats page: + - The user mentioned that the chart appears "messy" in the all-time view, and the 30-day view is too short. + - The suggestion was made to add a 90-day view and improve zoom-out functionality for easier viewing. +- Maxime Beauchamp acknowledged the feedback and mentioned that an issue had been created to address these concerns. + - He suggested that updating the graph library could improve chart functionality and invited community members to contribute to this effort. + - Maxime emphasized the importance of aligning on the library choice and implementation, and encouraged community involvement. + +**Discussion on Meeting Frequency (Tyler Wright, Maxime Beauchamp)** +- Tyler Wright asked if there were any additional topics or updates that needed to be covered before concluding the meeting. +- Maxime Beauchamp brought up the possibility of changing the meeting frequency from bi-monthly to monthly. +- After a brief discussion, it was clarified that "bi-monthly" means every two months, and the current schedule would remain unchanged. +- Tyler Wright mentioned that the decision to keep the meetings every two months was based on the current level of updates and contributions, but they could revisit the frequency if needed. + +**Open Floor for Additional Topics (Tyler Wright)** +- Tyler Wright encouraged participants to bring up any final topics or updates. +- He emphasized the importance of community involvement and reminded attendees to use Telegram and Discord for ongoing discussions. +- Tyler offered to organize one-off working group sessions for those interested in contributing more actively to the indexer or other projects. + +**For Maxime Cyr:** +- Share the link to track recent changes to the indexer for visibility among the group. + +**For Maxime Beauchamp:** +- Continue working on improving the chart functionality, including adding a 90-day view and zoom-out features. +- Support and engage with the community regarding contributions to the indexer and other analytics-related projects. + +**For Tyler Wright:** +- Facilitate any one-off working group sessions as needed for community members interested in contributing more actively. +- Ensure that meeting notes and resources are shared with the community to encourage involvement. + +**For All Participants:** +- Stay engaged with the analytics Discord channel and other platforms to provide feedback and suggestions for future meetings and projects. + +# **Transcript** + +Tyler Wright: alright, welcome everybody to the analytics by monthly meeting during + +Tyler Wright: Interest group for analytics the group has historically come together initially again to help develop a open source index or solution the cloud most team had one again that solution is now open source when we discussed some updates there. So I will hand you over to Max shortly to talk about any updates in addition, we get feedback from the community if there's any questions we're sharing again a lot of the information from the index service displayed on stats.com network so you can track some information there. if anybody has anything that they want to cover during this meeting feel free to drop it in. I know there's some conversation that's been going on this again analytics Discord channel, so I will bring up some of the topics there but + +Tyler Wright: Max I just want to see if there is anything I know we don't meet that often. So I know that you've been working on some things related to the indexer. I just want to see if there's anything that was worth sharing with the group here today and we're with those that might be listening to the recording or watching recording later on. + +Maxime Cyr: Yeah, sure and just looking the recent changes we did and the tracking for the r persistent storage. So previously when we Regularly provider to track available resources in previously. We were on the tracking FML storage. So now we're tracking persistent storage as well. It's combined in the UI for now, but eventually it will be a separate graph for it. And we also reduce the vitri interval when A Time check fails on the providers. So if I provide the the is down for whatever reason. + +Maxime Cyr: we try it more than so that it can come back online sooner when it's fixed. And we also found a small bug in the indexer about how we compute resources list and spent. akts it's fixed, but we did an analysis and Found out it on the affected 0.0001% of the value. So the didn't affect the stats. in any + +Maxime Cyr: significant way + +Maxime Cyr: I think that's all the changes with the recently. since last meeting + +Tyler Wright: Thank you very much Cool. does anyone have any questions about some of the updates from maxi? + +Tyler Wright: max if you don't mind when you get a chance, if you can just drop in the attach that work organization where people can kind of track some of these changes that happen just for again visibility sick. + +Tyler Wright: The perfect thank you. There is one question that came in be a telegram and I just want to just get some on the record kind of feedback here today from this big analytics from a couple days ago. it was offered a suggestion that daily USD chart on the staff page looks a bit. + +Tyler Wright: Quote unquote Messier noisy on the all view in the 30 day view is a bit short. So it'd be nice to have maybe a 90 day view of the USD chart. + + +### 00:05:00 + +Maxime Beauchamp: Yeah, I created an issue on the console people for that matter. + +Tyler Wright: They also talked about maybe some more in zoom out functionality for the charts this for easy viewing. + +Maxime Beauchamp: But yeah, we definitely could use an updated library for displaying the graphs. + +Tyler Wright: I don't know if that's something that other people can contribute to or something that Maxes you all have thought about and… + +Maxime Beauchamp: There's a lot of them available right now… + +Tyler Wright: maybe move in another direction for a number of reasons. + +Maxime Beauchamp: where you can zoom in. + +Tyler Wright: But again,… + +Tyler Wright: I just want to pass along that feedback from a telegram user as transcribed in Discord. + +Maxime Beauchamp: And do some custom ranges. + +Maxime Beauchamp: So yeah. The issue is there. We'll get to it at some point or… + +Maxime Beauchamp: someone from the community. You want to implemented their more than welcome to do it. + +Tyler Wright: I see a hand up. + +Tyler Wright: Go ahead. + +Maxime Beauchamp: if someone wants to do it for sure the best way to approach this would be to do a short meeting with us so that we're aligned with The library choice in the implementation. + +Tyler Wright: Thank you Max, I guess from that perspective because I know being Max C are working on a number of things is that an issue that you think a Community member can tackle and… + +Maxime Beauchamp: So yeah. + +Tyler Wright: has a sense of resources to be able to tackle right now or do you think somebody might have some questions and should ask them before getting started? + +Tyler Wright: excellent + +Tyler Wright: All right. + +Tyler Wright: Thank you Max Steve. Does anyone else have any questions again? We got to update on Max C and he's dropped in chat some of the PRS that have been worked on recently much appreciate that as well as how folks can kind of track the repo and monitor and again how folks get involved if they so desire to help continue to improve indexer and some of the things around the indexer. So again, if anybody wants to get involved on is listening to this or again is getting feedback from somebody in the community. Feel free to reach out to myself Maxi or Max B and Discord because set up some time to connect with you, help you get on boarded and then, aligned on projects and then off the races. It's certainly supportive needed. Excellent. Thank you Robert. again, if anybody from the community again, there's a zeely community where there's a number of bounties and missions that are available to folks. So if anybody wants to get involved there's a working group. There's a entire daily dashboard. So feel free to get involved Is there anything else that anybody wants to discuss that hasn't been discussed on the analytics front? + +Tyler Wright: + +Tyler Wright: Max B. Mac said I just want to see if there's anything else to potentially you want to cover for this edition of the buy monthly meeting. If not don't feel applies, but it's fun to give you the platform because I know that she goes working on a number of things. Go ahead Robert. + +Tyler Wright: + +Tyler Wright: If not, Go ahead Max. + +Maxime Beauchamp: Bad nothing for me. So I wanted to make that here. + +Tyler Wright: I appreciate All if there's nothing else again, we try to have this meeting by monthly just to connect with the community if there's some Community involvement again appreciate some of the questions that have been coming in summer suggestions through telegram through Discord keep that up. And again, if you want to get more involved there'll be something in the notes be available for folks that want to contribute some more go ahead next. + +Maxime Beauchamp: I think it could be a monthly meeting for analytics. I don't know what you think about it. + +Tyler Wright: You think go back to being a monthly meeting from monthly? + +Maxime Beauchamp: Why yeah was it it was a monthly and then it got to buy monthly. + +Tyler Wright: Yeah, yeah, it was monthly for a while and I think as of six months ago we changed it to every other month because some people thought there was mostly just you and Maxie giving updates and at that time there was less updates to be had. I have no problem. If we want to get more contributions and meet more consistently to have it every month. But I really leave that up to you and Max C because you all are the greatest contributors to the indexer as of right now. + + +### 00:10:00 + +Maxime Beauchamp: By monthly is every two months my bad. + +Tyler Wright: Yeah. + +Maxime Beauchamp: I mixed it up with weekly. + +Tyler Wright: Yeah by monthly it's every two months yeah + +Maxime Beauchamp: But yeah, every two months is + +Maxime Beauchamp: okay, my bad. Yeah, it's fine like this. + +Tyler Wright: No problem. No problem. + +Tyler Wright: + +Tyler Wright: Yeah, so we'll keep this again at every other month. And again, if anybody has any comments concerns again, please get involved in this again analytics Discord Channel, we can create some sort of one-off working group sessions, especially at folks want to get involved and contributing to the indexer like we've done the past. So again, if you desire to get involved and contributing look at some of the repos and preset Maxi has dropped in as well as this again familiar familiarize yourself with the console in general. + +Robert Del Rey: Thank you. Thanks, Max and stay safe everybody. + +Maxime Cyr: That's good. So + +Tyler Wright: And then again, we'll look to connect every two months as just an update on what's going on in the analytics side and see if there's anything worth discussing it more detail live. But much appreciate everyone's time today. Thank you again Robert for dropping in the daily word for this call. Hope everyone has a great rest of the day and thank you to those listening to the recording later. Feel free to get involved when you can. Bye-bye. + + +### Meeting ended after 00:24:11 👋 + +_This editable transcript was computer generated and might contain errors. People can also change the text after it was created._ + From 59bc1879650d75daedd6f822387ac94fda611512 Mon Sep 17 00:00:00 2001 From: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Date: Fri, 23 Aug 2024 01:44:08 +0000 Subject: [PATCH 2/9] Create meeting notes for Sig-Client #17 (#668) * Create meeting notes for Sig-Client #17 Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> * Update 017-2024-08-20.md added transcript Chore: add recording link Signed-off-by: Drinkwater * Update 017-2024-08-20.md added 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-clients/meetings/017-2024-08-20.md | 301 +++++++++++++++++++++++++ 1 file changed, 301 insertions(+) create mode 100644 sig-clients/meetings/017-2024-08-20.md diff --git a/sig-clients/meetings/017-2024-08-20.md b/sig-clients/meetings/017-2024-08-20.md new file mode 100644 index 00000000..a0d74c55 --- /dev/null +++ b/sig-clients/meetings/017-2024-08-20.md @@ -0,0 +1,301 @@ +# Akash Network - Clients Special Interest Group (SIG) - Meeting #17 + +## Agenda +- Updates on Clients Built on Akash +- Terraform and Go Client Libraries +- Updates from the Console Team +- Discussion of Console 2.0 +- Open Floor for Questions and Additional Agenda Items + +## Meeting Details +- Date: Wednesday, August 20, 2024 +- Time: 08:30 AM PT (Pacific Time) +- [Recording](https://4mgemilgnadqtihidt2lpu7ocnkirkq4voj2pabf64hw5zdlqh3a.arweave.net/4wxGIWZoBwmg6Bz0t9PuE1SIqhyrk6eAJfcPbuRrgfY) +- [Transcript](#transcript) + +## Participants +- Anil Murty +- B S +- Dominikus Brian +- Jigar Patel +- Maxime Beauchamp +- Maxime Cyr +- Rodri R +- Tyler Wright +- ⻲人小河 + +## Meeting Notes + +### Introduction +- **Tyler Wright:** + - Welcomed participants to the bi-monthly SIG Clients meeting. + - Focus of the meeting was on updates and developments related to clients being built on the Akash Network. + +### Updates on Clients +- **Tyler Wright:** + - Provided an update on Cloudmos, now rebranded as Console, which continues to be the primary deployment tool on Akash. + - Mentioned the upcoming Cosmos SDK 47 upgrade and its potential impact on both Terraform providers and Go client libraries. + - **Terraform Providers and Go Libraries:** + - Work is already planned to address compatibility and functionality with the SDK upgrade. + - Detailed discussions on these updates will be deferred to future meetings. + +### Changes in Meeting Cadence +- **Tyler Wright:** + - Announced a change in the meeting frequency from monthly to bi-monthly. + - **Reason:** The availability of updates from other sources, including the steering committee and product/engineering roadmap, reduced the need for monthly meetings. + - Emphasized the importance of the SIG Clients Discord channel as a primary communication and update platform. + - Encouraged members to share ideas for improving the user experience or adding new features to Console via Discord. + +### Console Team Updates + +- **Tyler Wright:** + - Transitioned the discussion to the Console team for updates on recent work and future plans. + +#### Updates from Maxime Beauchamp: +- **Managed Wallets on Console:** + - Significant progress has been made toward enabling managed wallets on Console. + - The feature is designed to abstract away the complexity of managing on-chain wallets, making the platform more accessible to users. + - **MVP (Minimum Viable Product):** + - Near completion, with plans to release it to production shortly. +- **Bug Fixes:** + - The team has been actively addressing bugs reported by users. + - Focus has been on improving the overall user experience, especially as the platform sees increased usage. + +#### Updates from Anil Murty: +- **Trial Wallet Implementation:** + - Focused on the implementation of managed wallets and the integration of credit card payments on Console. + - **Trial Wallet:** + - Allows users to experience Console without needing a wallet or login. + - Currently in beta testing within Overclock Labs, with plans to extend testing to a broader audience soon. + - Potential use in an upcoming hackathon in India as part of the extended testing phase. +- **Shared Packages:** + - The codebase has been reorganized to separate shared packages. + - **Impact:** + - This restructuring allows for parallel development of different components, such as the new user interface for the provider console. +- **Persistent Storage Tracking:** + - Persistent storage is now being tracked in Console's statistics, in addition to ephemeral storage. + - **Benefit:** + - Enables more accurate monitoring and reporting of storage usage across providers. +- **Exponential Backoff Algorithm Update:** + - The algorithm has been updated to improve the user experience by ensuring new providers appear online more reliably and quickly. +- **CICD Progress:** + - Significant progress has been made in enhancing the CICD (Continuous Integration/Continuous Deployment) pipeline. + - **Features:** + - Users will be able to connect their repositories (GitHub, Bitbucket, GitLab). + - Automatic building and deployment of applications. + - Triggering redeployments based on new pull requests. + +### Discussion and Feedback + +- **Tyler Wright:** + - Expressed gratitude for Anil’s updates and invited attendees to ask questions regarding the Console team’s progress. + - Highlighted the work of Jigar and Duval in integrating the Prater app into Console. + - Mentioned that more details would be discussed in the upcoming SIG Providers call. + +- **Dominikus Brian:** + - **Positive Feedback:** + - Praised the new SSH key generation feature, describing it as user-friendly and convenient. + - **Concerns:** + - **Bid Availability:** + - Reported issues with selecting providers due to configuration mismatches. + - Suggested that instead of failing bids, there should be an option to select lower configurations when the requested ones are unavailable. + - **Connection Stability:** + - Noted occasional instability with connections when using Console. + - **Suggestions:** + - Proposed implementing a system to show available bids that are close to the requested configurations. + - Suggested exploring the integration of Docker files to provide more detailed assessments of requirements for Dockerized applications. + +- **Anil Murty:** + - **Bid Availability:** + - Acknowledged the issue with filtering out some providers based on default values. + - Mentioned ongoing work to update the value from 1000 to 10,000 to include more providers, with changes currently in progress. + - **Design Choices:** + - Discussed the intention behind certain design choices aimed at simplifying the user interface for less technical users. + - Appreciated the feedback on potentially adding more detailed options and raw data views. + - **Persistent Storage and GPU Configuration:** + - Confirmed ongoing updates aimed at improving the visibility and management of persistent storage and GPU configurations. + - **CICD Pipeline Integration:** + - Reiterated the exciting developments in the CICD pipeline, including automatic Dockerization and repository integration. + +### Awesome Akash Templates + +- **Tyler Wright:** + - Encouraged contributions to the "Awesome Akash" repository. + - Mentioned that templates from this repository automatically integrate with Console. + - Invited attendees to contribute any Dockerized templates that might be valuable for others in the Akash ecosystem. + +### Client Contributions + +- **Tyler Wright:** + - Highlighted the ongoing efforts of contributors and the community in addressing smaller issues related to Console. + - **Community Pool Support:** + - Acknowledged the financial support from the community pool, which has been instrumental in funding CICD improvements. + - **Good First Issues:** + - Emphasized the availability of "good first issues" for those interested in contributing. + - Advised newcomers to start by running Console locally on their machines and exploring the available documentation. + +### Call to Action + +- **Tyler Wright:** + - Reminded attendees to stay involved by participating in discussions within the SIG Clients and Console ecosystem channels on Discord. + - Reiterated the importance of community feedback and engagement in the ongoing development of Console. + +### Feedback from Dominikus Brian + +- **Help and Guidance in Console:** + - Suggested implementing a help button or agent within Console to assist users by suggesting requirements and guiding them through various tasks. + - This feature would improve the overall user experience, especially for those unfamiliar with the platform’s intricacies. +- **Future Enhancements:** + - Expressed openness to contributing more ideas as he continues to use and test Console, particularly around making the tool more intuitive. + +### Acknowledgements and Next Steps + +- **Tyler Wright:** + - Extended thanks to George for supporting with meeting notes and to Maxime, Anil, and Dominikus for their contributions. + - Emphasized the importance of community involvement. + - Announced that more detailed discussions on Console 2.0 will take place in the SIG Providers meeting. +- **Looking Ahead:** + - The SIG Clients group will reconvene in two months, with ongoing updates provided via social media and the product and engineering roadmap. + +### Closing Remarks + +- **Tyler Wright:** + - Thanked participants for their contributions and updates. + - Encouraged staying connected between meetings via the SIG Clients Discord channel. + - Mentioned that any additional updates from other teams would be shared in the Discord channel before the next meeting. + +## Action Items + +- **Anil Murty:** + - Continue working on improving bid availability and capturing more scenarios related to bid issues. + - Review and potentially integrate Docker file assessments into the Console experience. + - Oversee the broader beta testing of the trial wallet feature and ensure readiness for the upcoming hackathon. + +- **Maxime Beauchamp:** + - Proceed with planned updates to the bid filtering system. + - Continue finalizing the MVP for managed wallets and prepare for its production release. + +- **Tyler Wright:** + - Share meeting notes and recordings with attendees. + - Prepare for the upcoming SIG Providers meeting focusing on Console 2.0. + - Coordinate with teams working on Terraform providers and Go client libraries to ensure updates are made ahead of the Cosmos SDK 47 upgrade. + +- **Console Team:** + - Explore the possibility of integrating a help agent within Console to assist users with real-time suggestions and guidance. + - Continue to engage with the community for feedback and contributions. + - Provide further updates on their work and future developments, particularly related to Console 2.0. + +- **Dominikus Brian:** + - Test different GPU and storage options and provide feedback. + +# **Transcript** + +Tyler Wright: All right, welcome everybody to Sid clients by monthly meeting. During this special interest group for clients the group here gets together to discuss anything that's going on with any clients being built on Obviously one of the first clients that was built on top of Akash was Cloud most which is now again update on Console being that again. It's the leading deploy tool for how people Deploy to + +Tyler Wright: I know there's some folks that usually join us that can't make it here that talk about terraform and also the gold client libraries. I know there's going to be a fair amount of work that goes on there as we move into the cosmos SDK 47 upgrade. So again when that test net starts some of the themes behind terraform providers as well as the go client libraries, we'll have again some additional work cut out for them in terms of making updates to those clients ahead of the network upgrade. So again, that work already been mapped out and discussed. I'm sure we'll have Some further discussion between meetings if not the next meeting. + +Tyler Wright: As a last couple of months, we've changed a Cadence where this used to be a a monthly meeting just because again, there's a number of other places including the steering committee the product and Engineering roadmap where you can get updates from the Consulting all the work that they've been doing on the client side. Again, there's a number of other teams that are building various clients on top of Akash or having the past getting them to join this meeting sometimes difficult because again, they have other responsibilities so we look for updates from anybody that's building any clients on top of Akash to again, feel free to chime in to the Sig clients Discord channel to give updates. If you're cannot make these meetings or if you have ideas for things that you want to add to console or things that you want to add to the user experience and maybe a form of another client again, always + +Tyler Wright: Looking for folks that are building the cost to join these conversations get involved talk about problems that they're facing Etc. + +Tyler Wright: you can also track many of the past meetings in the community repo. There's a sick clients folder where you can track again some of the stuff going on. I know there's been a big plan that was discussed at the last meeting about everything happening with console 2.0. So again, we'll just get update on some of the work on console and then if anybody has any questions or any agenda items that they want to talk about feel free to drop those in the chat and then we can talk about those here today. + +Tyler Wright: But I do want to hand it over to the console team again. We take a part of this agenda to get updates on all the work that the console team is doing across a number of different initiatives. We've talked previously about some of the work related to the indexer during this again analytics by monthly meeting. So we don't have to necessary talk about that here, but I want to hand it over to their Consulting. Maybe Max Anil to talk a little bit about some of the advancements over the last couple of months and look ahead of maybe what's to come? + +Maxime Beauchamp: Sure Anil you want to go? I can go. + +Anil Murty: Sure, or you can go first. + +Maxime Beauchamp: But yeah, I will wait in the past month and there's been a lot of effort and progress towards enabling managed I will on console. so users will soon be able to make complete abstraction the Wallets on chain. So everything will be so a lot smoother for users. So that is almost. The MVP is done, and we're almost there to release it on production. + +Maxime Beauchamp: We've been working in hard as well on fixing bugs that customers are facing right now. There's an more usage more bugs that we find and we work hard on fixing these and just improving in the overall experience for her console users. + + +### 00:05:00 + +Anil Murty: So I know I can jump in a little bit. But yeah as Max said the big Focus for the core team has been to implement the first phase of managed wallets Plus Credit Card base payments in console. The very first phase of that is basically implementing what's called a trial wallet. And so the idea here, is that a user that comes into console? Should not have to have a wallet. She not even have to log in and can just try console without having to literally do any sort of sign up or login. and then once they try it and maybe do one or two deployments then they can choose to obtain to either a custodial wallet solution where we manage your wallet for them and they play using credit cards or a self-cously you want it where the experiences exactly the way it is right now in console. + +Anil Murty: So the very first phase of that is the trial wallet portion and that portion is currently in beta test within the ocl codeine with an overclock lab score team. So we're going to spend a few days later testing it outside of the engineering team within the broader or Cloud lab scheme here. And I'm hopeful that in the next few days, we'll be able to open up the beta for insiders as well as for. Potentially a upcoming hackathon that's going to be happening in India. So if you don't find any major issues with the trial experience this week, we're hoping we can actually use this for the hackathon. What's happening in India? So that's the big update. Other than that, if you look at the project board that Tyler shared some of the other big updates you'll see that Max talked about + +Anil Murty: which are in the bucket of enhancements as well as bug fixes. + +Anil Murty: some of the things we have done is we have carved out all the shared packages into a separate section inside the code base. And the reason we have done this is so that we can build things more in parallel across the team particularly as the pretor team is starting to work on the fronting new contained user interface for provider console, which will be basically a portion of console that is going to sit inside consort network, but it's going to be basically a new front-end for spinning up providers. So all that work can happen in parallel. Now that the shared packages are shared out and we can reuse components across the deployment console as well as the provider console. So that's issue number 230 on the list and then one of the other things that was added, I think since the last time we met here was persist in storage of being tracked now in the stats app as well as in So when you went to Stats or to console providers + +Anil Murty: stories that you'd see there was only ephemeral storage and in the last few months, you've added a bunch of providers with a lot of persistent storage and it was important for us to start tracking all that as well. So even though it's not broken up into its own thing into its own donut chart the storage overall storage now reflects both FML storage as well as persistent storage. So if you notice a little spike in the stories, that's what that is. and then the third significant thing worth calling out is we have also updated What's called the exponential back of algorithm for a new providers that are coming on to the network. So what this does is basically + +Anil Murty: improves the user experience of how fast a provider shows up on the network while it being set up and also if for some reason a provider failed to check before the exponential back of algorithm would back off to a day or more and that would sometimes cause the provider to show up offline even though it's technically online. And so that was a pretty big fix that Maxi made and that's one of the board right there. There's other things that are happening on the cd side. I don't see the human HQ team on here, but there's a bunch of progress that's happening on implementing. Basically what I call a versatile style experience within console and push and the human HQ team and as we sync up pretty regularly on those between these meetings and the pretty close to having a solution that'll work really beautifully within console where the user will be able to come in connect to a GitHub or big Market or lab repository be able to pull in their + +Anil Murty: application code and then have the backend basically the software build it for them deployed onto console and just give them a main point so that way they don't have to authorize their application. They don't have to write an sdl none of that. And then also basically Trigger for being able to redeploy the application every time there's a new pull request into the Repository. So that exciting stuff is coming as well. And in the context of that they're also going to be looking at some testing out some logging improvements of sending console logs to a third party logging service and then cleaning up the logs and thinking in the back into console. So I'm hopeful that those changes will get more into console before the next time we come here if not much sooner than that. So I think the crcd work combined with the trial wallets and the custodial payment solution is going to be a huge driver of option on Akash in the coming months. + + +### 00:10:00 + +Tyler Wright: You Max Ben. Thank you Anil for those updates. Does anyone have any questions on all the work that the client team has been doing in terms of console and again bringing members of the community to also help? + +Tyler Wright: Cool as Anil mentioned as well there with all the work that jigar and Duval have been doing on bringing the Prater app into console, but we'll talk a little bit about that a little more detail there in the state providers call happening tomorrow. But again just another shout out to all the work that they're doing to unify the console experience. Go ahead dummy. + +Dominikus Brian: Hi everyone. Thanks for the update guys. It's very great. I'm in this console is becoming more and more. I mean, I have just tried several of one concern with this plane Linux with SSH so I tried it several other days, I mean Using trying to SSS there. I love this, generate key function. that's a perfect thing and then everything is just there. You can download it. Then I can just copy the public key and stuff. That's as easy as it gets. I mean, you don't even need to generate it yourself and that's nice. I love it but there is some issue with choosing this providers. So most of the times depending on the configuration I asked for the building is not always available. + +Dominikus Brian: And then I need to sort of manually downgrade instead of getting an options to if say I'm not sure which one is not affordable. Maybe I'm asking too much of memory if it's asking too much of something. so the GPU is already pretty General I'm asking only for NVIDIA and then I'm not sure whether it's the storage too big and other things. I need to just keep trying several times. I think this is a things that can be improve. So either doesn't show a bidding for that. I will be shown some beading for lower, + +Dominikus Brian: Great for instance. I asked for 300. There is an options like 300 is not available. How about 200? And in this bidding is also there you don't need to show everything but I mean the closest one to that will be a nice thing because sometimes it's a bit irritating to close all the deployments bidding. And then I go again trying to with lower quality one. I mean that's a thing. I mean that maybe can help accelerate where people feel it's like failing other it's just a little bit of requirements. So yeah, that's one thing and another thing with this connections when connecting to that sometimes it's not stable. I'm not sure why + + +### 00:15:00 + +Anil Murty: the nice words on the SSH option or the VM option basically, but yeah, we have heard very similar things from a lot of other users in customers as well for the longest time people would struggle with setting up their SSH from their own terminal and giving them this option and then also having the references deal in Akash is going a long way these days in terms of getting those customers onboarded. So we've heard very similar things where people are This is very much like the experience where we get to see in front if not, ec2 itself. So that's great. I want to address the two things that you mentioned or the I think the first thing you mentioned was something around. Not being able to get bids and not being able to sometimes adjust your parameters. So I think + +Anil Murty: there's a couple of things there and I want to make sure I capture your feedback. So one is in two places in the rent GPU page as well as in the page. What we were doing was we were defaulting the ukt value to 1000 and that filters off some of the providers that are more expensive some of the G2 providers are more expensive and so as we speak Max B's actually going to make this change. In fact here request open right now for updating all the awesome Akash SDS as well. And that will basically up this value from 1000 to 10,000. So it is an exit and so you should be getting pretty much every provider covered with that. So no provider should be getting filtered out. So that's one the second is I know that in the + +Anil Murty: as well as in the rim GPU, I'm just gonna check this again as I do this, but in both of these options, we actually don't show the noise here. That's just a design time choice that we made. we have to go with some more thing. We wanted to keep it as easy as possible with the assumption that these users are relatively less technical compared to the other users or something like that. So we hit the raw. I see from the ram GPU page as well as from the VM template, but if you think that that is something that we should consider adding that is something we can certainly look adding into that as well. It's something that we have another templates. So that's number two. There was another question that you had that I think I've kind of lost track of but just want to pause their see if you have any feedback. + +Dominikus Brian: Yeah, that's great. I mean I tried that video akt it doesn't help at the time. Maybe the other is busy. But I haven't tried much with other options with the friend GPA GPU directly without the get used to the STL. But yeah, I'll check and try the other ones and see whether it can give me more options. I'll write it back when I've tried more of them. + +Anil Murty: Yeah, that'd be great Both of them have all the options for adjusting everything. The only thing they don't have is the actual rise deal. so you should be able to change everything. It's like the GPU weapon will storage all of that but + +Dominikus Brian: Yeah, that's going to be very nice functions. Yes. + +Dominikus Brian: Sounds great. + +Tyler Wright: Perfect. Anything else go ahead. + +Dominikus Brian: And maybe it can go up together with the docker eyes. I mean you guys mentioned that in the future soon enough, we'll have this, Auto docorization from GitHub and everything. so there is the same functions that makes just describe what actually helps, giving users assessments of What's the requirement for this Dockers as the storage wise and things like that? So it will be nice if it's combined together. I guess that's all from me. Thank you. + + +### 00:20:00 + +Tyler Wright: Academic go ahead and deal. + +Anil Murty: Yeah, so on that point and I had forgotten what the third question was. Thanks for reminding Max B. So on the topic of how do we increase the likelihoods of bits being received? I actually created an issue to basically collect all the possible scenarios where that problem can happen. So if you have any other Feedback or other situations where you think this could happen or other ways of handling it feel free to comment on that issue as well. But I try to capture all the possible scenarios in + +Tyler Wright: Queen anything else on console and he wants anything anybody wants to discuss. Pardon me? + +Tyler Wright: I know it's been much discussion about awesome Akash as well. So again, please feel free to look at awesome occasion of the templates from Austin makash automatically go into console as well. So again, feel free to contribute to the awesome Akash repo if you see anything that you think might be great to dakarize and again put an awesome Akash for others in the Akash ecosystem again, feel free to contribute there as well. + +Tyler Wright: Are there any other discussion points that anyone wants to talk about related to clients on Akash? + +Tyler Wright: make sure that the notes are made available. Again. This is a monthly meeting much appreciate the updates from Max B from Anil the commentary from Domi all that is very thankful for all the work that the client team has been doing on the Shout out to whom who was also been supporting with some efforts on the CIA cicd side after getting some money from the community pool to support console. They're also been some contributors that have been getting involved in tackling some small issues related to console. So again, as more of those smaller issues get started or are made available, we'll have the core engineering team continue to work on a number of the big efforts continue to + +Tyler Wright: time to connect with the community talk about updates talk about all the work that they're doing get more people involved and again, there will be continued to be good first issues. One thing that we always ask if anybody wants to get involved in contributing to console. One of the first things to do is again, Look in the console repo and download our get console locally on your machine. That's a great first touch point to look at the again documentation and be able to run console locally. And then again, once that's done feel free to reach out to myself and Sid clients Channel or look in the issues inside the console repo and see if there's any good first issues for Community contribution. Go ahead and kneel. + +Tyler Wright: Sorry, excellent. Thank you very much Anil for sharing that and putting that together. Great again, if there's nothing else then we can certainly wrap up if there's any other notes or updates from any other teams. I'll make sure that those get added inside the stick client Discord channel in between meetings. Again, if anybody has any questions or conversation or any ideas, feel free to continue to drop those inside of the Sig clients Channel again, if it's specific to the console, there's an ecosystem console Channel as well where you can talk about any active issues again, we talk about some of that stuff during the six support. But again, there's all the issues that you can kind of track on the console side that's been dropped in chat here and yeah, I'm sure there will be a lot more to go ahead dummy. + + +### 00:25:00 + +Anil Murty: and so it would fit with AC clients even though You may be crunching data from the network and stuff like that to figure out which is a provider. + +Dominikus Brian: I Thank you for it. But yeah, because I think that's a great thing when you can have so in your say consoles a kind of help. Button, and then this agent basically, assists You actually need to do this or do that or things like that? I mean suggest you a little bit on requirements and stuff. But you need to train a lot of things maybe in the future if I have something on that are updated here. Thank you. Okay, that's it I guess. + +Tyler Wright: Mason excellent again, I'll make the notes in the recording available on very shortly again. Shout out to Gorge for all of the support with some of the notes again much appreciated the update from Max B from Anil some of the questions and comments from Domi great conversation. We'll talk a little bit more around the provider side of console during the sick providers a discussion where jigar and Devol will talk a little bit more about all the work that they've been doing relates to council 2.0. So look out for that sick providers meeting happening tomorrow. + +Tyler Wright: But yeah again much appreciated everyone's time today will reconvene in two months. But in the meantime, we have Sid clients, we have the product and Engineering roadmap that gets updated fairly frequently and look out for a number of updates in various channels on social media related to all the work that again the core team is doing as well as human HQ and many other teams that are working on console and other clients but much appreciate everyone again. Hope everyone has a great rest of the day. Thank you very much. + +Jigar Patel: Thanks. + +Maxime Beauchamp: Thanks, everyone. + +Anil Murty: Thanks, everyone. + + +### Meeting ended after 00:42:00 👋 From e36445154a570d5f6acfdba904e41c3ccc331fd8 Mon Sep 17 00:00:00 2001 From: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Date: Mon, 26 Aug 2024 08:45:29 +0000 Subject: [PATCH 3/9] update notes with additional info (#669) Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> --- sig-chain/meetings/019-2024-08-13.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/sig-chain/meetings/019-2024-08-13.md b/sig-chain/meetings/019-2024-08-13.md index db870f4c..2470cad6 100644 --- a/sig-chain/meetings/019-2024-08-13.md +++ b/sig-chain/meetings/019-2024-08-13.md @@ -46,7 +46,7 @@ - **Zealy Mission Announcement (Robert Del Rey):** - Robert wished the team good luck with the network upgrade efforts. - Introduced the secret word for the Zealy mission related to the Sig Chain working group call. - - Secret word: **"November"** spelled out as N (November), O (Oscar), V (Victor), E (Echo), M (Mike), B (Bravo), E (Echo), R (Romeo). + - Secret word: **"Node"** spelled out as N (November), O (Oscar), D(Delta), E (Echo) - Participants can use the secret word in the Zealy mission to earn additional AKT points while engaging in Akash Community initiatives. - **Closing Remarks (Tyler Wright):** @@ -57,11 +57,11 @@ - Announcements will be shared over the next few days into the following week as preparations for the testnet advance. - Tyler thanked everyone for their time and participation, indicating the meeting was adjourned. ## **Action Items** -1. **Artur Troian:** Continue preparing testnet and test cases for SDK 47 upgrade. -2. **Tyler Wright:** Reach out to community members and validators interested in participating in the testnet. -3. **Core Engineering Team:** Finalize the testnet requirements and ensure readiness for the upgrade by the next meeting. -4. **All Participants:** Stay engaged with the community and prepare for the upcoming network upgrade; watch for announcements on specific requirements. -5. **Tyler Wright:** Schedule additional community calls as needed leading up to the network upgrade. +- **Artur Troian:** Continue preparing testnet and test cases for SDK 47 upgrade. +- **Tyler Wright:** Reach out to community members and validators interested in participating in the testnet. +- **Core Engineering Team:** Finalize the testnet requirements and ensure readiness for the upgrade by the next meeting. +- **All Participants:** Stay engaged with the community and prepare for the upcoming network upgrade; watch for announcements on specific requirements. +- **Tyler Wright:** Schedule additional community calls as needed leading up to the network upgrade. # **Transcript** From 74f870fd43a3b2cef49d736efd9bc194a9c02c8b Mon Sep 17 00:00:00 2001 From: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Date: Tue, 27 Aug 2024 08:26:24 +0000 Subject: [PATCH 4/9] Create meeting notes for Sig-Support #36 (#671) * Create meeting notes for Sig-Support #36 Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> * Update 036-2024-08-21.md added transcript Chore: Add recording link Signed-off-by: Drinkwater * Update 036-2024-08-21.md added 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/036-2024-08-21.md | 318 +++++++++++++++++++++++++ 1 file changed, 318 insertions(+) create mode 100644 sig-support/meetings/036-2024-08-21.md diff --git a/sig-support/meetings/036-2024-08-21.md b/sig-support/meetings/036-2024-08-21.md new file mode 100644 index 00000000..307142ba --- /dev/null +++ b/sig-support/meetings/036-2024-08-21.md @@ -0,0 +1,318 @@ +# Akash Network - Support Special Interest Group (SIG) - Meeting #36 + +## Agenda + +- Review issues awaiting triage in the support repo +- Discuss any open issues or support-related topics +- Update on console-related issues +- Community support and Discord updates +- Any other support-related items + +## Meeting Details + +- Date: August 21, 2024 +- Time: 07:00 GMT-7 +- [Recording](https://wrx26ds6t7sofpahkzy5iphq7eqtfu3jln6xf5idxmrr2url4m5q.arweave.net/tG-vDl6f5OK8B1Zx1Dzw-SEy02lbfXL1A7sjHVIr4zs) +- [Transcript](#transcript) + +## Participants + +- Tyler Wright +- Scott Carruthers +- Andrey Arapov +- Maxime Beauchamp +- Rodri R +- Zeke E +- Other attendees (not explicitly mentioned in discussion) + +## Meeting Notes + +### Review of Issues Awaiting Triage + +- Scott Carruthers led the review of issues awaiting triage in the support repo + +- Packet forwarding issue: + - Opened by Tyler Wright + - Awaiting Cosmos SDK 47 upgrade + - Classified as P2 priority + +- Lack of visibility for deployers on exit codes of failed deployments: + - Opened by Andrey Arapov + - Assigned to provider repository + - Classified as P2 priority + - Considered a good feature for users to see reasons for deployment exits + +- GPU device plugin issues with inventory operator: + - Opened by Andrey Arapov + - Assigned to provider repository + - Issue occurs when NVIDIA GPU device plugin marks devices as unhealthy + - Mainly observed on Oblivious H100 PCIe provider + - May be related to virtualized environments + - Recovery methods discussed: bouncing NVIDIA device plugin, rebooting node + +### Console-related Issues + +- Maxime Beauchamp brought up issue #227 regarding exposing manifests via API: + - Proposal to add an endpoint to fetch manifests + - Would solve issues with local storage and device changes + - Potential to add more metadata to manifests (e.g., deployment name) + - Discussion on progress of storing manifests on-chain (still in idea phase) + +### Community Support and Discord Updates + +- Increase in Discord scammer activity: + - Rodri R noted an increase in scammers engaging in channels and DMing users + - Tyler Wright acknowledged the issue and mentioned it would be discussed further in Insider office hours + +- General increase in Discord activity: + - More people joining provider and deployment channels + - Possibly due to recent events or increased awareness + +### Snapshot Service Update + +- Zeke E provided an update on the new snapshot service: + - Fully in production at snapshots.akash.network + - Pull request submitted for website documentation + - Requested feedback from users + - Will provide snapshots for upcoming Cosmos SDK 47 testnet + +### Cosmos SDK 47 Testnet Update + +- Tyler Wright provided an update on the Cosmos SDK 47 testnet: + - Currently on hold due to focus on provider-related issues and active workload concerns + - Code is mostly complete with some initial internal testing done + - Plan to create a Discord channel for testnet testing + - Looking for volunteers with extra infrastructure for testnet participation + +### Additional Notes + +- Scott Carruthers highlighted the importance of the new hourly snapshot service for providers, noting it will significantly reduce sync times +- Andrey Arapov made a recent announcement in Provider channels about updating to Provider Services version 0.6.4 + +## Action Items +- Tyler Wright to create a Discord channel for Cosmos SDK 47 testnet testing. +- Tyler Wright to follow up with the website team on merging the snapshot service URL. +- Core engineering team to continue work on provider-related issues and active workload concerns. +- Community members to test and provide feedback on the new snapshot service. +- Interested parties to look out for updates on Cosmos SDK 47 testnet testing. +- Discuss Discord scammer activity further in Insider office hours. + +# **Transcript** + +Tyler Wright: Alright, welcome everybody to Sig support. This is now a monthly meeting. August 21st 2024 During the special interest group for support the group goes over a number of things related to the core repos and oftentimes a console repo really the goal of the support is to have members of the Court engineering team go over any issues that are awaiting triage in The support repo is we're all issues related to the core code base for our costs the blockchain ETC live. So again members of the core engineering team + +Tyler Wright: go over any issues of waiting triage people on the call can talk about any open issues and again ask any questions about open issues if they want to get involved in helping to solve some of the again, this is a place to ask questions get involved talk about your skill set Etc oftentimes again, we cover issues related to console but I know some members that team may not be here again, if anybody has any issues related to the Akash console, there's a console repo as well as a Discord Channel. I know that the team behind console does a great job of staying up to date and staying very active in that repo. + +Tyler Wright: After we go over any issues awaiting triage, I usually see if there's anybody from the Akash insiders vanguards or anybody in the general community that maybe has some themes related to support that they see a Discord telegram or other facing channels. And then if anybody has any other comments questions concerns related to issues in the core code base or console again, feel free to drop those inside the chat and we can make sure that they get discussed. + +Tyler Wright: Without further Ado. I'll hand it over to Scott who will lead us through issues related to again the support repo and any issues we're waiting To Scott take it away. + +Scott Carruthers: All right. Thanks I share my screen. + +Scott Carruthers: Okay, so everyone able to see my screen in the open issues? so prior to the call,… + +Tyler Wright: Yes. + +Scott Carruthers: I was reviewing open issues specifically those awaiting triage, so I currently just have the Issues with that filter awaiting tree Ash pulled up. So as we can see we have three issues to review. So first one Tyler the packet forwarding I know that this is a issues that you opened. This is a waiting day Cosmos SDK. 47 upgrade before we can continue. Do you want me to just leave this in awaiting treehouse for the moment or do you want me to take it out of waiting triage and Do further assignment? + +Scott Carruthers: Do you want me just leave it as a yummy classified as a P2 for now? Okay. + +Scott Carruthers: Okay, so we have that one checked off and either and again, I reviewed these issues and it's already familiar with these but reviewed. These two issues prior to the call. both of these waiting triage. Once that are remaining our both opened by when a record team members Andy who may want to just speak further. So we don't have to Deep dive into them now, but if you have any comment I'll take so first of all, they lack of visibility for a deployer on the Akash Network to get the exit code of a failed appointment. So I think that's something that we've discussed recently and obviously would be + +Scott Carruthers: a great knowledge point to add to the network. So if a pod access because of out of memory or something of that nature, they deployer can get some feedback. So We're with that. Prelude anything for that you want to I'll take this out of a waiting triage and assign it into the provider repository. I'm doing that. Do you have any further comments or anything further on this that you want to discuss? + + +### 00:05:00 + +Andrey Arapov: No, it's good. Go ahead. Thank you. + +Scott Carruthers: Okay. Sure. + +Scott Carruthers: What would you prefer the classification on this a P2 P1? + +Andrey Arapov: It's definitely like Peter or something lower just like extra functionality for the users to see the reason the deployments are exiting with just kind of Good feature to her. So I'll be doing good. + +Scott Carruthers: Yeah. Yeah,… + +Andrey Arapov: Thank you. + +Scott Carruthers: absolutely. Okay, I'm gonna assign both our turn myself to this. I've classified as a P2 and then they provide a repository. + +Scott Carruthers: So now going back to open issues and essentially with the top so I don't even need to filter so again, so this is a matter that when they + +Scott Carruthers: the provider has Nvidia and the DP device plug-in issues on the inventory operator is not picking up on the fact that there are issues with that plug-in. So again, I'll assign this to the provider repository and as I'm going through the labeling assignment anything further you want to discuss on this issue. + +Andrey Arapov: My little shortly. It's basically when you have some issues with GPU and that module automatically marks the device for GPU devices are unhealthy. This event is quite rare so far. We have only served it on the oblivious h100 PSE provider. They're working on it to fix it and likely the issues related to the fact that provider is running in Puma virtualized environment and passing through the PSE h100 device through it as someone reported the same having the same. + +Andrey Arapov: Let it has seen the same issues on the Media Forum they started so in this installs we often see this kind of things are happening and that's how I actually noticed this issues at all. I just was watching no other was reporting HTTP so available and after querying it again after the GPS market on health by this model and assuming the price is still reported into Chris are available. But in fact it was like We'll say one GP was available and… + +Scott Carruthers: Okay, sure and decide I noticed in the issues. + +Andrey Arapov: wasn't picking it up. So yeah, because + +Scott Carruthers: You said that rarely you can recover from this occurrence by bouncing the mvdp device plugin. if that doesn't work? how have you been able to recover from this situation? + +Andrey Arapov: I + +Scott Carruthers: Otherwise by bouncing the inventory operator? + +Andrey Arapov: am it's like let me think. So basically the nvp device plugging is the one that is responsible for marking at gpus and healthy or detecting them at all. And when it detects the GPU you can actually keep cattle common describe notes or describe notes specific note if you're wondering and then you can see the amount of resources that com/gpu resource and we can see the amount of them and basically what an Android operator does he means I think information from there actually so kind of needs to, keep updating this information either from an old or from this. + +Andrey Arapov: Plugin directly, but in order to recover from it. First of all, we need to detecting this issue. So normally you would query the provider status on point and you would see it https are available, but the only way how to objective. Basically it's a chain of actions, which is someone is deploying the EGU workload on that particular note and then you notice You cannot access your department. We don't see your deployment is ever becoming ready. And when you are asking provider to check the provider side and Humanities point a few you want is that your board is basically stuck for our pending and what's happening in conversation that it cannot spawn because it needs more GPS but reports less GPS available as you can very good describe mode. + +Andrey Arapov: But then you see providers to reports all of them already and that's where this synchronization is at and to recover from it. It depends how bad presentation is. So They're two ways to recover it only Simply bouncing this invisibility model and hope that it actually doesn't Mark the GPU. That is unhealthy again. Sometimes it works. Sometimes it's not it depends how bad situation is and if it still marks the gpus unhealthy, you would have to reboot the note entirely simply on a simply unloading and video and reloading and video model. It's possible to do I want to talk for it if you're wondering but even that doesn't help in India semi reset command to gpus doesn't help low level so + + +### 00:10:00 + +Andrey Arapov: Yeah, and it's another factor that says in favor of the tissue is related to the visualization. So something has to do with the qmi or the way how the egpu has been passed through x-ray. + +Scott Carruthers: Yeah. + +Andrey Arapov: It's a good point here discussing it right now something to highlight. Yeah. and once you done this and the note is back up again, you can basically see old reviews are present normally which again highlights that it's issue likely is the firmware or the way how it's being passed through the key in my because physically is always back after the book. And there is another thing issues opened for this kind of issue for the inventory operator. I think with missing. + +Andrey Arapov: Was it? + +Andrey Arapov: I think it was 240. I think that a couple of issues similar to this but they're different so you need to Detective. In life mode and the other issues is that when you finish the inorder book that nvdp and with the device plugging in it takes some time to initialize about, three to five minutes and an entry operator starts earlier. And where is the information earlier and sometimes you would see the provider is supporting zero to use are available. in fact, if you roll out to start inventory operator deployment, it will correctly detect it. So I think this kind of precious are connected so it just needs to I believe frequently all the information from the note. + +Scott Carruthers: Yeah, I sense and good to go through that inside personally. Haven't hit the fdp device in issues. good to hear your series of events. So if restarting the mvdp vice plugin doesn't work reboot in the note preview booting the node entirely as prevent to cure the issues. So yeah good to walk through that and I guess there's any providers that on the call or listen to the recording that haven't encountered that yet. So yeah. + +Scott Carruthers: Yeah. + +Scott Carruthers: Yeah, okay. Yeah, thanks for that review and I'll make sense. So that brings us through the issues that were previously awaiting triage. Does anyone have Questions about any of those issues that you want to Deep dive in a little further or possibly any questions about issues that we haven't covered so far. + +Scott Carruthers: Okay, if there's nothing else I'll hand it back to Utah. + +Tyler Wright: Excellent. Thank you very much Scott again. I just want to see if there's anything else from the support repo that anybody wants to discuss. + +Tyler Wright: I know there's a representative from the consult team, one of the original developers of clouds, which is our console. So always want to shout out Max. Does anyone have any issues related to the console repo that they want to discuss are any issues and console that they want to discuss at this time? Of your hand up. Go ahead rodri. + + +### 00:15:00 + +Tyler Wright: Yeah, I've noticed this too. We've talked to some insiders and we try to tighten up on some of the mod words. But to be honest some of this behavior. I'm not really sure what we're gonna do. I think we'll talk about a little bit more about it during The Insider office hours, again, they cost insiders is a special group of ambassadors that works on volunteer basis to provide support in Discord a number of other channels both non-technical support. So again, we'll take some time during the entire office hours to discuss this a little bit more and see if there's anybody that has any specific strategies. I know that Max dropped an issue prior to that. Is there any other? + +Tyler Wright: Items on the support side that I've seen really a lot more people in providers channel is also and also unemployment's channel. So I think again whether they're coming off of events or just general awareness there seems to be a fair amount more people in Discord. I've heard from a I've heard from some Partners recently as well that it getting involved in Discord. There's + +Maxime Beauchamp: Thanks Yeah, I talked about this issues with Arthur and I think I just want to bring it up to Scott as well out of you wherever it but yeah, It's probably not that big of a change to implement, but yes to expose the manifests. to the API so the way that we like query the logs are the events with the certificate. We would add an extra point to get the Manifest. So that way instead of storing it in the local storage like we do in console. + +Maxime Beauchamp: And if you change device or browser, it doesn't follow you and connect your wallet. if we had an endpoint to this we would just fetch it and then that problem would be solved and also. Arthur was talking about + +Maxime Beauchamp: Art, there is aware. Just wanted to put a little bit more light on the issues. + + +### 00:20:00 + +Scott Carruthers: Yeah, thanks for reviewing that Max and completely makes sense. as you were described in that I now have a little bit for their Insight. So we've talked at different points about story and manifests on chain. So someone could to ease the friction on deployment to a new provider or obviously there could be automation built around that as well. But the current focus of + +Scott Carruthers: Having a manifestive API so that's the part that wasn't following initially is why that helps if life for automations schemes and past conversations where we're going to have the manifests possibly on chain or stored elsewhere so that in automation you could redeploy to another provider easily. So I wasn't sure how exposing the manifests who are provider API would solve that issue issues that we're currently trying to solve is instead of storing it The sdl and local storage. So if someone brings up console on another device console want to have access to it that use case makes complete sense. I'm glad you went over that and yeah, I'm a little clearer now and as you said, I know the Archer is aware of this issues. So I think we're Contemplating how we're going to move forward. + +Maxime Beauchamp: Cool. Thanks Scott. + +Tyler Wright: It looks like even as quick as recently as yesterday. There's been some reference of this issue on the provider side. So thank you again Max for bringing this up and talking about a little bit more. Is there any other action that you want done or I guess I've looked at the issue and you've mentioned a number of the items at the top of it. But it is there any other specific functionality that maybe is not an issues 227 that you want to make sure it's very clear for the core engineering team. I know you already talked to Archer and obviously just recently brought it back up to Scott. But is there anything that can be added to that issue just to make sure that everything you're looking to be solved is sold or is it pretty much up to date? + +Maxime Beauchamp: They just pretty much up today. There's an image to it. Unless some Scott you think. + +Tyler Wright: . + +Maxime Beauchamp: It's not clear enough, but I think it's pretty straightforward. Yeah. + +Scott Carruthers: Yeah, no. Yeah, especially with the further conversation. I'm definitely Claire so I think we're good. + +Maxime Beauchamp: Is there any progress today and storing the Manifest unchain, or is it still just an idea? + +Maxime Beauchamp: Yeah, no worries. Just wanted to ask. + +Tyler Wright: I thought two hands up. I don't know what order. + +Tyler Wright: Perfect. + + +### 00:25:00 + +Tyler Wright: Excellent. Thank you Roger. + +Rodri R: The get with my turn now. + +Tyler Wright: Go ahead. + +Rodri R: Look Andrew said and Scott and Maxim makes it great idea to store the Manifest unchain. Not sure if this has anything to do with this, but just two weeks ago. I learned I deployed for my new address and console didn't ask me to Create a new manifest. Is this something that was added recently because before in Cloud moves, I remember we had to sign the first grade. I mean, I would have to create a manifest and they would deploy Kepler or Wale whatever and I would have to pay for that and now I just deployed without creating. I'm a manifest. + +Rodri R: Asking because Melton the others know that it's not necessary anymore. Am I correct? + +Maxime Beauchamp: Wait a minute. I'm not sure what exactly you're referring to and you're saying there's no need for a manifest. + +Rodri R: Yeah, like I said, I recently created a new wallet two weeks ago. I deployed from console and it did not ask me to sign up any manifest. It was a new wallet. + +Rodri R: So I was kind of surprised because I thought it was a new feature. And I didn't have to sign manifest before on Club moves. + +Maxime Beauchamp: Like the SEO you mean? + +Rodri R: No if you remember in Cloud mode Before even deploying you had to pay I don't know 0.0001 akt to create a manifest. And now he created it automatically for me in console. + +Maxime Beauchamp: I mean the certificate. + +Rodri R: Okay, it's different. Yeah certificate. Yeah, my bad. + +Rodri R: Okay, my Yeah is the certificate so this is different. + +Tyler Wright: awesome All right, again, we've talked about any issues that are awaiting triage and we went over some of those issues from the support repo. + +Tyler Wright: We've talked a little bit about inside and saw if there's any questions for anything console related Max brought up an issue that will have an effect for client side. Many users issues issues number 227. We're just discussing that we talked to members of the Insiders about just against support in Discord and some things that we've been noticing over the last couple of weeks. I want to see if there's anything else anybody wants to discuss related to support again. This used to be a weekly meeting where we change it to monthly just because there's again many things being worked on we have the product and Engineering roadmap. And then again, if anybody has any questions between these monthly meetings we can discuss them in the Sig support Channel or people can leave comments under a specific issue and again that can get some traction. You see a hand Go ahead Zeke. + +Zeke E: Yeah, I got two things first thing. I just wanted to give an update on the snapshot service. So it's fully in production. Now, you can access it at snapshots.cost.network. I did a pull request in the GitHub repo for the website for the documentation such as waiting to get approved. So that way we can start using that more widely. If you have any questions or feedback if you use it, I'd appreciate it as we continue to scale it up. And then just is there any update regarding the cosmos sdk47 testnet? + + +### 00:30:00 + +Tyler Wright: As of right now there is no update the hope is that over the next couple of days to a week. We will get that started. I know we've said that previously but there's just been a couple of other issues. I think you could see some of the commits that have been going on from the core engineering team, but there's some other provider related issues and some other issues related to active workloads that the core engineering team has been focusing on over the last two weeks and that has put next steps in terms of the cosmos SDK 47 upgrade on hold temporarily again, we're in a point where mostly we're code complete. There's been some initial testing done internally that's like automated testing and to Zeke's point. We're starting to gather some folks together that are technical that can help us. + +Tyler Wright: Test out the cosmos SDK 47 migration Scott and I were actually talking about a plan yesterday. So again, in terms of next steps, I'll start to put together a group. I know there's some people on this call and some people in the community that showed interest and initial testing. I'll create a specific Discord channel for that testing and then again over the next couple of days. we'll share some instructions and next steps. There are some validators and some providers that again if they had some extra infrastructure, we would love to leverage for the testnet. But again, I've reached out to folks there, but please look out for updates in various channels. And again, I appreciate everyone understanding and being patient as again our core team of + +Tyler Wright: Three and a half Engineers on the core engineering side has been working relentlessly on a number of different fronts. So I've been trying to limit Scott and Archer and the rest of teams sleep schedule,… + +Zeke E: And then just one other thing I will. + +Tyler Wright: but apparently they need to sleep to live. So we're working as quickly as we can. + +Zeke E: I will be perfect. I will be providing snapshots for the testnet once that gets started up. + +Tyler Wright: So I go ahead Zeke. + +Tyler Wright: Yeah, that's gonna be instrumental and I think that would be the snapshot that gets used for those that are helping to test things and participate in that testnet. So thank you Zeke's for all the work that you've been doing over the last couple of months to provide it again additional snapshot service. That stacked out by the core engineering team. Obviously, we have the poker Chief snapshot service and number of other avenues but having a snapshot service control by kind of overclock labs in the core engineering team that has some of more + +Tyler Wright: more often Cadence around snapshots is going to be very helpful, especially when core engineers and other members of the community are setting things up testing things Etc. So appreciate all the work you've been doing there Zeke. + +Tyler Wright: I'll follow up. I've already followed up with the website team on just the URL making sure that gets merged. But again, thank you for all the work there. + +Tyler Wright: Any other support related items? + +Scott Carruthers: but I was just gonna agree with Zeke the fact that we have snapshots available every hour. + +Tyler Wright: Go ahead Scott. + +Scott Carruthers: So I'm sure there's probably a number of people on the call that can understand the frustration or just challenges with you trying to build a New provider especially with the scripting that I created. I think a majority of the time waiting for the provider to come up was waiting for the dedicated notice zinc. So that process was actually longer than building in a cash provider. So having them. Available every hour and be able to sink Within. 30 seconds is obviously going to be huge going forward. and that's probably good update is I'm not sure that everyone on this call was aware of this new. Snapchat service that we have created Zeke doing all the work on the back end, but obviously that's going to be very important going forward. + + +### 00:35:00 + +Tyler Wright: Excellent any other discussion topics that anybody wants to talk about here related to support? + +Tyler Wright: if not again, please continue to follow the support repo for all things related to the core code base follow the console repo for all things going on relate to the cash console much appreciate all the Insiders vanguards members of the community here on the call and listening in later and just involved in continuing to provide support to existing users teams and projects and companies are trying to integrate with the cash again much appreciate all that efforts. Just a reminder the Sig providers monthly meeting is going to be starting in about 22 minutes or 21 minutes at this point. We'll get an update from Jigger and the ball and all the work that they've been doing related to console 2.0 and integrating crador into the Akash console experience. If anybody has any other topics related to provider again, please feel free to join that call and we can talk about those. + +Tyler Wright: Those in more detail and about 20 minutes. But again, thank you everybody for their time today. Make sure this recording and transcript is available shortly. But again another great call. Thank you all and we'll continue to update in between meetings in specific tickets or again. Look out for some announcements in Discord elsewhere. I believe actually Andrey correct me from wrong, but you did put an announcement Provider channels as recently as today with updates for folks on how to update to provide a Services version 0.6.4. So again, if anybody has any questions there what we'll talk about in more detailed and providers, but again, it also touches support in looking at those updated instructions, so + +Tyler Wright: Look out for the provider announcements and again much appreciate everyone's time and energy today. Hope to see many of you and sit providers the steering committee that originally tomorrow is now scheduled again for August 29. So again, no steering committee tomorrow. There will be a steering committee as normal on August 29th at the same time next Thursday, but hope to see you all around the community and thank you all for all that you do. Have a great rest of your day. + +Zeke E: Thanks everybody. + +Tyler Wright: Hope to see many of you and stick providers. + +Rodri R: See you in a bit. + +Scott Carruthers: Thanks. + +oo o: live long and prosper + + +### Meeting ended after 00:51:13 👋 From 2fc5b279984d10e05329c4c20b650c49a8bba795 Mon Sep 17 00:00:00 2001 From: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Date: Tue, 27 Aug 2024 08:29:08 +0000 Subject: [PATCH 5/9] Create meeting notes for sig providers #20 (#670) * Create meeting notes for sig providers #20 Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> * Update 020-2024-08-21.md added transcript Chore: add recording link Signed-off-by: Drinkwater * Update 020-2024-08-21.md added 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-providers/meetings/020-2024-08-21.md | 214 +++++++++++++++++++++++ 1 file changed, 214 insertions(+) create mode 100644 sig-providers/meetings/020-2024-08-21.md diff --git a/sig-providers/meetings/020-2024-08-21.md b/sig-providers/meetings/020-2024-08-21.md new file mode 100644 index 00000000..5f7bc40f --- /dev/null +++ b/sig-providers/meetings/020-2024-08-21.md @@ -0,0 +1,214 @@ +# Akash Network - Providers Special Interest Group (SIG) - Meeting #20 + +## Agenda +- Introduction and overview of meeting topics. +- Updates on the Praetor App and Console 2.0 development. +- Discussion on Provider Services v0.6.4. +- Implementation details of the new Snapshot Service. +- Review and update of provider-related documentation. + +## Meeting Details +- Date: Wednesday, August 21, 2024 +- Time: 08:00 AM PT (Pacific Time) +- [Recording](https://eyppjrj4mhnx5sbrndju5rgjpdcmejx3c76cn4d7isytmkhceq7q.arweave.net/Jh70xTxh237IMWjTTsTJeMTCJvsX_Cbwf0SxNijiJD8) +- [Transcript](#transcript) + +## Participants +- Andrey Arapov +- B S +- Deathless +- Deval Patel +- Jakob Hürlemann +- Jigar Patel +- oo o +- Rodri R +- Scott Carruthers +- Tyler Wright +- Zeke E + +## Meeting notes +- **Praetor App and Console 2.0 Integration:** + - Jigar Patel provided updates on the progress of integrating the provider process into Console 2.0. + - The current focus is on transitioning from k2 to k3s, improving the visual and functional flow for users managing Akash providers. + - The new scripts developed for Praetor are being tested internally, showing positive results. These scripts ensure compatibility for both multi-node and single-node setups on k3s. + - There is excitement about moving these changes into production. The new Console 2.0 dashboard will include features such as real-time lease monitoring, CPU and memory utilization statistics, and financial data related to leases. + - The upcoming version 0.6.4 of Praetor will support easy upgrades from version 6.2. The update is expected to roll out shortly, and feedback from the community will be sought to refine the experience further. + +- **Snapshot Service Integration and Helm Chart Updates:** + - Zeke E highlighted the need to update the Helm charts on GitHub to incorporate the new snapshot service, which provides hourly snapshots. This service is expected to enhance the speed of environment setups and testing for Akash providers. + - Scott Carruthers suggested a cautious approach to adopting the new snapshot service as the default in Helm charts. He recommended a testing period to ensure there are no connectivity or stability issues before making it the default. + - Andrey Arapov supported the idea of a testing phase and suggested updating the Helm charts after verifying the snapshot service's reliability. + +- **Migrating from K8s to K3s**: + - Zeke E asked about documentation and support for migrating from a K8s setup to K3s. + - Andrey Arapov explained that while technically possible, such migrations could be complex due to differences in container runtimes, configuration files, and networking setups. + - He suggested that in most cases, it might be easier to announce a maintenance window and rebuild the cluster rather than migrate. + +- **Documentation Updates:** + - Rodri R pointed out that some sections of the provider documentation, particularly those related to hardware requirements, are outdated and need revisions. + - Tyler Wright agreed and mentioned that this would be added as an action item. There will likely be a pull request (PR) made to update the documentation to reflect current needs accurately. + +- **Community Acknowledgement and Support:** + - Tyler Wright expressed appreciation for the continuous support provided by community members like Andrey, Scott, Tampa, and Deathless, who actively engage in the provider channels to assist new users and share their expertise. + - Deathless was specifically mentioned for his ongoing support in answering questions, sharing success stories, and helping new members navigate the provider landscape. + +- **Cosmos SDK 47 Testnet Participation:** + - Tyler Wright invited participants to join the testnet for the upcoming Cosmos SDK 47 upgrade. This testnet aims to thoroughly test the network, review documentation, and ensure all components function correctly. + - Participants with available bandwidth are encouraged to get involved. AKT rewards are available for those who contribute significantly to the testing efforts. + - Interested individuals should contact Tyler Wright or express their interest in the public channels. Announcements and updates related to the testnet will be shared soon. +**Next Steps:** +- Monitor the implementation and testing of the new snapshot service and any updates from the Praetor team. +- Ensure timely updates to the provider documentation. +- Engage with the community to gather feedback on new features and encourage participation in testnet activities. + +**Closing:** +- Tyler Wright thanked all attendees for their contributions and ongoing support. +- He encouraged continued collaboration in the provider channels and reminded everyone to stay tuned for updates on the snapshot service and upcoming testnet activities. +- The meeting concluded with expressions of gratitude from several participants. + +## **Action Items:** +- **Jigar Patel & Deval Patel**: + - Continue working on the integration of the Praetor app into Console 2.0. + - Prepare and communicate the release of Praetor version 0.6.4, encouraging community members to test and provide feedback. + +- **Zeke E**: + - Proceed with plans to update the GitHub repository for Helm charts with the new snapshot service, following a period of testing to ensure stability and functionality. + - Monitor the performance and reliability of the snapshot service, and report any issues encountered during testing. + +- **Scott Carruthers & Andrey Arapov**: + - Participate in the testing of the new snapshot service as part of the Cosmos SDK 47 testnet activities. + - Decide on the appropriate timing to update Helm charts based on test outcomes and community feedback. + +- **Tyler Wright**: + - Ensure that documentation updates are prioritized and completed, possibly through submitting a pull request. + - Facilitate community involvement by sharing resources and updates related to the new snapshot service and other developments. + - Coordinate feedback and participation for the Cosmos SDK 47 testnet and engage with interested community members. + +- **All Providers**: + - Review the new Console 2.0 dashboard features when they become available and provide feedback. + - Continue engaging in community discussions and provide support to new users and other providers. + +- **Cosmos SDK 47 Testnet Participants**: + - Reach out to Tyler Wright or express interest in public channels to participate in the testnet and contribute to testing and feedback activities. + +# **Transcript** + +Tyler Wright: All right, welcome everybody to providers monthly meeting. It's August 21st 2024. + +Tyler Wright: During the special interest group for providers monthly meetings the groups discuss anything related to being a cost provider in the past. We've gotten updates from jigarette DePaul and all the work that they've been doing on Trader app is one of the preferred ways to build a provider on the Akash Network making it significantly easier to do that as of the last four or five months jigar and the ball have joined the overclock Labs 14 and are now building pretor into console as a part of the console 2.0 effort. So again console in the future will be a place where folks can both deploy and build and manage providers. We'll get an update from jigarette ball and all the work that they've been doing and some of the next steps. + +Tyler Wright: We all discuss a little bit about Andre recently put an updates in the provider announcements Channel around Provider Services version 0.6.4 documentation again, as also getting updated as of now, but again, there's clear path for folks to upgrade their providers. If anybody has any questions again, feel free to ask them here, but I know that's some overclock Labs manage providers or in the process of being upgraded if not already upgraded. So again, we'll discuss that if there's any other topics that anybody wants to discuss feel free to drop them in chat. I know there are some teams that may not be able to make it this month, but there are some teams that are building provider related. + +Tyler Wright: Support Solutions and are talking about providing Demos in September. So again, I'm sure there will be a lot of messaging going on in various Discord channels leading up to some of those potential demos. It'd be great to have many of the folks here on this call who again run providers and are very just In tune with the provider experience on Akash to get some feedback to those teams and individuals. Again, if anybody has anything that they want to specifically provider will also discuss that. again + +Tyler Wright: One other thing that we'll discuss and we kind of discuss it during six support is in shoutout to Zeke who just joined us. There is a new snapshots service and it'll be available at snapshots at a cash dot Network. This is a service act out by the core team that again has a snapshot on an hourly basis that providers and others can use Zeke. I see your hand Go ahead and Zeke. + +Scott Carruthers: Andy may have some thoughts here as well. I had thought about that as well that Snapchat service could be our default in Helm charts. I don't know if we want to give some period time to and I can't imagine there's going to be but a snapshots are working they're working, but we could give it a little period of time to Ensure there are no issues like connection issues maybe necessarily even core snapshot related. So Andy, I don't know if you have any thoughts if we want to update the home charts immediately or possibly give it a short period and then update. + +Andrey Arapov: Let's give it some good. + +Tyler Wright: I'll put that in action either but I was thinking the same thing maybe we could just do a couple of tests as we're getting into this test net for the cosmos SDK 47 upgrade. And then once we feel a little bit more comfortable, even though I know that many people are using it currently like Scott Zeke's some others. Then we can update their home charts accordingly. + +Tyler Wright: But again, there will be some links shared for that snapshot service that is available to anybody in the community again, there's still a snapshot service and Pikachu and some other members of The Wider Community. But this spec for the specific snapshot service was again something that could be overclock managed just in case, there's ever any issues with poker shoe or anybody else from the community, being that they are managing their own businesses as well as the desire to have snapshots available and an hourly basis because that it greatly increases the speed of for those that are looking to set up providers or looking to do a number of tests. Go ahead Andrey. + + +### 00:05:00 + +Andrey Arapov: I just wanted to add something about the snapshot. So sometimes when we are creating the network we have High knowing that maybe would stop at the height and then all the notes expecting the new Akash version + +Andrey Arapov: and sometimes it's very rare, but it can happen. if they're great those bad that we need to recover from this snapshot up until that I lost last one. So it would be really nice if there's some short service will have this kind of ability to kind of detect the software upgrade proposals that were approved and based on that night in this particular photograph a great proposal that would make this kind of snapshots and so that they would last for longer than let's say an hour what or others like a week or so just in case some things going bad. So we have always listening thought before the third grade. + +Andrey Arapov: That's amazing. Thank you very much Zeke. + +Tyler Wright: terrific All right again, before we jump into any updates from Digger and Deval on all the work. They're doing related to the provider side of console 2.0. I do want to hand it over to Andrey again. He dropped an announcement for folks to upgrade their providers. I just want to see if there's any questions one from anybody here on the call or Andrey if there's anything that you wanted to specifically call out related to provide our upgrades. + +Tyler Wright: excellent Thank you as always Hunter. + +Tyler Wright: Thank you for that context Again, if anybody has any questions, feel free to drop them in the provider builds Channel again, I said this at six supports I'll just say it again especially related to folks that are looking to build providers. I've seen a great deal of support from just members of the community answering questions in a timely fashion so much appreciate obviously Andre Scott Tampa for all the work that they do, but I know that there's a number of people in the community that are offering advice on builds. and just supporting new users are trying to get involved in the provider side. So + + +### 00:10:00 + +Tyler Wright: shout out to those people and just saying involved in conversation. I know that he doesn't like to be talked about but I often see deathless in there too. Just like making sure that people are in tune, answering questions providing feedback talking about their success stories, things that they're working on so much appreciate that kind of constant conversation and collaboration with other members of the cash community. + +Tyler Wright: All right without further Ado I get me talk about snapshots. We talked about provider service upgrades. I do want to kick it over to jigarette and Deval who have been doing a great deal of work, obviously on Trader to this point and then are continuing to do more work on getting Prater into console 2.0. So Yeah, I'll just kick it over to jigarette and Deval to talk a little bit about what's been going on over the last month and kind of a look ahead and what they're looking what they're working on over the next month. + +Jigar Patel: Hey, thanks Yeah, so currently we are working on bringing the whole provider process into console to row and we are actually currently working on making sure that multi-node and the single node works on k3s and converting that process from k2k3s and Visually streamline the whole thing. Yeah, so + +Jigar Patel: Current the work is on making sure that power is being built or using this new scripts. There has worked on and whether it's very great. it's working great. We're internally on testing one some of the providers so far. So there is no issue on it. So we are actually moving them into production for our console provider process. And once that's like the whole continent already you're able to see the dashboard. It will see the lazy's that your product and currently holds on it able to pick up radio Provider from it. You're able to make new provider from the process. And yeah, we excited to be working. + +Jigar Patel: On Disney process. Once that's done. I will obviously post unto the ecosystem predator and also the provider channels so + +Jigar Patel: You can test it out the new process. Obviously. We look forward for any feedback that comes with it. In the meantime. We are also upgrading our Predator based the providers to the new the new 0.6.4, which is we're gonna Just Launch that in and a couple of hours. We're just doing fire testing. So you able to upgrade your printer Provider from six to two six to four pretty soon probably today and so once that's ready we'll also post that update into the ecosystem predator and our Channel as well. So yeah, look for that as well. Yeah and in general + +Jigar Patel: Being doing good been very welcome entertained. And we are excited to bring this new updates and upgrading the broader experience in terms of ux in terms of General process in terms of for simplifying a lot of stuff using k3s. So yeah really excited for it. + + +### 00:15:00 + +Jigar Patel: Yeah, so basically we are planning to Have dashboard and this Statistics. + +Jigar Patel: You don't have to install anything, right you will able to see all the leases in the past you're able to see your CPU memory utilization based on the leases. In the future. We are planning to add these feature where you will able to use your community file to just see your Cube statistics, right? But for now, you'll be able to see all the lazy related statistics all the financial related statistics. Also, you're able to see your CPU utilization every relation based on the release they get the provider. + +Zeke E: What about the ability to close leases from that dashboard so there's someone running and that I don't like or whatever. + +Zeke E: Great. Thank you. + +Zeke E: So with this new documentation and the student build process, will there be an option documentation to be able to migrate a current provider running K8? S and move over to k3s. if there's even any benefit to doing so + + +### 00:20:00 + +Scott Carruthers: Yeah, yeah, definitely. yeah, I don't yeah, I would have to give it some more thought. + +Andrey Arapov: Alec on the + +Tyler Wright: Go ahead rodri. I'll go ahead and go first and… + +Tyler Wright: then we'll have rodri follow up. + +Andrey Arapov: I don't just was wondering about this myself. + +Andrey Arapov: I think on the application. it's about like you can actually stop the cash provider service but the older manifest to move them to the new to build cluster, but actually that's gonna be quite complex and I'm not sure will be possible because once you have the container pots up and running and I know that 3s is using low level or container runtime. + +Andrey Arapov: it's all about how they can connect and I know that has specific config files which are different from Caterers. So there can be a bunch of mass in configs and also doing how they configure Telecom Network cni container networking interface plugin. I believe there will be so much pain to actually do this migrations mostly and it will be difficult the technique on different provider configurations because some providers may be using different settings. Let's say my cubes pray deployed before version 2.19 which was the distancing a year ago. It was set to I think Conflict for Calico now, it doesn't use it. long directly. So it's just one thing to just highlighted how complicated he could be. So + +Andrey Arapov: in my view it's easier to just destroy the cluster and rebuild it by announcing from maintenance window or just like you keep it running these cubes free as well. + +Tyler Wright: And we appreciate that Zeke. + +Andrey Arapov: Okay. + +Tyler Wright: Go ahead rodri. + +Tyler Wright: Great call out. I'll make sure it's as an action item. I'll probably with simple to make a PR when they have some time to update that as So thank you Roger for calling it up. + +Tyler Wright: I wanted to see if there's anything else related to a cost provider to anybody wanted to discuss right now. + +Tyler Wright: Again, I'm just tracking the provider Channel again. I know some teams are talking about presenting some solutions over the next month or so, but again just continues to be constant conversation that providers channel so much appreciate that and the providers build channel so much appreciate that. yeah, is there anything else anybody wants to discuss have to let you all go a little bit early and I know there's some next steps that will take in terms of Provider documentation. I know that again prayers going to be making some updates in terms of Provider service upgrades sometime very soon, but I want to see if there's anything else related to the hash provider anybody want to discuss at the time. + +Tyler Wright: If not, then again, I will follow up with some folks if anybody wants to get involved in testing for the cosmos SDK 47 upgrade. That'll be happening sometime very soon. Please reach out to me or just drop a note in a public Channel and I'll follow up with you again. Testing will include everything I think the idea is to + + +### 00:25:00 + +Tyler Wright: Have folks that want to participate in a testnet look at all of the documentation. Make sure that every part of the network works and then again from there. We'll do some more advanced testing with some strategic partners and some other folks and other clients in the community, but really looking to have folks that again have some bandwidth. There are akt Awards available, but have some bandwidth to test deployments test out things in the console and that would be highly appreciated over the next couple of weeks. But I'll drop some notes and announcements when we get to that time, but if anybody wants singing get involved again, feel free to reach out. + +Tyler Wright: If there's nothing else provide a related then again much appreciate the conversation. There's a number of action items. We'll take from this meeting. We're looking forward to seeing again updates from jigarette and Deval next month because I know that they work again diligently again jigars a new dad and he's still out there grinding. I hope he's getting some time for himself but much appreciate the work for the Prater team much appreciate all that Andre Scott's and everybody else on this call does in helping out the ecosystem as a whole so Thank you. All again. If anybody needs access to the provider build scripts the case way again, feel free to reach out to me or Scott there dropped in the chat here and you can share those as a beta path. But again much appreciated everybody. Look out for updates on a snapshot service coming very very shortly. + +Tyler Wright: Thank you all again for all that you do. We'll talk online for sure. See you soon. + +Scott Carruthers: Thanks, everyone. + +Jigar Patel: Thanks. + +Zeke E: Thanks everybody. + +Rodri R: See you soon. + +oo o: live long and prosper + + +### Meeting ended after 00:27:19 👋 + + From 32f8c36a74243f153e6c2285b3c500be94a4b2de Mon Sep 17 00:00:00 2001 From: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Date: Tue, 27 Aug 2024 08:31:10 +0000 Subject: [PATCH 6/9] Create meeting notes for Sig-Design #20 (#667) * Create meeting notes for Sig-Design #20 Signed-off-by: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> * Update 020-2024-08-20.md added transcript Chore: add recording link Signed-off-by: Drinkwater * Update 020-2024-08-20.md added 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/020-2024-08-20.md | 279 ++++++++++++++++++++++++++ 1 file changed, 279 insertions(+) create mode 100644 sig-design/meetings/020-2024-08-20.md diff --git a/sig-design/meetings/020-2024-08-20.md b/sig-design/meetings/020-2024-08-20.md new file mode 100644 index 00000000..a3a954fd --- /dev/null +++ b/sig-design/meetings/020-2024-08-20.md @@ -0,0 +1,279 @@ +# Akash Network - Design Special Interest Group (SIG) - Meeting #20 + +## Agenda +- Review of ongoing design projects +- Discussion of Akash website updates and issues +- Product design advancements for Akash Console +- Merchandise and giveaways for events +- Working group for YouTube content creation +- Akash Shopify store and potential expansion to other platforms + +## Meeting details +- Date: Wednesday, August 20, 2024 +- Time: 08:00 AM PT (Pacific Time) +- [Recording](https://t3sgdqvogazfp5dgoxojhngj43wccndepjg5f7ajo35y5h4z32oq.arweave.net/nuRhwq4wMlf0ZnXck7TJ5uwhNGR6TdL8CXb7jp-Z3p0) +- [Transcript](#transcript) + +## Participants +- B S +- Denis Lelic +- James Kano +- Marian Gheata +- oo o (Oakley) +- Oyase +- Robert Del Rey +- Tyler Wright +- ⻲人小 河 + + +## **Meeting Notes** + +- **Review of Ongoing Design Projects:** + - Denis Lelic welcomed everyone and provided an overview of the meeting's purpose. + - The group discussed the ongoing design initiatives, focusing on the improvements and updates made in the past month. + +- **Akash Website Updates:** + - Denis Lelic mentioned the creation of several issues related to the Akash website on GitHub. + - Key areas of focus include the pricing page, where users will have a unified experience for GPU pricing and usage calculators. + - The group is working on a new menu experience to enhance user navigation. + +- **Product Design Advancements for Akash Console:** + - Denis Lelic shared updates on product design advancements for the Akash Console, an open-source deployment tool. + - Credit card payments are being integrated, along with new features from the Praetor app. + - Shared product and engineering [roadmaps](https://github.com/orgs/akash-network/projects/) for more detailed information on upcoming features. + - The goal is to create a comprehensive tool for users to provide compute and deploy on the platform. + +- **Upcoming Events:** + - Denis Lelic highlighted several upcoming events in September and October, with the Akash community involved in designing booths, giveaways, and merchandise. + - Tyler Wright suggested ideas for new event giveaways, such as trucker hats and specific gifts for token249, like moon cakes. + +- **Merchandise and Giveaways for Events:** + - The group discussed the types of Akash-branded merchandise available, including shirts, hats, and pins. + - Tyler Wright encouraged contributions to the Shopify store, noting that it serves as a marketing tool with profits directed to the community pool if any arise. + +- **Working Group for YouTube Content Creation:** + - Robert Del Rey provided updates on the YouTube working group, including the creation of short samples and responding to comments on the YouTube channel. + - The group is working on uploading steering committee call videos with proper branding and thumbnails, with assistance from other members like B S and Oakley. + - Robert encouraged members to join the working group if interested in video editing, creating thumbnails, or other content-related tasks. + - Denis Lelic [shared a link](https://akash.network/brand/resources/) to the Akash logo kit for those needing brand assets for video production. + - Denis addressed the distribution of an open-source font used in the videos, ensuring no license violations. A [download link](https://www.fontshare.com/) for the font was provided.\ + - A Canva project was created to collaborate on the graphics, which will be shared with Denis for feedback. + - The group plans to finalize the graphics and upload the Steering Committee Calls videos once completed. + +- **Akash Shopify Store and Potential Expansion:** + - Tyler Wright reiterated that the items sold on the Shopify store are at cost, with any potential profits going to the community pool. + - Oakley suggested expanding to platforms like Redbubble, which the group agreed to explore further. + - Denis Lelic and Tyler Wright emphasized managing efforts and ensuring that community contributions align with Akash's overall goals. + +- **Community Contributions and Opportunities:** + - Tyler Wright highlighted ongoing community contributions, particularly in creating content for the Akash website and YouTube channel. + - A new mission in Zealy will involve designing Akash-branded swag, with a reward of 15 AKT for selected designs. + - Members were encouraged to participate in various working groups and contribute ideas for future initiatives. + +- **Recaps of SIGs Content:** + - Tyler Wright introduced the idea of creating recaps for the Special Interest Groups (SIGs) on a weekly or monthly basis. B S has been assisting with this effort. + - The recaps will be hosted on the Akash website as blog posts, summarizing key activities in SIGs and working groups, with links to notes and a look ahead. + +- **Akash Zealy Missions:** + - Robert Del Rey announced a mission on Akash Zealy related to the SIG Design call. The secret word for the mission is "SWAG." + - Robert also discussed an upcoming mission for designing Akash swag, where community members can submit designs for the Akash shop. The mission will be part of Sprint 2, and selected designs will be rewarded with 15 AKT. + +## **Action Items** +- Oakley will explore and potentially test Redbubble for Akash merchandise, with findings to be reported in the next meeting. +- Attendees are encouraged to engage with Akash Zealy missions, including the secret word "SWAG" and upcoming swag design missions. +- Community members are invited to participate in the upcoming mission on Zealy to design Akash-branded swag, with a reward of 15 AKT for selected designs. +- Members interested in frontend development or design are encouraged to join the Akash website working group meeting on Thursday. +- B S to continue developing recaps for SIGs, with feedback from Tyler Wright, and publish them as blog posts on the Akash website. + +# **Transcript** + +Denis Lelic: Hey everybody and welcome to today's Sikh design meeting. As usual we meet on a monthly basis where we discuss everything design related and sometimes we even touch topics such as content creation and so on and so on. So I'm glad. Some new community members are joining so welcome if you're here for the first time. I'll just get us. Going and maybe we cover some of the stuff we've done in the past month So maybe we start with. + +Denis Lelic: So for those of you who are attending working group for a cash website. There was a lot of issues created. I'll just drop a link from our GitHub. Website report here in the chat section. So there was a lot of shoes created which is good. I think everyone is just trying to evolve the website improved the experience. So we're trying to work on several areas. + +Denis Lelic: just to highlight a few maybe pricing page where we're gonna offer one unified experience on one single page where users could switch between GPU pricing usage calculator and if a user decides they want to Contribute compute they can also calculate how much would they earn? + +Denis Lelic: Maybe the next one I think. That's gonna have a positive impact and it's gonna improve the user experience is probably the new menu experience. So you can just go through some of these issues and of course if you're interested in any way of contributing just drop a comment there and will connect offline + +Denis Lelic: Let's Yeah, the next topic would be maybe product design. So on the product side. We're making some advancements on. A cash console for those of you that are maybe new or not aware of it. It's like deployment tool. + +Denis Lelic: Which is also open source. So everyone. Can you just give me a second? I'll share Maybe. + +Denis Lelic: Product and Engineering roadmaps, you can see what's happening in more detail right here in this link that I dropped in the comment section. So yeah, we're working on a bunch of stuff on that front. Credit card payments are on the way. There's gonna be + +Denis Lelic: some new features added and the app is gonna grow. So we're looking to add some of the functionalities from the Prater app. and I believe this is gonna + +Denis Lelic: Be a great way for users to have one tool. So either provide compute and on the other side they can deploy. + +Denis Lelic: Yes, and Tyler just mentioned. So anyone interested in having a more detailed. Walkthrough you can join sick clients later today. + +Denis Lelic: Okay, moving forward. There's a lot of events happening in the next couple of months. So in September and October, there are covered a couple of them. Maybe I'll just share. + +Denis Lelic: So here's the Community page from our website and hear all the upcoming events. You can find the link in the chat section. Yeah, so on the event side we try to support all the community members in core team members that are attending these events. so we've been involved I can designing booths giveaways like stickers. and merge and so on and so on and + + +### 00:05:00 + +Denis Lelic: yeah. That's it from the event side. + +Denis Lelic: Yeah talking about Merchant and all the giveaways. Yeah, Tyler you want to say something about the events? + +Tyler Wright: Yeah, I just want to throw out some ideas, obviously in the past we've had shirts socks pins and some of those things that have been given away at events insiders have worn and they seem to have gotten a lot of positive response at the most recent event in Buenos Aires for Cosmo verse that just happened. It seemed like there's some trucker hats the cash made obviously all this stuff is in the vein of just continuing to spread awareness around Akash what it is how people can use it one of the things that some people from overclock as well. As some people in the community have talked about is potentially specific gifts for token 249 because I think that's a special period so they were talking about many moon cakes for some events happening there. I know that there's a booth happening Atoka 24:9 a hacker house. I think some VIP events as well. So there's + +Tyler Wright: Is around very specific products that again can be a cost-branded and given a way to folks as Denis mentioned. If anybody has an ideas about products that they think should be added to the Shopify store. That's an effort that's ongoing and we talk about here, obviously the shop data cost.network stories quite basic, obviously much of the group is focused on building a blockchain and a core product and permissionless decentralized Marketplace for compute. But again, as a part of Sig design, there are opportunities to help out with the website, whether it be pitching ideas of our student at the shop pitching ideas of products that you want to be added that you think should be a class branded or the layout of the shop, all ideas are welcome and + +Tyler Wright: recommended and again, it's Denis mentioned for those that want to participate in creating content whether it be videos Graphics Shopify helping out with some of the working groups like The working group for the class YouTube. They're working group for the college website. There are again opportunities to contribute and earn akt, so we're always looking for folks that want to contribute. + +Denis Lelic: Thanks Yeah, I just shared the link from Swag shop data network. Feel free to check it out, but hopefully in the next week's. We're going to try to make this a little better experience and with some new Place there as well. Yes. I am. Not sure if you talked about the newly formed working group for YouTube. So it was set up I think two or three weeks ago, Robert's has been pretty much involved there. Fortunately. I couldn't make it to some of these meetings. I had a conflict. + +Denis Lelic: Robert if you're able to talk feel free, so otherwise I'll just give + +Denis Lelic: a call to action for everyone who's interested in any kind of possible videos out there like shorts and long form or editing or creating thumbnails, please join that working group. What's up? Yes, Robert. Go ahead. + +Robert Del Rey: Thank you is. So in today's call we basically recup. What we did last week. + +Robert Del Rey: We have spoke about the short samples. we showcase one the participants in the call. let me look for the notes happy We also talk about responding comments in the YouTube channel. + +Robert Del Rey: and yeah, basically, the one thing that was not completed was overloading the steering Comedy Calls videos into the YouTube channel. We wanted to add an opening a screen and a closing screen along with Brandon thumbnail before uploading those videos. + + +### 00:10:00 + +Robert Del Rey: The main reason why it's because you cannot edit a video Once you upload it. So the video has to be ready before upload the video. And I really wanted to follow up on that b s I believe he's in the call and also Oakley they both offer to help out with this Graphics. So then I know sometimes you have lots of stuff going on your side and I want to let you know that we have people here ready to support you with a graphics. What I would thinking is that they could get some draft going and show them with you for your feedback. I created a kamba project. I share that with BS and we are. + +Robert Del Rey: Together in that project so we can share the link with you as well and you can see the changes there or maybe we can share that in the cash YouTube channel or in The Design Channel, whatever Channel you prefer. Yeah, so once we have those Graphics already we can set uploading the informally calls star shipping out how the videos will look. + +Robert Del Rey: Around it doesn't all make sense. + +Denis Lelic: Thanks, That sounds good. And I'm happy that group is growing and there's interest in contributing for anyone who might need a cash brand assets. I'm just gonna share here link where you can download logo kit so you can find everything there. + +Denis Lelic: So feel free to play around with it, and I'm also available on Discord if you need anything. + +Denis Lelic: Just like a feedback or if you need any additional assets. Feel free to DM me or just drop it in the channel sick design. + +Denis Lelic: Yes, I don't know. Who's first Robert or Tyler. Go ahead. + +Tyler Wright: No, Robert was first Robert goes. + +Denis Lelic: Yeah, the reason it's why it's not added is I would just like to Distributing that font it's open source. I'll share it here. So if I believe in that kid, there's also a manual Which font is used and you can just download it here fawnshare.com. Yeah, and as I said, I just wanted to avoid any conflict with foreign chair team, even though it's open source. I just thought it would be more safer not to include it there. So we wouldn't violate any of their licenses. + +Denis Lelic: Or you can download it here. I provided Link in the chat section. Tyler + +Tyler Wright: Yeah, the one thing I want to add. I'm not really sure if we talked about it at I think design quite yet, but + +Tyler Wright: be maybe we have but b s at another down team has been helping out and I owe him some feedback, but he's been helping out to create basically Recaps of the cigs on a monthly slash weekly basis. We're figuring out the Cadence. Now those ideally should be needed via the website. So again, as blogs that can kind of recap for folks what's been going on the six in the working group front a paragraph on each with some of the highlights with links to the notes and maybe even sometimes a look ahead. So I want to shout out the work that he's continuing to do. I think it'll be very impactful for folks. I know everyone here is busy but folks have showed a desire to help contribute and obviously the only way that a class will grow to where we all wanted to go is he is by getting contrib + + +### 00:15:00 + +Tyler Wright: from a number of different kinds of people. So just look out for blogs. Hopefully coming soon. I think he'll ask some more questions either to piyush or come to the working group session and look out for those soon. If anybody else wants to contribute again, whether it be video or other kinds of content, please feel free to reach out. There's plenty of opportunities. + +Denis Lelic: Thank you time. So yeah, we covered a lot of stuff that's been done. I think all of these initiatives are just continue to work on in the next month or so. + +Denis Lelic: But I would like to. Just open the floor if anyone has any questions anything, maybe you want to start working on maybe you want to create a new initiative. + +Denis Lelic: Feel free to talk now or you can always as I said DME or just drop your ideas in this Design Channel. + +Denis Lelic: Okay, cool. I just see a lot of claps. I guess you support all the initiatives that are happening currently there is many but + +Denis Lelic: Hi. Did you want it to say anything else? Did you had anything else to discuss? + +Denis Lelic: Thank you Agree on everything. So anyone who's Feel free to join the meetings. I can also share. I'm not sure if I shared it, but I will now the community calendar where you can subscribe and + +Denis Lelic: you won't miss any of the future meetings. Just give me one second to + +Robert Del Rey: Ahead and share the secret word for the sick design called mission in a cash ceiling. Their cash series support all we have missions to engage with the cash community and new members and one of those missions is attending to this type of calls. so the secret word for this particular call it's going to be swag As w a g assassin said obvious and whiskey as in Alpha and G as in golf swag, that's the secret word for this or you can put it in now or when you listen to the recording of this call. + + +### 00:20:00 + +Robert Del Rey: In another topic. it's related to see you guys attending this call. You will get the alpha. We actually are working on a mission. I will take over the screen if you don't mind this. We're working on a mission. About designing a cash swag for the Akash shop. This Niche is going to be available in the Sprint number two and using my screen. Yeah, I believe you can. + +Robert Del Rey: Yeah, So this Mission we plan to launch it on a Sprint number two, it's their cash slog designer as you can see we want people to create Unique Designs that can be used by their cash community and either to use one of your designs Denis as an example here. I hope you don't mind and there are also resources where people can go for example, they can get the same thing that you share for the brand assets. It's right here. and the price for each selected winners gonna be 15 akd this can be discussed. But at the moment this is how it's looking right now and to release this on a screen number two and hopefully get The best designs that we can from the cash community and reward them for it. So I'm just gonna drop that offer here in the Channel with you. And yeah. + +Robert Del Rey: that's only guys that's + +Denis Lelic: Go ahead. + +Tyler Wright: So one quick caller on the record anybody who wants to participate with the shop, right now the items are sold at cost. So nobody's making any profit the idea is that if there were ever profits from any of the products sold to the Shopify store. They would just go to the community pool. So just putting that out there on the record. I think that's mention that number of times but always want to clarify why the shop store exists again as a awareness and marketing tool and then where the funds go from the Shopify store. So just putting that on the record again. + +Denis Lelic: Thank you someone raised their hand, but I can see and… + +oo o: Yeah, that was me. + +Denis Lelic: I go ahead please. + +oo o: yeah about the shop that Tyler just spoke about I know if you have seen swag on Redbubble and similar size before us and is there anything that's stopping a cat from also displaying the Swag there in places like that. + +Denis Lelic: Then you drop the link. Of the shop use just mentioned here in the chat section, please. + +oo o: Redbubble One of those pop art sites here. + +Denis Lelic: Okay, I got it here. Is that like? + +oo o: yeah, essentially one of those sites where essentially you can find all sort of stuff, from your favorite TV show to just something with you whimsical? but I've actually seen a few startups t-shirts on it before + +Denis Lelic: Yeah, it's something I guess we could. consider but as Tyler mentioned where not looking to create + +Denis Lelic: to make profit out of the shop. It's more like support the community or anyone who's Interested in Akash and likes the design maybe in purchase it. But yeah, maybe we can consider this. + +Denis Lelic: And we can drop a couple of designs here in the future. just to see + + +### 00:25:00 + +Denis Lelic: How it is going to go? What do you think time? + +Tyler Wright: Yeah, I would agree. I'm always down to try new things. The only thing that we're trying not to do is again, but because there's so many efforts around Sig design. We're just trying to manage our efforts. So if anybody here is I really think that this should be on Redbubble or any other platform then we can discuss it at one of these calls or maybe async and then go from there. I've seen Redbubble before I thought it was a site where it's kind of like Etsy where anybody can just throw up a design that's non-incorporated. if a member of the community didn't want to attend to Sig design, they could just make their own Akash merch and then throw it up on Redbubble. That's how I thought it was used. But again, I'm happy to continue to explore + +oo o: I think a lot of it is like that… + +Tyler Wright: Okay, Excellent. + +oo o: but I've actually seen official Marvel and DC mark on it. + +Tyler Wright: That's good to the only other thing I think about is the customer. + +oo o: Yeah. Yeah. + +oo o: Robert never,… + +oo o: I've never put anything. + +Tyler Wright: Go ahead. Sorry. + +oo o: Okay, Yeah, Robert put up a question. He was asking if it cost anything how much it costs are your clothing? I've never actually put a design up on Redbubble. I'm mostly been a customer. never a seller. creator You may go gone. + +Denis Lelic: Yeah. As Tyler mentioned maybe if you're interested, you can just give it a try see what happens and you can share. + +Denis Lelic: Everything you found on in our next meeting. + +oo o: over + +Denis Lelic: cool okay guys, so + +Denis Lelic: I think we've covered pretty much everything. I'm glad we had a couple of new discussions. Thanks, Robert and I can't see your name. There's just like two o's, so thank you. Double o + +Robert Del Rey: let's hopefully + +Denis Lelic: Oakley okay Oakley. Thank you. + +Denis Lelic: but I think maybe you have this information. I'm not sure if working group for their cash website is happening this week on Thursday. So everyone is welcome to join. There's a lot of stuff happening there. So if you're interested in either front end development or you want to contribute as a designer, please for you free to join our next meeting sync design is gonna happen next week next month. + +Denis Lelic: I hope we'll see each other. Next month as well. So thanks again for joining today and Have a great day. + +Robert Del Rey: Thank you Denis. + +Tyler Wright: Thank you all. + +Denis Lelic: Thank you. + +oo o: live long up + +Robert Del Rey: I say everybody. + +Denis Lelic: Bye-bye. Thank you. Bye. + + +### Meeting ended after 00:28:36 👋 + From f3fe81608d4cc3b0cd14e16b31666f1c5220d53f Mon Sep 17 00:00:00 2001 From: Drinkwater Date: Thu, 29 Aug 2024 12:52:36 -0400 Subject: [PATCH 7/9] steering committee Update README.md add meeting details for July 2024 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 dded03a4..edf7401f 100644 --- a/committee-steering/README.md +++ b/committee-steering/README.md @@ -31,7 +31,7 @@ The Steering Committee is a special SIG that periodically evaluates the list of | 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 27, 2024 11:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/017-2024-06-27.md) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/017-2024-06-27.md#transcript) |[Link](https://upv27tytyope2fseqvgnnre2au6nmmo65bs2c2fvuxtohsr5bpjq.arweave.net/o-uvzxPDnk0WRIVM1sSaBTzWMd7oZaFotaXm48o9C9M) -| Thursday, July 25, 2024 11:00 AM PT (Pacific Time) | | | +| Thursday, July 25, 2024 11:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/018-2024-07-25.md) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/018-2024-07-25.md#transcript) |[Link](https://vowukrgkuwsl7fdoune7kqruamcwsbhm7bh4aic6dse6vyussagq.arweave.net/q61FRMqlpL-UbqNJ9UI0AwVpBOz4T8AgXhyJ6uKSkA0) | Thursday, August 29, 2024 11:00 AM PT (Pacific Time) | | | | Thursday, September 26, 2024 11:00 AM PT (Pacific Time) | | | | Thursday, October 31, 2024 11:00 AM PT (Pacific Time) | | | From cee7872b03186c835e3afbbe46c8f8334b5b4414 Mon Sep 17 00:00:00 2001 From: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Date: Fri, 6 Sep 2024 09:06:02 +0000 Subject: [PATCH 8/9] update readme table and wg akash youtube notes (#676) --- sig-analytics/README.md | 6 +- .../{013-2024-08-15.md => 014-2024-08-15.md} | 0 sig-chain/README.md | 2 +- sig-clients/README.md | 2 +- sig-community/README.md | 2 +- sig-design/README.md | 2 +- sig-providers/README.md | 4 +- sig-support/README.md | 2 + wg-Akash-youtube/meetings/001-2024-07-23 | 86 +++++++++++++++++++ wg-Akash-youtube/meetings/002-2024-07-30 | 70 +++++++++++++++ wg-Akash-youtube/meetings/003-2024-08-06 | 74 ++++++++++++++++ 11 files changed, 241 insertions(+), 9 deletions(-) rename sig-analytics/meetings/{013-2024-08-15.md => 014-2024-08-15.md} (100%) create mode 100644 wg-Akash-youtube/meetings/001-2024-07-23 create mode 100644 wg-Akash-youtube/meetings/002-2024-07-30 create mode 100644 wg-Akash-youtube/meetings/003-2024-08-06 diff --git a/sig-analytics/README.md b/sig-analytics/README.md index 65cb43d1..6856adbb 100644 --- a/sig-analytics/README.md +++ b/sig-analytics/README.md @@ -31,9 +31,9 @@ Analytics Special Interest Group is dedicated to defining and building tools tha | #9 | Thursday, October 12, 2023 09:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-analytics/meetings/009-2023-10-12.md) | [Link](https://github.com/akash-network/community/blob/main/sig-analytics/meetings/009-2023-10-12.md#transcript) | [Link](https://v5ixigio4enkf7qhvlmzfptnlx6zkdite2skrznyil2d3xih6ana.arweave.net/r1F0GQ7hGqL-B6rZkr5tXf2VDRMmpKjluEL0Pd0H8Bo) | #10| Thursday, December 14, 2023 09:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-analytics/meetings/010-2023-12-14.md) |[Link](https://github.com/akash-network/community/blob/main/sig-analytics/meetings/010-2023-12-14.md#transcript) | [Link](https://ek6ahcmxfv2mnwpitrfidefkzfm6razh4zlv7cuowuue5tnrqy4q.arweave.net/IrwDiZctdMbZ6JxKgZCqyVnogyfmV1-KjrUoTs2xhjk) | #11| Thursday, February 15, 2024 09:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-analytics/meetings/011-2024-02-15.md) |[Link](https://github.com/akash-network/community/blob/main/sig-analytics/meetings/011-2024-02-15.md#transcript) | Coming Soon -| #12| April 18, 2024 09:00 AM PT (Pacific Time) | | | -| #13| June, 2024 09:00 AM PT (Pacific Time) | | | -| #14| August, 2024 09:00 AM PT (Pacific Time) | | | +| #12| April 18, 2024 09:00 AM PT (Pacific Time) | coming Soon | Coming Soon | Coming Soon +| #13| June 20, 2024 09:00 AM PT (Pacific Time) |Coming Soon |Coming Soon | Coming Soon +| #14| August, 2024 09:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-analytics/meetings/014-2024-08-15.md) |[Link](https://github.com/akash-network/community/blob/main/sig-analytics/meetings/014-2024-08-15.md#transcript) |[Link](https://j3ac6jsjcqd3hmfii6dophi4gunxiuqqxdeslkehhz6fpnvvgkta.arweave.net/TsAvJkkUB7OwqEeG550cNRt0UhC4ySWohz58V7a1MqY) | #15| October 2024 09:00 AM PT (Pacific Time) | | | | #16| December, 2024 09:00 AM PT (Pacific Time) | | | diff --git a/sig-analytics/meetings/013-2024-08-15.md b/sig-analytics/meetings/014-2024-08-15.md similarity index 100% rename from sig-analytics/meetings/013-2024-08-15.md rename to sig-analytics/meetings/014-2024-08-15.md diff --git a/sig-chain/README.md b/sig-chain/README.md index e9dbd75c..4f8da0ec 100644 --- a/sig-chain/README.md +++ b/sig-chain/README.md @@ -31,7 +31,7 @@ date: 2023-1-09T00:19:20-08:00 | #16| May 21, 2024 09:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-chain/meetings/016-2024-05-21.md) |[Link](https://github.com/akash-network/community/blob/main/sig-chain/meetings/016-2024-05-21.md#transcript) |[Link](https://t7vun4ttnoelbnwkis4rf7eacagljw7a5tsobsuujmsiycgjdpna.arweave.net/n-tG8nNriLC2ykS5EvyAEAy02-Ds5ODKlEskjAjJG9o) | #17| June 11, 2024 09:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-chain/meetings/017-2024-06-11.md)| [Link](https://github.com/akash-network/community/blob/main/sig-chain/meetings/017-2024-06-11.md#transcript)|[Link](https://g6qelhldnaj52ry4xc56kge2wjrswqfgxrqs4iduth4cpqpndlfq.arweave.net/N6BFnWNoE91HHLi75RiasmMrQKa8YS4gdJn4J8HtGss) | #18| July 17, 2024 09:00 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-chain/meetings/018-2024-07-17.md) | [Link](https://github.com/akash-network/community/blob/main/sig-chain/meetings/018-2024-07-17.md#transcript) |[Link](https://556xxz5f7wcokgit5qlznxtkdvmdkcrafobpcwztrytgflmcifjq.arweave.net/731756X9hOUZE-wXlt5qHVg1CiArgvFbM44mYq2CQVM) -| #19| August, 2024 09:00 AM PT (Pacific Time) | | | +| #19| August 13, 2024 09:00 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-chain/meetings/019-2024-08-13.md) |[Link](https://github.com/akash-network/community/blob/main/sig-chain/meetings/019-2024-08-13.md#transcript) |[Link](https://bcp7f4xex34ci3vtw7rfaeonelh52dkaqdb26xjfs67jojmips7a.arweave.net/CJ_y8uS--CRus7fiUBHNIs_dDUCAw69dJZe-lyWIfL4) | #20| September, 2024 09:00 AM PT (Pacific Time) | | | | #21| October 2024 09:00 AM PT (Pacific Time) | | | | #22| November, 2024 09:00 AM PT (Pacific Time) | | | diff --git a/sig-clients/README.md b/sig-clients/README.md index cdec57ef..fd661f9a 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 | #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) |[Link](https://github.com/akash-network/community/blob/main/sig-clients/meetings/015-2024-04-24.md) |[Link](https://github.com/akash-network/community/blob/main/sig-clients/meetings/015-2024-04-24.md#transcript) |[Link](https://j3gehsinfdsmtozvozl7ne3dv2w255mnewbmwe3unblpiayao3ya.arweave.net/TsxDyQ0o5Mm7NXZX9pNjrq2u9Y0lgssTdGhW9AMAdvA) | #16| June 25th, 2024 10:00 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-clients/meetings/016-2024-06-25.md) |[Link](https://github.com/akash-network/community/blob/main/sig-clients/meetings/016-2024-06-25.md#transcript) |[Link](https://g4sync4igp5y56x5cxfhh45vo4elgdzmcptwja4z33gcjhzkkoqq.arweave.net/NyWGi4gz-476_RXKc_O1dwizDywT52SDmd7MJJ8qU6E) -| #17| August, 2024 10:30 AM PT (Pacific Time) | | | +| #17| August 20th, 2024 10:30 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-clients/meetings/017-2024-08-20.md) |[Link](https://github.com/akash-network/community/blob/main/sig-clients/meetings/017-2024-08-20.md#transcript) |[Link](https://4mgemilgnadqtihidt2lpu7ocnkirkq4voj2pabf64hw5zdlqh3a.arweave.net/4wxGIWZoBwmg6Bz0t9PuE1SIqhyrk6eAJfcPbuRrgfY) | #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) | | | diff --git a/sig-community/README.md b/sig-community/README.md index 3c92ff05..ffbde371 100644 --- a/sig-community/README.md +++ b/sig-community/README.md @@ -33,7 +33,7 @@ This SIG (Special Interest Group) is designed for Akash community members to pro | #15| May, 2024 11:00 AM PT (Pacific Time) |Coming Soon |Coming Soon |Coming Soon | #16| June 11, 2024 11:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-community/meetings/016-2024-06-11.md)|[Link](https://github.com/akash-network/community/blob/main/sig-community/meetings/016-2024-06-11.md#Transcript)|[Link](https://nl4ez6metcnz3sdkdgvxj6b2opl74ywekhhfqfj3smj6m4in3e2a.arweave.net/avhM-YSYm53IahmrdPg6c9f-YsRRzlgVO5MT5nEN2TQ) | #17| July 09, 2024 11:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-community/meetings/017-2024-07-09.md) |[Link](https://github.com/akash-network/community/blob/main/sig-community/meetings/017-2024-07-09.md#Transcript) |[Link](https://x6pq6krlnowidy2qpsxdgyrnx7gz5i4ypuxxeemqsynsvipvhoaa.arweave.net/v58PKitrrIHjUHyuM2Itv82eo5h9L3IRkJYbKqH1O4A) -| #18| August, 2024 11:00 AM PT (Pacific Time) | | | +| #18| August 14, 2024 11:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-community/meetings/018-2024-08-14.md) | [Link](https://github.com/akash-network/community/blob/main/sig-community/meetings/018-2024-08-14.md#Transcript) | Coming Soon | #19| September, 2024 11:00 AM PT (Pacific Time) | | | | #20| October 2024 11:00 AM PT (Pacific Time) | | | | #21| November, 2024 11:00 AM PT (Pacific Time) | | | diff --git a/sig-design/README.md b/sig-design/README.md index 67c53019..13718d6c 100644 --- a/sig-design/README.md +++ b/sig-design/README.md @@ -34,7 +34,7 @@ date: 2023-1-09T00:19:20-08:00 | #17| May 08, 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| June 12, 2024 08:00 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-design/meetings/017-2024-06-12.md) |[Link](https://github.com/akash-network/community/blob/main/sig-design/meetings/017-2024-06-12.md#transcript) |[Link](https://ifqou2kkf6gqtmise2kelunxe2wc4xrcssgptlx3oh25flm7tcea.arweave.net/QWDqaUovjQmxEiaURdG3JqwuXiKUjPmu-3H10q2fmIg) | #19| July 17, 2024 08:00 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-design/meetings/019-2024-07-17.md) | [Link](https://github.com/akash-network/community/blob/main/sig-design/meetings/019-2024-07-17.md#transcript)|[Link](https://ifqou2kkf6gqtmise2kelunxe2wc4xrcssgptlx3oh25flm7tcea.arweave.net/QWDqaUovjQmxEiaURdG3JqwuXiKUjPmu-3H10q2fmIg) -| #20| August, 2024 08:00 AM PT (Pacific Time) | | | +| #20| August 20, 2024 08:00 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-design/meetings/020-2024-08-20.md) | [Link](https://github.com/akash-network/community/blob/main/sig-design/meetings/020-2024-08-20.md#transcript) |[Link](https://t3sgdqvogazfp5dgoxojhngj43wccndepjg5f7ajo35y5h4z32oq.arweave.net/nuRhwq4wMlf0ZnXck7TJ5uwhNGR6TdL8CXb7jp-Z3p0) | #21| September, 2024 08:00 AM PT (Pacific Time) | | | | #22| October 2024 08:00 AM PT (Pacific Time) | | | | #22| November, 2024 08:00 AM PT (Pacific Time) | | | diff --git a/sig-providers/README.md b/sig-providers/README.md index aa757fd6..9eb5be2f 100644 --- a/sig-providers/README.md +++ b/sig-providers/README.md @@ -33,8 +33,8 @@ Provider SIG covers everything pertinent to Providers on Akash Network. This inc | #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 22, 2024 08:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-providers/meetings/017-2024-05-22.md)|[Link](https://github.com/akash-network/community/blob/main/sig-providers/meetings/017-2024-05-22.md#transcript) |[Link](https://a6qm5qjrbhmjkmbmsfldmoqzdspsaxypsgfq26wfw6ysnw3xp7cq.arweave.net/B6DOwTEJ2JUwLJFWNjoZHJ8gXw-Riw16xbexJtt3f8U) | #18| June 26, 2024 08:00 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-providers/meetings/018-2024-06-26.md) |[Link](https://github.com/akash-network/community/blob/main/sig-providers/meetings/018-2024-06-26.md#transcript) |Coming Soon -| #19| July, 2024 08:00 AM PT (Pacific Time) | | | -| #20| August, 2024 08:00 AM PT (Pacific Time) | | | +| #19| July 24, 2024 08:00 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-providers/meetings/019-2024-07-24.md) | [Link](https://github.com/akash-network/community/blob/main/sig-providers/meetings/019-2024-07-24.md#transcript) |[Link](https://aa2i7ytftmtlehngryvt4m6jnaxvu5ku72e34u5akdetalzdimja.arweave.net/ADSP4mWbJrIdpo4rPjPJaC9adVT-ib5ToFDJMC8jQxI) +| #20| August 21, 2024 08:00 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-providers/meetings/020-2024-08-21.md) | [Link](https://github.com/akash-network/community/blob/main/sig-providers/meetings/020-2024-08-21.md#transcript) |[Link](https://eyppjrj4mhnx5sbrndju5rgjpdcmejx3c76cn4d7isytmkhceq7q.arweave.net/Jh70xTxh237IMWjTTsTJeMTCJvsX_Cbwf0SxNijiJD8) | #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) | | | diff --git a/sig-support/README.md b/sig-support/README.md index 547b4e75..d1b4161f 100644 --- a/sig-support/README.md +++ b/sig-support/README.md @@ -50,6 +50,8 @@ sig-support is responsible for defining mechanics of how support works at Akash | #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 26, 2024 08:00 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-support/meetings/034-2024-06-26.md) | [Link](https://github.com/akash-network/community/blob/main/sig-support/meetings/034-2024-06-26.md#transcript) |[Link](https://edy24xoc5isqb4ilutntgush3jmsnlcnfjaajdnsr2f5d34caktq.arweave.net/IPGuXcLqJQDxC6TbM1JH2lkmrE0qQASNso6L0e-CAqc) +| #35 | Wed, July 24, 2024 08:00 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-support/meetings/035-2024-07-24.md) | [Link](https://github.com/akash-network/community/blob/main/sig-support/meetings/035-2024-07-24.md#transcript) |[Link](https://aa2i7ytftmtlehngryvt4m6jnaxvu5ku72e34u5akdetalzdimja.arweave.net/ADSP4mWbJrIdpo4rPjPJaC9adVT-ib5ToFDJMC8jQxI) +| #36 | Wed, July 24, 2024 08:00 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-support/meetings/036-2024-08-21.md) | [Link](https://github.com/akash-network/community/blob/main/sig-support/meetings/036-2024-08-21.md#transcript) |[Link](https://wrx26ds6t7sofpahkzy5iphq7eqtfu3jln6xf5idxmrr2url4m5q.arweave.net/tG-vDl6f5OK8B1Zx1Dzw-SEy02lbfXL1A7sjHVIr4zs) ## Leadership diff --git a/wg-Akash-youtube/meetings/001-2024-07-23 b/wg-Akash-youtube/meetings/001-2024-07-23 new file mode 100644 index 00000000..a7223cf6 --- /dev/null +++ b/wg-Akash-youtube/meetings/001-2024-07-23 @@ -0,0 +1,86 @@ +# Akash Network - Akash Youtube Working Group (WG) - Meeting #1 + +## Agenda + +- Review the plan of action for overhauling the Akash Networks YouTube channel +- Discuss Phase 1 and Phase 2 of the YouTube channel improvement project +- Determine timeline for Phase 1 completion + +## Meeting Details + +## Meeting Details +- Date: Tuesday, July 23, 2024 +- Time: 08:00 AM PT (Pacific Time) +- Recording: Coming Soon +- [Transcript](#transcript) + +## Participants + +- Tyler Wright +- Robert Del Rey +- Rodri R + +## Meeting Notes + +### Background and Objectives + +- The YouTube Working Group emerged from the Special Interest Group (SIG) for Design +- Main goal: Overhaul Akash Network's YouTube channel to increase discovery and usability for new and existing users +- Robert Del Rey shared a [document](https://docs.google.com/document/d/1yA1V6HKoRhnXs29h_peTFRnlVUHARx7qfRM6eTHPz7w/edit?usp=sharing) with a plan of action in the Discord channel + +### Current State of Akash YouTube Channel + +- Inconsistent thumbnail designs across videos +- Limited categories displayed on the home page +- Outdated welcome video for non-subscribers +- Inconsistent video descriptions, some lacking detail +- Underutilization of relevant keywords like AI, DePIN, and blockchain + +### Phase 1 Plans + +- Improve overall look of thumbnails for visual consistency across the channel +- Optimize keywords in video descriptions and titles for better discoverability +- Update video descriptions to ensure consistency and include relevant keywords +- Revamp playlists into key topics: + - Deployments and tutorials + - Events (panels and other events) + - Akash Community videos + - Steering committee videos +- Create and upload a new welcome video for non-subscribers +- Update the channel banner to reflect current branding and information + +### Phase 2 Considerations (for future discussion) + +- Determine optimal frequency of video uploads +- Develop a strategy for creating and utilizing YouTube Shorts +- Explore options for remastering existing content +- Plan for creating new, original content + +### Timeline and Next Steps + +- Aim to complete Phase 1 in the next 20-30 days, with a target date of September 1st +- Transition into maintenance mode after the initial revamp +- Schedule a follow-up working group session for next week +- Continue asynchronous discussions in the Discord channel + +### Key Performance Indicators (KPIs) + +- Track and aim to increase overall channel viewership +- Monitor and work to increase channel subscriptions + +The meeting concluded with an agreement to continue discussions asynchronously and to involve other interested teams in future efforts for the YouTube channel improvement project. + +## Action Items + +- Robert Del Rey to obtain access to the Akash YouTube channel +- Robert to begin creating new categories and organizing existing videos +- Robert to work on keyword optimization and description updates for current videos +- Tyler Wright to provide Robert with access to steering committee and Akash Accelerate videos +- Team to collaborate on improving the YouTube channel banner +- Create a GitHub issue to track progress and assign tasks +- Discuss Phase 2 questions and strategies in the Discord channel +- Robert to share the planning document link in the GitHub issue + + + +## Transcript \ No newline at end of file diff --git a/wg-Akash-youtube/meetings/002-2024-07-30 b/wg-Akash-youtube/meetings/002-2024-07-30 new file mode 100644 index 00000000..634bee82 --- /dev/null +++ b/wg-Akash-youtube/meetings/002-2024-07-30 @@ -0,0 +1,70 @@ +# Akash Network - Akash Youtube Working Group (WG) - Meeting #2 + +## Agenda + +- Review access and documentation for Robert Del Rey +- Discuss YouTube channel improvements with Denis Lelic +- Review thumbnail designs by Robert Del Rey +- Discuss short-form content strategy +- Plan next steps and action items + +## Meeting Details +- Date: Tuesday, July 30, 2024 +- Time: 08:00 AM PT (Pacific Time) +- Recording: Coming Soon +- [Transcript](#transcript) + + +## Participants + +- Tyler Wright +- Denis Lelic +- Robert Del Rey +- Alex Pedersen + +## Meeting Notes + +- Tyler Wright provided an update on granting Robert Del Rey access to the Akash YouTube channel as a manager + +- Areas for improvement on the YouTube channel were discussed: + - Updating the main banner + - Revising the "Sovereign infrastructure that Scales" messaging + - Updating playlists and video content + - Improving thumbnails and descriptions with calls to action + +- Denis Lelic offered support for creating graphics and suggested reaching out to the community for additional design assistance + +- The group discussed adding branded intro/outro screens to community-created content when uploading to the Akash Network channel + +- Robert Del Rey presented three thumbnail design concepts: + - Design featuring large text and imagery + - Design including larger logos + - Design aligning with current YouTube trends, featuring a large host image and short title + +- Denis Lelic suggested collaborating on designs to ensure brand consistency across platforms + +- The group discussed creating short-form content (1-2 minute videos) from existing long-form content for distribution on YouTube and other platforms + +- Tyler Wright clarified the difference between the community contributions page on the website and the more formal Akash Network YouTube channel + +- The team agreed to move the next meeting to one hour earlier + +## Action Items + +- Robert Del Rey to compile a list of design assets needed for Denis Lelic's review + +- Robert Del Rey to send an announcement in the YouTube chat about future meetings + +- Robert Del Rey to create a short video on "How to deploy on Akash" for next week's review + +- Robert Del Rey to work on descriptions for videos, coordinating with Zack for specific content + +- Tyler Wright to provide access to steering committee videos for Robert Del Rey + +- Team to consider creating additional short-form content on topics like becoming a validator, Akash Accelerate highlights, and how to contribute to the project + +- Discuss updating the community contributions page on the website during the Website Working Group meeting + +- Robert Del Rey to check YouTube access and notify Tyler Wright of any issues + +## Transcript \ No newline at end of file diff --git a/wg-Akash-youtube/meetings/003-2024-08-06 b/wg-Akash-youtube/meetings/003-2024-08-06 new file mode 100644 index 00000000..174b17c5 --- /dev/null +++ b/wg-Akash-youtube/meetings/003-2024-08-06 @@ -0,0 +1,74 @@ +Here are the meeting notes in the requested format: + +# Akash Network - Akash Youtube Working Group (WG) - Meeting #3 + +## Agenda +- Review Akash YouTube plan document +- Discuss video descriptions and titles +- Update YouTube video playlists and add sections +- Community-generated content +- Shorts content +- Multi-language content + +## Meeting Details +- Date: Tuesday, August 06, 2024 +- Time: 08:00 AM PT (Pacific Time) +- Recording: Coming Soon +- [Transcript](#transcript) + +## Participants +- Tyler Wright +- Denis Lelic +- Robert Del Rey +- Fenil Modi +- Minh Tâm Nguyễn +- Rodri R +- B S + +## Meeting Notes + +### YouTube Channel and Content Plans +- Robert Del Rey provided an update on gaining access to the Akash YouTube channel and presented the Akash YouTube plan documents. He made changes to the channel, focusing on reorganization. +- Robert Del Rey highlighted updates to descriptions and the need for consistent branding across videos, including adding timestamps and thumbnails for easier navigation. + +### Enhancing Video Descriptions and Titles +- Robert Del Rey shared ideas for improving YouTube video descriptions to include more detailed content and ensure consistency. The descriptions are designed to lead viewers to relevant Akash content. +- Tyler Wright suggested adding deployment links in video descriptions for easier access to the Akash Console. + +### Playlists and Channel Organization +- New playlists were created: + - *Deployments and Tutorials* - contains tutorials like "Running the BLM on Akash." + - *Akash Events* - for event recordings like *Akash Accelerate* and *Decentral 2022*. + - *Community Contributions* - includes videos by community members like Shimpa. +- Tyler Wright recommended conducting an audit of older videos to decide which ones to keep or remove, possibly archiving outdated videos. +- Rodri R and Tyler Wright agreed that community-generated videos that meet the channel's quality and branding standards could be included in the main Akash YouTube channel. + +### Use of Disclaimers +- Tyler Wright and Robert Del Rey discussed the appropriateness of disclaimers. +- They agreed that educational content on Akash tools should not carry speculative disclaimers (e.g., NFA - Not Financial Advice), as they may deter new users. + +### Community Contributions and Feature Options +- Robert Del Rey proposed three options for featuring community content: + 1. Upload videos directly to the Akash YouTube channel. + 2. Feature community-created videos in a playlist. + 3. Add feature channels, highlighting contributors like Europlots. +- Rodri R and Tyler Wright supported maintaining a high standard for community content featured on the channel. + +### Short-form Content and Future Additions +- Robert Del Rey mentioned the creation of short-form content (YouTube Shorts) and promised to present sample shorts in the next meeting. +- The need for multilingual content was raised, with Rodri R supporting the idea of creating language-specific playlists rather than separate channels. + + +## Action Items + +- Robert to continue refining video descriptions and applying timestamps to existing videos +- Group to audit existing videos for potential archiving or removal +- Robert to create sample YouTube Shorts for review in the next meeting +- Tyler to reach out to community content creators (e.g., Shimpa) about featuring their content +- Tyler to initiate discussions on including community-generated content with proper credits and branding. +- Robert to research best practices for multi-language content organization on YouTube +- Group to consider creating an Akash channel on Omniflix TV +- Robert to update the Akash YouTube planning document with meeting outcomes +- All participants to contribute ideas for new video content in the Discord channel + +## Transcript \ No newline at end of file From 84f637fb1a71a0e4f8a7c87a1a0267743d5df3ec Mon Sep 17 00:00:00 2001 From: George Appiah <48031636+iamGeorgePro@users.noreply.github.com> Date: Tue, 10 Sep 2024 14:27:31 +0000 Subject: [PATCH 9/9] rename wg-akash-youtube meeting files to add ".md" (#677) rename wg-akash-youtube files --- wg-Akash-youtube/meetings/{001-2024-07-23 => 001-2024-07-23.md} | 0 wg-Akash-youtube/meetings/{002-2024-07-30 => 002-2024-07-30.md} | 0 wg-Akash-youtube/meetings/{003-2024-08-06 => 003-2024-08-06.md} | 0 3 files changed, 0 insertions(+), 0 deletions(-) rename wg-Akash-youtube/meetings/{001-2024-07-23 => 001-2024-07-23.md} (100%) rename wg-Akash-youtube/meetings/{002-2024-07-30 => 002-2024-07-30.md} (100%) rename wg-Akash-youtube/meetings/{003-2024-08-06 => 003-2024-08-06.md} (100%) diff --git a/wg-Akash-youtube/meetings/001-2024-07-23 b/wg-Akash-youtube/meetings/001-2024-07-23.md similarity index 100% rename from wg-Akash-youtube/meetings/001-2024-07-23 rename to wg-Akash-youtube/meetings/001-2024-07-23.md diff --git a/wg-Akash-youtube/meetings/002-2024-07-30 b/wg-Akash-youtube/meetings/002-2024-07-30.md similarity index 100% rename from wg-Akash-youtube/meetings/002-2024-07-30 rename to wg-Akash-youtube/meetings/002-2024-07-30.md diff --git a/wg-Akash-youtube/meetings/003-2024-08-06 b/wg-Akash-youtube/meetings/003-2024-08-06.md similarity index 100% rename from wg-Akash-youtube/meetings/003-2024-08-06 rename to wg-Akash-youtube/meetings/003-2024-08-06.md