diff --git a/committee-steering/README.md b/committee-steering/README.md index 99383a2b..46a52c56 100644 --- a/committee-steering/README.md +++ b/committee-steering/README.md @@ -23,9 +23,9 @@ The Steering Committee is a special SIG that periodically evaluates the list of | Thursday, July 27, 2023 11:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/007-2023-07-27.md) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/007-2023-07-27.md#transcript) | [Link](https://2uw2d6ylfq3v2btiav5izgx4kvsgcc2s72bb5vvymb5byck4jsca.arweave.net/1S2h-wssN10GaAV6jJr8VWRhC1L-gh7WuGB6HAlcTIQ) | Wednesday, August 30, 2023 11:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/008-2023-08-30.md) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/008-2023-08-30.md#transcript) |[Link](https://6bmxztaobmi5ox6n3nv5f6hgz7cwn7y7qxkp7ureegcbxswq4yxa.arweave.net/8Fl8zA4LEddfzdtr0vjmz8Vm_x-F1P_SJCGEG8rQ5i4) | Thursday, September 28, 2023 11:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/009-2023-09-28.md) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/009-2023-09-28.md#transcript) |[Link](https://bw2dirmu4darmwcx74o24hzfkjzs7f33grrc5rdihgysff4kxyta.arweave.net/DbQ0RZTgwRZYV_8drh8lUnMvl3s0Yi7EaDmxIpeKviY) -| Wednesday, November 1, 2023 11:00 AM PT (Pacific Time) | | | -| Thursday, November 30, 2023 11:00 AM PT (Pacific Time) | | | -| Thursday, December 28, 2023 11:00 AM PT (Pacific Time) | | | +| Wednesday, November 1, 2023 11:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/010-2023-11-01.md) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/010-2023-11-01.md#transcript) |[Link](https://4yrnmjlm3nco2ccfkbkv67s6cfgvgrge7op5dfwnv6gn46mueqxa.arweave.net/5iLWJWzbRO0IRVBVX35eEU1TRMT7n9GWza-M3nmUJC4) +| Thursday, December 07, 2023 11:00 AM PT (Pacific Time) | | | +| Thursday, January 11, 2023 11:00 AM PT (Pacific Time) | | | | Thursday, January 25, 2024 11:00 AM PT (Pacific Time) | | | | Thursday, February 29, 2024 11:00 AM PT (Pacific Time) | | | diff --git a/sig-chain/README.md b/sig-chain/README.md index b38d45a8..e4802a2a 100644 --- a/sig-chain/README.md +++ b/sig-chain/README.md @@ -22,7 +22,7 @@ date: 2023-1-09T00:19:20-08:00 | #7 | Tuesday, August 01, 2023 09:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-chain/meetings/007-2023-08-01.md) |[Link](https://github.com/akash-network/community/blob/main/sig-chain/meetings/007-2023-08-01.md#transcript) |[Link](https://ublt6v3ytezl3kaq6ygiaz2zk52wxhmp7khokzmiy2ufgjheanpa.arweave.net/oFc_V3iZMr2oEPYMgGdZV3VrnY_6juVliMaoUyTkA14) | #8 | Tuesday, September 05, 2023 09:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-chain/meetings/008-2023-09-05.md) |[Link](https://github.com/akash-network/community/blob/main/sig-chain/meetings/008-2023-09-05.md#transcript) |[Link](https://r67rmtmtcv66e7edkvshs42dzkzhk46xpknlhrtrvzwkvdm464ja.arweave.net/j78WTZMVfeJ8g1VkeXNDyrJ1c9d6mrPGca5sqo2c9xI) | #9 | Tuesday, October 10, 2023 09:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-chain/meetings/009-2023-10-10.md) |[Link](https://github.com/akash-network/community/blob/main/sig-chain/meetings/009-2023-10-10.md#transcript) |[Link](https://nyvxvysvdc5oz5zwbmxrvtkyh2n2rrsqkopr2gxgpd7gkptvvsyq.arweave.net/bit64lUYuuz3NgsvGs1YPpuoxlBTnx0a5nj-ZT51rLE) -| #10 | Tuesday, November 07, 2023 09:00 AM PT (Pacific Time) | | | +| #10 | Wednesday, November 08, 2023 09:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-chain/meetings/011-2023-11-08.md) |[Link](https://github.com/akash-network/community/blob/main/sig-chain/meetings/011-2023-11-08.md#transcript) |[Link](https://sshyyg4r3uoeixzudilhwdkncekgk3yw5m6mulso6foidluersuq.arweave.net/lI-MG5HdHERfNBoWew1NERRlbxbrPMouTvFcga6EjKk) | #11| Tuesday, December 05, 2023 09:00 AM PT (Pacific Time) | | | ## Leadership diff --git a/sig-chain/meetings/011-2023-11-08.md b/sig-chain/meetings/011-2023-11-08.md new file mode 100644 index 00000000..80d67479 --- /dev/null +++ b/sig-chain/meetings/011-2023-11-08.md @@ -0,0 +1,200 @@ +# Akash Network - Chain Special Interest Group (SIG) - Meeting #10 + +## Agenda + +- Discuss upcoming network upgrades. +- Discussion on Github Discussion 309 +- Open discussion of chain related issues. + +## Meeting Details + +- Date: Wednesday, November 8th, 2023 +- Time: 09:00 AM PT (Pacific Time) +- [Recording](https://sshyyg4r3uoeixzudilhwdkncekgk3yw5m6mulso6foidluersuq.arweave.net/lI-MG5HdHERfNBoWew1NERRlbxbrPMouTvFcga6EjKk) +- [Transcript](#transcript) + + +## Participants + +- Artur Troian +- Deval Patel +- Jigar Patel +- Scott Carruthers +- Tony Stark +- Tyler Wright + + +## Notes + +- Artur talked about the binary update today. +- Previously there were limitations on the Network. +- This fix is non consensus breaking, but it is configuration breaking. Binary update is planned for an hour or so. +- Deval asked if providers are going to be updated as well. Artur says providers can use the older version, but they cannot bid on workloads. +- Artur talked about the impending network upgrade. Artur talked about this issue. +- Mainnet 8 will introduce resource offer into the bid. The idea is that in the future, provider will be able to offer different configurations. +- Governance Proposal and block height will be coming soon. +- Artur talked about a draft of implementation for Packet forwarding. That is the upgrade after Mainnet 8. This will either happen in December 2023 or January 2024. +- CosmosSDK 0.50 has been released this week. Akash is on 0.45x. Core teams plans to wait for some time to see other changes moving. No plans to move over the next 6 months. +- Deval needs help with CRD, as they work on provider services code changes for Content moderation. +- Deval will update the project issue in Github with specific questions. +- Artur would like all code base questions or ideas to go in Github, where he and others can comment in 1 specific place. Feel free to tag Artur on github for comment. + + +### Action Items + +- Binary update happening today. +- Tyler and Artur going to plan for Mainnet 8 upgrade. + + +# **Transcript** + +_This editable transcript was computer generated and might contain errors. People can also change the text after it was created._ + +Tyler Wright: Hello perfect timing. I took welcome everybody to Sig chain monthly meeting. I believe this is number 10. + +Tyler Wright: during the special interest groups for chain or blockchain. We talk about all things related to the Akash blockchain some Cosmos stuff as well as Network upgrades or anything like that. I know that there is a network upgrade potentially planned for the end of the month. The Firm dates will be clarified either today or sometime soon on chess. This will be not only a note upgrade but also provider upgrade and I know that prior to that there is also potential upgrade happening so lots of talk about I just wanted to make sure that the Patriot team is here because I know sometimes in the past some of the provider upgrade has affected their impressed. I just want to make sure that they have the ability to ask any questions in real time or just here in real time kind of what's going on and what the game. + +Tyler Wright: Without further Ado. I know that again. We have a couple of issues. I think those issue number 136 which is around the network upgrade mainnet 8. As well as another issue number 140. I'll link both of those issues and in the chat. Last month Archer gave us an update and all things related to upgrade to mainnet seven. I know there was some things that are being worked out to round the validator submission. Those things have been fixed and we talked about those at the last meeting. + +Tyler Wright: and then there was a team that put forth a discussion related to some Akash akt 2.0 work on that. They wanted to help Implement in the ask a couple of questions to Archer related to icq and some of the next steps there. So what the discussion that happened at the previous Big Chain meeting but again the topic of discussion for this month rather. Is around issue number 136 and then I believe that there's another issue number one forward. To Archer. I'll hand it over to you to get us going with. the topics of discussion + +Artur Troian: a guitar Yeah, so first and foremost, we are having the binary update today. This is rather. Urgent but not security issue. So historically we have had limitations on how many compute resources can be requested by deployment. And we put some logic into the transaction validation. Just making sure that people do not abuse it at the early stage of the network. And so we really debut if you want to go. the demand for high performance applications deployment. Sorry has been increasing and years and they had requests that somebody wanted to deploy. + +Artur Troian: Service with the four replicas each requesting 256 CPUs. So right now the limit is maximum 512 CPUs per deployment which obviously example of such request me go through. So we have made a new release called 26.2. Which is non-consensus breaking but this is configuration breaking. So what pretty much happens is We need to thirds of war in power to apply the new binary that will allow configurations with. Higher limits to be passed through and including blocks. The sensitively we're gonna have a binary update in an hour or so. + +Artur Troian: We had somebody dieders to apply update actually right now, which is not the good thing so they had a crash issues. So we asked them to roll it back and wait until we do it in the more or less centralized manner. And this is it for that case any questions? + +Artur Troian: Okay, moving on to the other things. Let me share screen. Okay? + +Deval Patel: So sorry to conditions. So after the binary update we are planning to update the providers binary as well, right? + +00:05:00 + +Artur Troian: Yeah, so providers + +Deval Patel: and just go ahead. + +Artur Troian: Yes, so the idea is the max that the first of all we want to update validators and RPC nodes to make sure they have upper hirings for the configuration requests for the resource requests. Providers can be still using the old version. They just won't be able to be on the deployments with a higher resource request So as soon as we confident that majority of the radiators are updated and the network is stable. We will be communicating to Providers to start picking up the 4.7 version of the provider. + +Deval Patel: Okay. I'm just asking… + +Artur Troian: All right. + +Deval Patel: because we plan to provide one click update for the version 4.7. Right and I just want to know that there is nothing change in terms of other than the command space that are the helmetric space the same right? + +Artur Troian: Yeah. yeah, there's no changes to an apis. + +Deval Patel: configuration Okay. + +Artur Troian: So when those breaking changes are in place we have them in there is not so this one is much change, so it doesn't break anything from Progressive. + +Artur Troian: moving on to the upcoming network of great, which is right now scheduled on November 20. so that one is once again Improvement requests from Washington clients and some analytics when provider does bid on Wild Card attributes + +Artur Troian: Especially for the gpus. It's not actually clear not for tenant or a safe almost. What kind of GPU provider offers for this record? So the minute 8 wheel introduce the attributes, which is pretty much. + +Artur Troian: Upgrades will introduce resource units into the beat actually resource offer. But right now we will be only attributes from the parts and idea of this entire offer is that in the future provider will be able to offer different configuration for political deployment. Let's say deployment asks for 128 CPUs but provider has only a hundred so provider should be super able to beat this offer less money. Probably, right? + +Artur Troian: And this upgrade is obviously the breaking change because it breaks the state so we gonna have to do migration which is done in the past as well as provider really change, too. Later this week. We will be having all of the instructions on how great it will be performed as well as the government proposal on the block height. + +Artur Troian: All right any questions with that? + +Artur Troian: And let me just check if you move 148. I think this is for it + +Artur Troian: Yes, so 140 is the internet. I just discussed that we gonna solve all tonight. release for + +Artur Troian: accustomed to release is out this 2.6. Sorry 0.2. + +Artur Troian: 26 0.26.2 and looks like all but that's our passing so we should be good to In case of anything goes wrong because that's not a medical grade. We can always go back to 26.1 just in case. And so that's it for current plans. There is a one upgrade that is being. + +Artur Troian: In work pretty much related to the packet forwarding so we have draft of implementation we need to do thorough testing of that. and right now I know maybe sometime in December if we Got time incorrect. If not. Then bucket forwarding will be available sometime after New Year. The other news for the blockchain and core customer SDK. 0.50 has been released this week. these are still on 40 five acts and honestly saying that the transition from 45 to 50 Is a realistic curve? + +00:10:00 + +Artur Troian: So what we're going to do is we are going to probably wait for quite a Time. seeing other chains my writing I believe they're gonna be quite a few watch fixes to the 0.50 in accord month so we would rather wait and see how it goes. Another challenge with this upgrade. Is this cosmosis Escape 0.50 is the entire code base is split into dozens of modules, which is introducing huge amount of complexity from the maintenance perspective. So we've got a hug this thing about the ways to do that properly. So let's say + +Artur Troian: at this stage if the request comes up, there won't be upgrade to point 50 in the next I would say maybe six months. or so so hopefully sometime after New Year, we're gonna have better quality on that. but From this time. I don't think we can. There's a reason to actually do that. And I think there will be for me and questions. + +Tyler Wright: Thank you so we talked about it again the binary update that's going to be happening and a little under an hour. Again. We will send out messaging to the validators when it's time for them to upgrade until that time. They should just be doing nothing and just sitting tight and then again beyond that we talked about the main that eight upgrade which is planned right now for November 20th. But again, there will be a governance proposal that'll go out prior to that with the exact blackheight and we'll make sure to update everybody across a number of different channels there and we'll stay closely linked with pray Tour on the provider side again, no only binary changes updates are happening today. So nothing else should be affected on the provider side. + +Tyler Wright: And then beyond that Artur talked a little bit about after the main data May net eight upgrade around packet forwarding that is going to be tested and some time in the near future. So we've been plenty going on. We've also talked about Cosmos SDK and our plans for console SDK in the near future. + +Deval Patel: for half an hour and then go through the things and guide me how to do the things in the provided service and the pull request so + +Artur Troian: What changes are you planning to? are you talking about? + +Deval Patel: We are planning to introduce a new CID for Content moderation where they should be able to add our greatest for blocking host name as well as the images and the wallet address. + +Artur Troian: I see. + +Deval Patel: So basically I'm trying to get that from presentation of getting things something like configuration. I'm trying to get those things from the CID, So once if anybody else that's CID and they put the values in there I should be able to access that right and based on that. I'll make decisions in that whether I should be able to meet So I figured out the part where we are not paid right? But I'm looking for help where I can put the cids and forward new CID please right that coding new CID is okay, right but adding proper Channel where I can get it data from right? that's challenging part. I'm trying to figure out right. + +00:15:00 + +Artur Troian: can you first maybe have is there an issue for that it helps or + +Deval Patel: That issue for that but not particularly the CID portion. it's in general form of. + +Artur Troian: I see. + +Artur Troian: so Yeah, unfortunately timing is a little bit weird frankly saying I don't think I will be able to do frankly saying next two weeks. + +Deval Patel: moderation API + +Deval Patel: Okay. + +Deval Patel: Okay. + +Artur Troian: Because we have also things going on this week and I will be meeting with team next week. So it's gonna be really tight my suggestion is write an issue + +Deval Patel: No. + +Deval Patel: Doors all so what I'll do that, I'll try to figure it out by going through all those things right if I need help then I'll message you right if you are able to help while Discord and that's fine, that's all. + +Artur Troian: I would say the best would be to maybe highlights implementation what you're trying to do? So that just in case… + +Deval Patel: Yeah. + +Artur Troian: if I can support anything on the early stage so you don't do some things and then apparently all then need to write it completely from scratch. So if you… + +Deval Patel: Yeah, sure. + +Artur Troian: if you outline the least of the things put them in GitHub destruction, I will be able to reply within a few hours after the you post it. make sure to tag me so I can see the rest. + +Deval Patel: Yeah. + +Deval Patel: Okay, sounds good. Thank you. + +Tyler Wright: Our turn let's do have any pushback on this. I was going to suggest there's already a Content moderation item in that project board the engineering and product roadmap project board that Deval and jigar have access to maybe they could just put the comments in that and then tag you there and then we could talk about at least of the high level during the engineering sinks. If you're able to attend prior to I know you're out of office next couple weeks with some work things. + +Artur Troian: Yeah, yeah that whatever is suitable. I just make sure that using GitHub. + +Tyler Wright: Okay, Yeah, so Deval, if you could put it inside that content moderation issue that you're already working on and in the comments, then we can handle it again Arctic respond very quickly in the comments via GitHub. + +Deval Patel: Yeah. + +Tyler Wright: Beautiful. Thank you. Does anybody else have any other chain or network upgrade related discussion or topics? + +Tyler Wright: Cool again, I know about 40 minutes away from the binary updates and then continuing to test and get ready for the next mainnet. Aid upgrade amongst the number of other things. thank you to Archer Scott and others for all the work that you all have been doing on the core team side. And again, thank you to our members of the community. Obviously. Thank you to pray to her for all the work that you do in supporting upgrade on the preacher side for many of the providers. So feel free to join more of these conversations where you can talk with the core team about anything Network up the greatest special as we get ready for mainnet 8 upgrade after today's events and then beyond that pack affording go ahead Arch. + +Artur Troian: So yeah, just sort of probably my suggestion so whenever you have Think that you guys want to improve our physics. This is going to be the I need help from engineering the best way just make sure to put the discussion in the GitHub. Not the Discord. So this court is mainly to General discussions and… + +Deval Patel: Yeah. + +Artur Troian: thoughts But if that relates to whatever happens to the core product. I mean blockchain as well as a provider is going to be the quickest way so I can take a look and apply there. + +Artur Troian: And as soon as we see that discussion in the GitHub either Scott or me, or maybe Autumn even can just jump in and reply if you don't reply don't hesitate to just tag us or then if you don't reply just being in this score that's why the conversation isn't going + +00:20:00 + +Deval Patel: Thank you. + +Tyler Wright: Thank you Alright, I think that wraps up the agenda for today again. If anybody has any questions, feel free to drop those in GitHub specifically around this special interest group because it's very technical if anybody needs me for anything. Feel free to reach out to me via Discord or get GitHub. But again, appreciate your all time today. Look out for some changes happening on the binary today. Again Patriot team will keep you up to date after hopefully the successful upgrade or updates over the next hour and when the providers should be upgrading and then we'll follow up with some more information to the main updates coming soon. upgrade comes in + +Tyler Wright: All right, everyone. Have a great rest of the day. Again. If anyone needs anything today, please feel free to reach out to myself Artur others, but we'll be getting ready for this binary update happening in the next 40 minutes or so. Appreciate everybody. We'll talk soon. Bye. + +Artur Troian: restaurant + +Jigar Patel: Right. Thanks guys. + +Meeting ended after 00:21:20 👋 + diff --git a/sig-community/meetings/009-2023-11-15.md b/sig-community/meetings/009-2023-11-15.md new file mode 100644 index 00000000..17180374 --- /dev/null +++ b/sig-community/meetings/009-2023-11-15.md @@ -0,0 +1,297 @@ +# Akash Network - Community Special Interest Group (SIG) - Meeting #9 + +## Agenda +- Overview Of Community Sig Group +- Discussion on 2024 Events Working Group +- Discussion on Hackathon Working Group +- Community Support Proposal +- Community Recap blog post +- AkashEdu Progress + +## Participants +- Adam Wozney +- Andrew Gnatyuk +- Dimokus +- George Pro +- Kamuel Bob +- Robert Del Rey + +## Meeting Details +- Date: Wednesday, November 15, 2023 +- Time: 11:00 AM PT (Pacific Time) +- [Recording](https://elrhjnozov4zcwv4mcpc7n4za4nyuxelufxrk56hniqprbk3bmka.arweave.net/IuJ0tdl1eZFavGCeL7eZBxuKXIuhbxV3x2og-IVbCxQ) +- [Transcript](#Transcript) + +# Meeting Notes + +### Overview Of the Community Sig Group +##### Adam Wozney: +- Adam Wozney welcomes everyone to the November special interest group Community call. +- Focus on discussing, supporting, and managing Akash Community initiatives. +- Mentions the Events Working Group as a successful example of a community initiative. +- Special Interest Groups (SIGs) are constants throughout Akash's lifespan. +- SIG calls lead to the formation of working groups with specific timelines and task-oriented goals. +- Explains the iterative nature of SIGs and working groups using the example of the first Akashathon. +- Highlights the success of working groups, citing the positive outcome of the 2023 events working group. + +### 2024 Events Working Group +##### Adam Wozney: +- Working group has met twice to discuss events for 2024. +- Proposal is [live on GitHub](https://github.com/orgs/akash-network/discussions/380) for community review and discussion. +- The proposal covers event selection, resource requirements from the community pool, and a proposed budget. +- Discussion period on GitHub until November 27. +- Not a fund withdrawal proposal, but a signaling proposal for community agreement. +- If passed in December, a resourcing proposal will follow for event logistics, sponsorships, etc. +- Adam acknowledges his role in leading the organization of Akash's presence at events. +- Suggests the continuation of his role as the lead organizer unless there are significant objections. +- Assures the community that all event details will be made public before implementation. +- Community members are encouraged to review and provide feedback on the GitHub discussions for transparency. + +### Hackathon Working Group +#### Adam Wozney: +###### Hackathon Overview: +- Formation of a working group around the first Akash hackathon discussed. +- Acknowledgment of both positive and negative outcomes from the initial Akash hackathon. +- Acknowledges the beneficial role of hackathons in onboarding new developers to the Akash ecosystem. +- Highlights the purpose of providing tools, training, and resources to encourage building on the Akash Network. + +###### Post-Hackathon Actions: +- Proposed Changes for Next Year's Hackathon: +- Proposes a rough plan for three hackathons in the next year, spaced approximately every three or four months. +- Key focus on determining the budget considering Akash's delegation of tokens to Dorahacks. +- Highlights that 70% of staking rewards delegated to Dorahacks will return to the community pool for prizes and hackathon operations. +- Contemplates using Dorahacks resources for prizes or potentially requesting additional funding for prize amounts. +- Open discussion on whether to increase, decrease, or maintain the prize amounts from the initial 50k USD. + +#### Robert Del Rey: +- Asks about the possibility of obtaining Twitter data to measure the reach of the Akash hackathon. +- Expresses curiosity about the Twitter metrics during the hackathon and its impact on developer attention. + +#### Adam Wozney: +- Responds that tracking Twitter metrics is challenging, and he doesn't recall if there was a specific hashtag for the hackathon. +- Suggests combining retrospective documents from various sources, including dorahacks and internal discussions. +- Proposes including the compiled information in the end-of-year report and community section for a comprehensive overview. + +### Community Support Proposal +##### Adam Wozney: +- Adam introduces the Community Support Proposal, a project he has been working on. +- Considers the possibility of creating a working group for further collaboration but acknowledges the existing number of SIGs and working groups. +- Describes the Akash Vanguards program as community technical support, content creators, and event organizers. +- Specifies that the proposal includes a budget for the Akash Vanguards program, which involves incentives and rewards based on program requirements. +- Outlines the inclusion of a budget for specific roles at Akash, such as community manager roles. +- Clarifies that the exact nature of these roles is still under debate and development. +- Details a budget for bounties and rewards, offering a straightforward mechanism for the community to propose and fund specific tasks or projects. +- Explains that bounties are funds allocated for community proposals, allowing individuals to contribute to Akash-related goal +- Consider the possibility of creating a working group for the Community Support Proposal. +- Highlights the ongoing development of the proposal in collaboration with members of Overclock. +- Plans to share the proposal on GitHub discussions for community feedback. +- After incorporating feedback, the proposal will be presented for a governance vote. +- Aims to have the proposal live for a community governance vote before the end of the year. + +### Akash Community Recap Blog Post +##### Adam Wozney: +- Adam Wozney discusses the agenda item of the 2023 Akash Community Recap blog post. +- Mentions ongoing collaboration with the PR agency at Overclock Labs to draft the year in review for the Akash ecosystem. +- Specifies that the blog post will encompass product launches, mainnet launches, and the significant addition of GPUs to the network. +- Highlights the importance of including community-related activities in the recap. +- Encourages community members to contribute by suggesting specific highlights, initiatives, or programs. +- Urges participants to share ideas in the Sig Community Channel or send direct messages, expressing interest in community input. +### AkashEdu Progress +- Acknowledges the launch of Akash Edu earlier in the year with one curriculum. +- Highlights the addition of two new videos created after the recent hackathon, featuring Robert and another community member. +- Mentions two more videos in progress, one on putting GPUs onto the network and another on terraforming a project. +- Proposes adding the new curriculums and video demos to Akash Edu to enrich the educational content. +- Discusses ongoing collaboration with Omniflix for platform updates streamlining the Signup Process: +- Shares concerns about the complexity of the current signup process on Akash Edu. +- Anticipates a smoother journey for users interested in Akash Edu, eliminating unnecessary roadblocks. +### Community Awareness and Engagement: +- Robert expresses concern about how to engage and update the community effectively, considering the diverse audience, including both tech-savvy developers and general community members. +- Adam acknowledges the challenge and provides insights into various initiatives to address this issue. +##### Approaches to Community Engagement: +###### Events Participation: +- Adam highlights events as a way to engage and introduce more people to Akash. +###### Hackathons: +- Adam acknowledges the positive impact of hackathons in bringing new developers and insiders to the community. +- Acknowledges the need to improve tracking methods to measure the effectiveness of hackathons in onboarding new members. +###### Community Support Proposal: +- Stresses the importance of a robust support system, particularly through the vanguards program, to ensure timely responses to technical queries. +- Recognizes the potential negative impact on the community if technical questions go unanswered. +###### Akash Edu: +- Adam Highlights Akash Edu as a valuable tool for onboarding individuals interested in Akash but unsure how to get started. +- Acknowledges the need for more automation and user-friendly processes in education initiatives. +###### Local Meetup Groups and Regional Engagement: +- Adam expresses support for Robert's initiative of local meetup groups, seeing it as a valuable way to engage with the broader crypto community. +- Shares the desire to build on this idea and utilize the Insiders program to introduce Akash to new communities. +###### Scaling Community Activities: +- Adam emphasizes the need to scale community activities and create a flywheel effect by involving more community members. +- Envisions a cycle where increased community involvement leads to successful tracking, enabling the request for more resources, which, in turn, attracts more community members. +- Acknowledges the current robust of the Akash Community in terms of active contributors and members. +- Expresses the intention to grow and scale the community in the upcoming year. +###### Call for Ideas and Contributions: +- Encourages community members to share ideas on reaching new audiences and increasing Akash involvement. +- Suggests posting ideas in the Community Sig Channel or the Insider Chat. +- Proposes the creation of a proposal template to make it easier for community members to present their ideas coherently. +- Outlines potential components of the template, including an idea overview, impetus, timeline, resource needs, and forecasted outcomes. +### Other Matters discussed +#### Idea Review and Working Groups: +- Andrew raises the question of who will review community ideas and work on them. +Adam outlines a potential process: +- Community members submit their ideas using a proposed template. +- Ideas are shared in the community, inviting comments and suggestions. +- If the idea gains interest, it could lead to the creation of a working group. +- Working groups can further refine and develop the idea. +- For resource-intensive projects, a community support proposal can be initiated. +- Adam emphasizes that the entire community has the opportunity to review and contribute to ideas. +## Action Item +- Adam to finalize the hackathon proposal and budget. +- Adam to Schedule a hackathon working group call before the year-end to review the proposal +- Adam to finalise the Community support proposal before the year ends +- Adam to Work closely with Omniflix to implement AkashEdu platform updates and streamlined signup process. + +# **Transcript** + +_This editable transcript was computer generated and might contain errors. People can also change the text after it was created._ + +Adam Wozney: All right, welcome everyone to November's Sig special interest group Community call. I think it's the first one we've done in a couple months. I'm actually gonna have my video off because I'm just right and I've been on video calls all day and I can't help I got to stop looking at myself. So my video will be off but I'm a real person and I'm happy to leave this community call. Just as a reminder. we're getting someone else. Let me add them in here. + +Adam Wozney: Just as a reminder the community Sig call at least the definition of the community sake call is to discuss support and manage Akash Community initiatives a good example of an Akash Community initiative is what formed out of our very first special interest group Community call the events working group and just as another quick reminder special interest groups basically live on they're kind of constants throughout the lifespan of Akash and the ecosystem there's clients. There's website there's design there's a bunch of other special interest group calls and from those calls working groups can be formed and working groups are meant to have kind of a timeline. They're almost more task iative related. So good example of that is 2023 events. I think we're officially done with 2023 working group and now we're on to 2024 events. So it's a new working group. That's formed proc same. + +Adam Wozney: Is just a different working group another good example of that is the first akashathon that we did last year or this year. That working group were really well. I think we had a lot of key learnings from this act from that hackathon, but that Spawn from this call. So I think this is an opportunity for folks that have ideas on larger tail initiatives to kind of, share those ideas get feedback and then look for additional resources or support and proposing those ideas potentially to get funding or other folks involved in those initiatives. + +Adam Wozney: so that's the community Sig group. We have a couple agenda items to cover a lot of them are things that I'd probably covered in previous Sig calls for Community, but I wanted to see before I Are there any agenda items that you guys would like to discuss or bring up for consideration before I get into my agenda items anything that's top of mind for you in relation to how we can discuss support and manage the Akash Community initiatives. Look at the chat, if there's anything on here. Oops, looks like we're good. Cool. So, there's really one two, three four five things. I want to cover today. So the first thing I want to talk about was our 2024 events working group. + +Adam Wozney: We're at the point now where we've met as a working group twice. We've discussed upcoming events in 2024 that we think it makes sense for a cost to participate in and from that we've all gone back to our corners and The Proposal is live right now for discussion on GitHub. And I'll put a link in the chat if you guys want to review it, if you haven't seen it. Basically this proposal is kind of a signaling proposal. So what you're going to see here as soon as I put in the chat. There you go is the high level on how we as working group decided on which events. We believe the cost should have a presence at We discussed and decided on how much we would need to pull for resources from the community pool for 2024 events. + +Adam Wozney: It lists the meetings we had and recordings to those meetings and then it actually showcases the final 2024 event proposal. So this is going to live for discussions on GitHub until the 27th of November. So basically another little under two weeks. People have already started putting comments in there so far. It's been positive views. So nothing really we have to update on the proposal because this is just a signaling proposal. We're not pulling money out of the community pool yet. This is basically saying the community agrees that the events that we have listed and the proposed budget that we will pull from the community pool is okay. + +Adam Wozney: Once that goes up for a vote in December. Hopefully it passes again. It's just signaling. So we're not gonna pull any money from the community pool at this point. But if it passes we're going to put together a resourcing proposal and that proposal will be just spend for events that we want a cost to have a presence at each of those events have already been determined by the community. They're all listed in the high level Community signaling proposal that's live right now for review and if that q1 proposal passes, then we basically have budget to start debating and deciding what we want to do at these events who can go and start locking in the logistics and sponsorships and all the other side of an activities that happen at these conferences and events up until this point. + +00:05:00 + +Adam Wozney: It's been me essentially leading the charge on organizing what our presence looks like at events. But a lot of folks in this call and in across the community have helped with the deciding who goes what we what people can do to support the events on site and all that stuff. So unless there's any, giant issue with people saying no, we don't want Adam to leave these events anymore, which I understand I can be annoying sometimes. + +Adam Wozney: We can kind of continue to use me as the kind of the sherpa for these activities, but all of these events, will be made public before they go live all the details on who's going and what we'll be doing there is live for the community to review. So everything will be very Case by case. But I'm one final note on this is events. I mentioned this in the proposal. It's not a perfect science. So things can change, we might decide we don't want to go to an event in a specific quarter and that's fine all the resources that we pull off from the community pool per quarter. Go right back into the community pool that aren't used. go and review the events that are upcoming leave your feedback and the GitHub discussions. There's two more weeks before we put this proposal live so we can still have time to update it or add some notes, but I think it's pretty well thought out is the second time we're doing it. So we're getting better at kind. + +Adam Wozney: event proposals any questions on upcoming events as a part of the community Sig + +Adam Wozney: I think be look good cool. next up is the hackathon. So yeah as mentioned from these calls we formed a working group around a first Akash hackathon, there were good things that happened as a part of the Akash acted on there were bad things, but that's okay the goal really for me for my perspective of the working group for that this first Akash hackathon was to learn what doesn't work because I know and I think + +Adam Wozney: Folks in this call would agree. Hosting hackathons is a beneficial way to bring on new developers into the ecosystem to introduce them to Akash and to give them the tools training and resources to hopefully build on the Akash Network, which is good overall. So from those key learnings, we had a retro call with the different community members that participated in support we had call set with door hacks, which was our hackathon service provider and we're starting to work on the budget right now for next year's hackathon. This year will be a little different the next year and I'm still putting together a rough proposal and I want to set up a hackathon working group called before the years out to kind of discuss the proposal that I'm working on but the idea is right now at a high level I want to potentially host three hackathons next year, basically. every, three or four months. + +Adam Wozney: TBD and what we want people to build TBD on the timing and all that stuff, but the big question that we need to kind of figure out right now is budget because since Akash is delegating tokens to Door hacks to be able to use their platform 70% of the staking rewards that door acts will go right back into the community pool for prize winnings and for the operations of the hackathon. + +Adam Wozney: So because of that we might be able to just use door hacks resources for prizes or we might want to in The Proposal ask for a small amount of additional funding for prize amounts. Because the first one we did was 50k USD. We didn't spend it all which was good went back into the community pool. The next ones we might want to raise it. We might want to lower it TVD. We're still kind of working on that. So the hackathon's idea right now is still kind of being locked in in terms of what the proposal looks like and the budget but the goal is once I have that and kind of a good spot. I want to set up a hackathon working group call where I can review The Proposal of folks that want to join that call and then see if there's any issues and if not that will go through a very similar process as the events calls and go up for GitHub for discussions for review and then any issues or ideas we can Implement into a potential proposal for 2024 hackathons. + +Adam Wozney: So that's kind of where it stands right now any questions on the hackathon working group? + +Adam Wozney: All right. go ahead Robert. + +00:10:00 + +Robert Del Rey: Hi all again about that the hackathon Adam. For the next working group. Do you think it's possible maybe to have the Twitter data to see how many reach that cash hackathon had during that time because during hackathons like you say, I agree with you hackathons, bring lots of developers and lots of attention to the network that is hosting the hackathon. So I'm curious on how that data on Twitter look like while Akash was doing the hackathon if you know what I mean. + +Adam Wozney: Yeah, totally. I'm not sure I can't remember if we had a specific hashtag for the conscientathon. Twitter metrics are kind of difficult to track. So I don't know if we have anything from the akashathon that we can share in an easily digestible format where you can kind of see how many people liked or retweeted or shared or whatever. I think we use the hashtag akashathon. I can't remember but I would have to look into that. we did a couple Retros one with door hacks one with the ins. + +Adam Wozney: Is that participate in supporting the hackathon and I think we did one internally just at overclock labs to kind of talk about it. So I think if anything what I can do can combine those retro docs that I've created to maybe do and include in our end-of-year report that we're working on right now to put out as a newsletter blast and as a blog post 2023 Akash Network and review there will be a community section there. So I think that's something we can maybe include in that but I think that's a good idea. + +Adam Wozney: cool all right. Next up is a community support proposal and this is something that I've been kind of working on by myself. It might be worth maybe even creating a working group around this. I don't know if we want to do another one. I feel like there's enough sigs and working groups as it is. but if it is something that you guys think is valuable maybe we could open it up to the rest of the community be like, hey help us kind of Define community support at Akash and basically the community support rules that I'm working on is something that we also did last year. It's essentially a resourcing proposal from the community pool to Resource the Akash vanguards program. + +Adam Wozney: Which is kind of our community technical support and content creators and event organizers all the people that are actively doing things for There are requirements the part of the vanguards program. So because our requirements there is incentives and rewards as a part of that so it would include in a budget for that. There's also going to be a budget for specific roles at a cautious essentially contract workers. So Community manager roles still working on exactly what that looks like. It's still up for debate. But the idea behind that is finding people that can kind of work on specific tasks for Akash and that's essentially their roles. And then finally there's a bounties rewards and bounties rewards are basically pretty straightforward. It's like a bucket of funds that the community can propose. we need this belt or hey, can someone help create that and we'll put out a bounty for it. So there's really three separate kind of + +Adam Wozney: Did proposals inside the community support proposal that I've been working on along with some members of overclock? And the idea behind that is once it's ready to kind of be shared. We'll put it up and GitHub discussions for Community feedback. Once we implement the feedback. We'll put it online for a governance vote. And if it passes then we'll have budget for vanguards next year. We'll have for bunties budget for some kind of specific tailored goals that are beneficial to the Akash community. So that's still under development. I'm hoping to get both the hackathon and this community support proposal live in the next week or two. And that way events hackathons and Community Support can all live for Community governance vote before the end of the year so we can hit 2024 running to kind of start doing all the stuff that we're talking about here. So right now from now into the end of the year, it's a lot of planning around support props. + +Adam Wozney: Any questions on the support props that I mentioned Community Support hackathons or events. + +Adam Wozney: No, go ahead Andrew. You can type it… + +Andrew Gnatyuk: Yeah. Then okay. + +Adam Wozney: if you need to. + +Andrew Gnatyuk: I just be quiet. So, we had lost the overhead also additional budget for the bounties. And did you spend some of those did work we have bounties that problem is this part? + +Adam Wozney: Sorry say that part again. + +Andrew Gnatyuk: That we had about a budget for a bounties for last year, So did we spend some of those budget money for bounties? + +00:15:00 + +Adam Wozney: Yes. + +Andrew Gnatyuk: I did we have some bounties. + +Adam Wozney: Yes, I believe we did Tyler has been the one mostly mostly and actually Zach to a certain extent because he's been working with folks like dimokus and chimpa and maybe even you Andrew on specific tasks. So I would have to check with him to see what was spent and what wasn't spent throughout the year. Also Scott. UE he's the one that kind of manages he's the master of coin for all of these kind of programs so he has a lot of that data in front of him. He's not on this call, but if you are interested you could tag them in the community Sig Channel and say hey, I just want to know how much was spent and how much wasn't spent from 2023 on the money side if you're interested in learning more. + +Andrew Gnatyuk: Yeah, I'll just ask him. Thanks. + +Adam Wozney: Cool for And that's actually a perfect transition to my second to last kind of agenda item today, which is the 2023 kind of Akash Community Recap blog post So currently we're working with our PR agency at overclock labs to draft a kind of 2023 year in review for the entire Akashi ecosystem. It will include, product launches. It will create mainnet launches. I don't include obviously gpus added to the network will be a big part of about that and it'll be a community part as well. + +Adam Wozney: I wanted to pitch to you guys that if there's anything specific that you want to highlight things that you were working on or things that you think were interesting that of benefit to the ecosystem. Feel free to send me or message the Sig Community Channel say, hey, I think it'd be great to highlight this activity or this initiative or this program that we worked on collectively as a community in that blog post. There's only all sorts of data in there. + +Adam Wozney: spend from the community pool for I thought the hackathon that we ran to our events that we actually participated in. So we're looking to kind of put essentially it's going to be a 2023 recap report on the Akashi ecosystem. Not just Community, but I want Community have a big part of that. So if you are there is anything that you'd like to think about that still a few weeks till that would go live. But if you have ideas put it into the community Sig Channel and we can make sure to add that into the report that will go out at the end of the year. So I wanted to mention that + +Adam Wozney: and then the last thing is Akash edu, so personally the four things and Robert's very familiar as I've been chatting with him about it the four things that I'm very much focused on up until 2024 where I can start executing on this stuff is the events getting budget approved from the community pool for that so we can actually start attending events and getting insiders to represent a cash out events. One is the hackathons that I want to run three. Hopefully hackathons next year. There's a lot of planning that goes into that. The community support proposal, for vanguards budget for bounties budget for specific roles. And the final leg is Akash edu, Kashi to you is something that we really launched, earlier this year and I would say too much fanfare but because it was the first time we're doing this there was a lot of Road. + +Adam Wozney: Stocks to kind of going through the program. We only had one curriculum added. But after this past hackathon, there were two new videos created one from actually Robert on this call one from another Community member and then there are two other videos one from someone that overclock on how to put gpus onto the network and then also one from an Insider Mr. Luna who's been developing a video on how to terraform a project that he's been building out for a while now because there are four essentially curriculums or for new video demos. I thought we should add those to shi to you. I'm also working with omniflexes are platform for Akashi to you currently if you actually go through the platform. It's a little bit too difficult in my opinion you have to apply and then you have to whitelist your akt address and then you have to get an nft just to gain access to the prerequisites docs and is just a lot of roadblocks to kind of having it turnkey. + +Adam Wozney: People just to go and actually get this education and get an ft saying that they've accomplished it. So a flex is about halfway through their update to the sign up process for Akashi to you. and basically the signup process is gonna be much more streamlined. So all we have to do now is point people you want to learn about You want to get an nft for going through a curriculum go to this website once they're on that website. They'll just log in through their Kepler wallet and then they're gonna access to prerequisites the video demo and the quiz and then once they pass the quiz they get an nft. + +00:20:00 + +Adam Wozney: So the idea is we're gonna add four new videos which will to us five videos on different aspects of Akash teaching people about how to do things on the network and then also getting them streamlined. So all we have to do is point people to the website and we gain access to the folks that have passed these courses, who they are. There will be a contact collection form so we can reach out to people after the fact when we have new courses that go up. So that's the main focus for me. I would say over the next, one and a half months before the end of the year is to get the events hackathon Community Support proposals past and then I can work on all the things that are aligned with that and then included in that is Akashi to you updating that sign up process and once the curriculum is added once the sign-up process has been simplified. Then I can start working on adding more curriculum tokashi to you. + +Adam Wozney: If you look at across Cosmos, there's really only one other similar platform that has an educational platform and They have kind of a Builders education platform, but that is a lot more handholdy. It's like a six week course, you have to sign up that people that actually host workshops. because we're pretty small team because we want to make this TurnKey as possible. We want to make this automated. So the goal of Akash edu is to make this an automated process where all we have to do at a certain point is just add new curriculum to the course and then people can go through it without us having to kind of hand hold them. So those are really the big four things on the community side. I would say that is being built out over the next few months here. So that's kind of it for the + +Adam Wozney: for the updates. Do you guys have any questions on anything that we covered Akashi to you Community Support hackathons events. + +Adam Wozney: Cool seems like everyone has a pretty good understanding. + +Adam Wozney: Go ahead Robert. + +Robert Del Rey: Yeah, I guess that's the thing like the people. Very simple with the community the most and even those that are building developers. Usually we are very up to date about what is happening with the network. I'm just wondering now how we could + +Adam Wozney: Yeah. I mean, I would say there's so everything I kind of mentioned is kind of what for me personally because I work on this full-time and I know you guys kind of a lot of you, volunteer your time or you're part of the vanguards program to kind of get involved. + +Adam Wozney: I would say the events that we are participating in that's one Avenue of getting more people involved in Akash because we're meeting people on site and getting them to apply to insiders inviting them into our community. One. Other thing is the hackathons. I think from this past hackathon. There's a couple insiders we got out of it. We introduced a costume people that didn't know what Akash which I think is beneficial. I think we could do a little better job of Tracking how many people join the network from that hackathon? And that's a key learning from this last one. + +Adam Wozney: The community support prop that's a big part of it because vanguards being able to respond to Community Technical Support questions in a timely manner is essential the worst thing that can happen is somebody finds a caution. They're really interested and excited about it. they go to Discord and ask a technical question and they get radio silence and nobody responds to it. That's a death knell for a community. So I think getting those support proposals are all super beneficial because it's focused on awareness getting people into the network and support and then Akashi you for people that maybe are interested in Akash, but don't know how to get started. That's a way to kind of get people onboarded and get them involved. The one thing that I really want to do on top of these things and this is something that I want to build out maybe with community members as well. One is what you're working on Robert which is kind of local meetup groups where people can actually host meetups in their regions. Not just about a cash but about crypto + +Adam Wozney: I think that's a great idea and that's something I've wanted to do for years. And I think we're just about at the point where we can start building that out. And then in addition to that, I think there are other ways that we can utilize the Insiders program to introduce a cost to new communities. We're pretty small team. I actually just got off a call with one of my former colleagues that works at consensus and just to put it in perspective. I'm the only one that's full-time working on community initiatives for overclock Labs at consensus. They have a team of about 12 Community people managing a pretty Global program. There are definitely things about their program that don't make any sense. But there are definitely things about their program that makes a lot of sense and it really just comes down to bandwidth and the availability to people to work full-time and knowing who has the skill set to do specific tasks as a part of community building. + +00:25:00 + +Adam Wozney: Because it's not just the fact of saying hey, let's go out to different communities and let people know to gosh that's cool. And that's great. But how do we actively track and measure the success of initiatives? That's how we get resources for future activities. It's great saying, hey, we want to host, a bunch of meetups all around the world and people are doing it cool sounds good on paper. How are we tracking the success of those activities? That's how we can get additional resources and funding. + +Adam Wozney: For getting more community activities going and it becomes kind of a flywheel effect, more people involved the more you can track it if tracking successful you can ask for more resources to get more people involved and then it goes back to finding more community members and I would say since I've been here this is probably the most solid the Akash Community has been in terms of community members that are active in terms of people that are contributing but now we're at the point where going into next year. I want to kind of grow it I want to scale it and the things that I'm mentioning right now the support proposals Akashi all of this stuff goes into that higher level kind of vision of what the Akash Community can be. But as always if people have ideas. + +Adam Wozney: On ways they can reach new audience members get more people involved in Akash and what we're doing here throw them into the community Sig Channel if you're an Insider, which I think most everyone on this call is you can put your Insider ideas Insider chat. I would say if you're really serious about a specific idea. The best thing you can do is create a document on it. and I'm actually going to make a note and this is something that might be beneficial for folks. make a note on this just for myself. documentation on your ideas + +Adam Wozney: Create template. + +Adam Wozney: Template so one maybe thing that I'm gonna take away from this is I've been doing community building for 10 years now. I'm an old salt. one thing that I think that could be helpful for folks that have great ideas and just don't know where to start I think something I can go back and do is create a proposal template so similar to the GitHub proposals for people that want Community Resources. I think I can make people's lives a little easier that have ideas to pitch and ways they want to support together template that people can just fill out and that would include an overview of your idea the impetus of your idea. why you think this is a good idea the timeline for building out your idea from inception to launch if there's resources needed in terms of financial resources or swag or just other people to help you free resources. That's a big one. + +Adam Wozney: And then what the proposed or forecasted outcomes over that timeline look like that is something that I think I could put together that would make it a little bit easier for folks that have ideas on ways. They can find your community members launch specific programs or initiatives because at the end of the day, you have to sell your ideas to not only myself and overclock Labs members, but the community itself. I know if somebody came to me and said hey, I have a great idea to do XYZ thing I'd say that's awesome. Do you have something I can review because that's where you can actually start building out your idea. your ideas really don't become real until you put pen to paper and I think that's something that needs to happen for every good idea. Otherwise, it's just nothing it doesn't exist. + +Adam Wozney: So I think that's something that's a way I can help folks that are interested in doing things that we're not doing right now get resources funding support. So I made a note of that and I think that's kind of a good idea to put together folks that want to build things out and create new things that don't exist yet as a part of the ecosystem. + +Adam Wozney: Cool any other thoughts ideas or feedback before we wrap up today's Community sake call? + +00:30:00 + +Adam Wozney: if you guys wait actually says who will review those ideas who will be working with the guy who have ideas. great question Andrew, so just kind of spitballing here. I would say let's say Andrew you're like, I really think it would be awesome if akash, Had some form of I don't know. + +Adam Wozney: Let's see here. I think we should start to host or create telegram groups that are language specific people in Costa Rica people in Japan people here people there. I love it on paper. I love The template that I think I could create would list out the overview of your idea. why you think it's important the timeline for creating it the resources needed into forecasted outcomes. And then once that document is filled out, I think the best place to share that would be probably first thing is put it on the community hey guys, here's an idea. I've been thinking about for a while would love your guys's thoughts and feedback open it up for comments suggestions, whatever from there. It could go into the potential creation of a working group where people Join that call that are specifically interested in that idea. + +Adam Wozney: And then from there if resources are required, you could create a community support proposal. You could put it up and potentially get funding and then once you have that funding you're basically able to go and build out this idea. As for who's reviewing those it's no particular person. It's the whole Community. It's people that are part of this that want to get involved. If nobody, contributes to that idea then you still have the ability to go and put it up on line or up on chain for a vote if there's no resources needed you could just go do the idea. There's no one stopping you anything that's free. You guys can go do that's one thing I think people don't realize if you have a good idea and you don't think it's gonna cost you anything to do it, but it's gonna be successful and you really want to get involved. You can just go do it. I think for most people though, they're probably gonna look for some sort of financial resources to kind of + +Adam Wozney: Dedicate their time to building out something but if you don't need those resources, you're able to do it. So high level answer for you Andrew. Is anyone can review those ideas it all would go online. It would all go in the Discord Channel people can put their thoughts and feedback in and then it kind of goes from there. There's no single person that says yes or no to potentially developing those things. I hope that answers your question. + +Adam Wozney: cool anything else before we wrap up today's call? + +Adam Wozney: thank you guys for joining November's Community sake call. I'm sure December we're gonna have a handful of things to cover again. Hopefully a lot of the stuff that we caught talked about today will be wrapped up or live online for votes, but I'm excited. I think 2024 is gonna be a huge year for Akash and for community. So thank you guys as always for joining this call. If you have any feedback thoughts questions head over to the community Sig Channel and leave your notes in there. But with that as always I'll see you guys in the matter verse. Take care everybody. + +Robert Del Rey: Thanks, Stay safe everybody. + +Meeting ended after 00:33:37 👋 + + diff --git a/sig-documentation/README.md b/sig-documentation/README.md index d2b283d1..2d1a0ac4 100644 --- a/sig-documentation/README.md +++ b/sig-documentation/README.md @@ -25,7 +25,7 @@ The goal of this SIG is to foster a community around the creation and maintenanc | #7 | Tuesday, July 25, 2023 07:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-documentation/meetings/007-2023-07-25.md) |[Link](https://github.com/akash-network/community/blob/main/sig-documentation/meetings/007-2023-07-25.md#transcript) |[Link](https://vxe3skefb3gv6igjgmwqlzhkfhsvltmzf4cufajqw6yuzh46wana.arweave.net/rcm5KIUOzV8gyTMtBeTqKeVVzZkvBUKBMLexTJ-esBo) | #8 | Tuesday, August 22, 2023 07:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-documentation/meetings/008-2023-08-22.md) |[Link](https://github.com/akash-network/community/blob/main/sig-documentation/meetings/008-2023-08-22.md#transcript) |[Link](https://53oqqojl3emoys343dhzcfp5hsfmcs2q4r4kiah4wn3wj77pbyta.arweave.net/7t0IOSvZGOxLfNjPkRX9PIrBS1DkeKQA_LN3ZP_vDiY) | #9 | Tuesday, September 26, 2023 07:00 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-documentation/meetings/008-2023-09-26.md) | [Link](https://github.com/akash-network/community/blob/main/sig-documentation/meetings/008-2023-09-26.md#transcript)| [Link](https://dknymsd25d4wo4gbxp6435niarkm3ugz7f6onipsi7r7aoghn72q.arweave.net/GpuGSHro-Wdwwbv9zfWoBFTN0Nn5fOah8kfj8DjHb_U) -| #10 | Tuesday, October 24, 2024 07:00 AM PT (Pacific Time) | Coming Soon | Coming Soon | Coming Soon +| #10 | Tuesday, October 24, 2024 07:00 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-documentation/meetings/010-2023-10-24.md) | [Link](https://github.com/akash-network/community/blob/main/sig-documentation/meetings/010-2023-10-24.md#transcript) | [Link](https://j7umqwzmkiglhuckkezav7c2rbh4cirv4d2nrjophespxwsjqtxa.arweave.net/T-jIWyxSDLPQSlEyCvxaiE_BIjXg9Nilzzkk-9pJhO4) | #11 | Tuesday, November 28, 2024 07:00 AM PT (Pacific Time) | | | | #12 | Tuesday, December 26, 2023 07:00 AM PT (Pacific Time) | | | | #13 | Tuesday, January 23, 2024 07:00 AM PT (Pacific Time) | | | diff --git a/sig-documentation/meetings/010-2023-10-24.md b/sig-documentation/meetings/010-2023-10-24.md new file mode 100644 index 00000000..16c888e2 --- /dev/null +++ b/sig-documentation/meetings/010-2023-10-24.md @@ -0,0 +1,229 @@ +# Akash Network - Docs Special Interest Group - Meeting #10 +## Agenda +- Update on Documentation +- Docs 2.0 Effort + +## Meeting Details +- Date: Tuesday, October 24th, 2023 +- Time: 7:00 AM PT (Pacific Time) +- [Recording](https://j7umqwzmkiglhuckkezav7c2rbh4cirv4d2nrjophespxwsjqtxa.arweave.net/T-jIWyxSDLPQSlEyCvxaiE_BIjXg9Nilzzkk-9pJhO4) +- [Transcript](#transcript) + +## Participants +- Damir Simpovic +- Denis Lelic +- Dimokus +- Emmanuel Arthur +- George Pro +- Samuel Walker +- Joao Luna +- Tyler Wright + +## Metting Notes + +### Docs 2.0 effort +#### Tyler: +- Appreciated the work done by Luna and the Quasarch team. +- Mentioned Piyush and his team's involvement in optimizing the efforts and the availability of the repository. +- Mentioned that the [repository is now public](https://github.com/akash-network/new-docs) for everyone's access. +- Highlighted the work done by Quasarch in the migration from Gitbook to Hugo and optimization of the structure. +- Discussed ongoing efforts related to optimizing docs 2.0. +- Mentioned that these efforts are being passed to Piyush and the website revamp team for completion. +- Highlighted that Scott has been working on technical documentation for developers focusing on the Akash network code base. +- Announced the inclusion of this documentation in multiple places, specifically in the docs 2.0 site for accessibility by developers. +- Noted that this documentation targets those developing and building on top of Akash. + +### Call for Additional Contributors to Documentation +#### Tyler: +- Discussed the need for additional contributors to create, edit, and update documentation. +- Mentioned that Scott had led this effort with support from Andre, but Scott's focus has shifted more towards the Engineering Core team and Overclock Labs. +- Encouraged community members to contribute to technical documentation following the structure laid out by Scott. +- Highlighted that there are rewards available for those contributing to documentation. +- Noted that Scott has many responsibilities within Overclock Labs, making community support essential for maintaining and improving documentation. + +### Consideration of Video Documentation +#### Tyler: +- Mentioned the recent monthly meeting where video documentation was a significant topic of discussion. +- Noted that while there is substantial written documentation on Akash and elsewhere, there is a growing demand for video documentation. +- Highlighted the ongoing work by Andre on videos related to deploying stable diffusion. +- Mentioned that other community members have expressed interest in creating video guides or tutorials for specific tasks to be included on the documentation pages. +- Indicated that this has been a focal point of discussion within the group for documentation over the last month or two. + +### Update on Documentation +#### Scott Carruthers: +- Shared an update on new documentation. +- Mentioned that new documentation has been relatively light due to necessity. +- Highlighted the addition of documentation on stable payment deployments. +- Explained that the stable payment process is currently somewhat cumbersome but has been simplified by conducting all actions within Leap Wallet. +- Anticipated the introduction of 'taker forwarding' to further streamline the process. + +### Support for Sandbox +#### Scott Carruthers: +- Discussed the recent shift in supporting the use of the sandbox for new user experimentation. +- Noted that significant resources are now available for using the sandbox as the preferred method for new user experimentation. +- Highlighted that manual processes for supplying new users with Akt, faucets, have faced challenges due to fraud protection measures. +- Mentioned that there have been weekly requests for minor edits in the documentation, which have been addressed. + +### Whitelisting Changes on Sandbox +- Tyler asked Scott about the requirement for whitelisted wallet addresses for users of the sandbox. +- Scott explained that the requirements for using the sandbox have changed. +- Scott mentioned that the whitelisting requirement has been temporarily removed. +- Scott clarified that users currently do not need to be on the address whitelist to use the sandbox. +- Scott indicated that while the current guardrails have been lifted, there may be the need for additional safeguards in the future. +- Scott discussed potential policies to address abuse, such as workloads running for extended periods. + +### Leap Wallet and Documentation Needs +- Denis inquired about the possibility of deploying with Leap Wallet through Cloudmos. +- Denis mentioned that he had heard positive feedback about Leap Wallet and was interested in its deployment capabilities. +- Scott responded that people who have used Leap Wallet often find it to be a superior experience. +- Scott noted that the Cloudmos team has been looking at adding Leap Wallet support, and it may already be in place or close to being implemented. +- Denis suggested the need for an additional section in the documentation to cover tokens and wallets, particularly Leap Wallet. +- Scott agreed that once Leap Wallet support is in place and tested, documentation would be necessary. + +### Other Matters Discussed +- Samuel inquired about developer guidelines related to documentation and any specific standards to follow when submitting PRs. +- Tyler asked Scott if there are established guidelines or standards for developer documentation. +- Scott responded that there are no strict guidelines for developer documentation. +- Scott suggested looking at the structure and layout of existing documentation for reference. +- Scott mentioned that there might be some initial back and forth when submitting a PR for documentation, but the process usually becomes smoother. + +## Action Items +- Group to continue to update and improve documentation. +- Group to make Leap Wallet documentation available. + +# **Transcript** + +_This editable transcript was computer generated and might contain errors. People can also change the text after it was created._ + +Tyler Wright: All Welcome everybody to SIG, documentation monthly meeting number nine, I believe. Or Number 10, During these special interest groups for documentation the group gets together and talks any you recommendation on the Akash network talks about documentation updates, Denis, who's been in the background? I know there's some work happening across multiple CIGS and working groups. Right now, with the Working Group of Cash website, taking on some of the efforts of the front, end of the documentation site. Luna, and the quasarch team did a great job of + +Tyler Wright: of migrating, some of the documentation from Getbook. And now, it's, again, open source that they have it on Hugo. Those efforts are not going to be in vain, as again, a lot of work has been done by Luna and the Price Arch team so much appreciate their efforts. What's happening now is again Piyush and his team that are working on the revamp of the website are going to be taking the efforts and just optimizing them that repository is available. Here, I'll drop it in. It was private for some time but now it's public. So again, everybody should have access to win. This is again the work from Quasarch and a. on their efforts on the migration and optimization of the structuring + +Tyler Wright: So again, there's been some efforts happening for a number of docs meetings related to optimizing docs 2.0. And again, those efforts are being passed now to piyush and the website revamp team to get those over the line. As there's going to be a revamped website coming very soon. + +Tyler Wright: In addition, some of those efforts that Scott has been working on in the background that have been talked about in SIG documentation over, a number of meetings are going to be added in number of places. Again, Some of the documentation is going to be brought in to the docs 2.0 site and made accessible for developers. Scott Carruthers, who's on this call, has been working on a number of pieces of documentation for developers. For more technical folks that dive deeper into the Akash network, the code base. And again, is designed more for folks that are developing building on top of Akash and so that documentation will be shared very soon. But again, Scott has done a lot of work there and that documentation will be leveraged both on the dockside and a number of other places that focus on developer experience and developer getting started. + +Tyler Wright: So much appreciated Scott and his efforts there. + +Tyler Wright: One other thing that were looking for is additional people that want to create edit and update documentation in the past, it's been an effort. That's been led by Scott with support from Andre. Andre is going to continue to stay involved in documentation, Scott, a little bit here and there, but with Scott's increased need and presence in the Engineering Core team and overclock labs, and is desire and his need to be heads down with engineering efforts. Again, we are asking for more folks in the community, to be able to contribute to documentation. And even if there is a language barrier, again, some of this documentation is very technical and the structures already been laid out by Scott. So, it's just about creating PRS and then again, whether it be internally, or again, members of the community, we can find folks that kind of edit and optimize those + +Tyler Wright: trees. Damir. Go ahead. I know you had your hand up. + +Damir Simpovic: No, you answered my question. So, Thank you. + +Tyler Wright: Yeah. And again there are rewards available for those that want to help contribute to documentation because it is certainly a need as many folks on this call know that are involved in discord and helping new and existing users interact with the Akash network. But again with Scott already wearing so many hats within the Overclock Labs organization. Now on being more heads down on engineering we're certainly calling upon the community to step up a little bit more and be able to provide some support in developing existing documentation, and making updates where they see where it needed. + +Tyler Wright: Anyone have any questions about any of those next steps? Again, if anybody wants to feel free to drop a message in SIG, documentation and we can take it from there, or, you can feel free to DM me as well. + +00:05:00 + +Tyler Wright: Cool out of the last monthly meeting. One of the big topics. I was discussed by a member. That's not here. Currently today was video documentation. I know that again there's a great written documentation both on a docs out of cash on network, as well as elsewhere. But there was a call for folks that maybe + +Tyler Wright: Respond to have some more video documentation on how to do specific things. I know that Andre has been working on some videos related to deploying stable, diffusion in eight minutes or less. But again, other community members have talked about the idea of potentially creating video guides or video tutorials for specific things that can go on the documentation pages. So, that's something that we can talk more about async but that's something that's been top of mind for folks, in this special interest group for documentation over the last month or two. + +Tyler Wright: other than that, + +Tyler Wright: Scott, I know that you have been working documentation adjacent and hopefully less and less. So over time. So we can rely on more people from the community. Is there anything on the new documentation side that maybe is worth talking about? Or does anybody on this call have anything that they want to ask about documentation wise? I'll start with you Scott. + +Scott Carruthers: Yes, I knew doumentation. I'm going to share my screen. So new documentation has definitely been. Pretty light, just out of necessity. It hasn't really been that much so they only ones that I can think of that have been added since our last SIG documentation meeting is stable payment deployments. So this is + +Scott Carruthers: a processes a little bit cumbersome right now. We've made it as less cumbersome as possible by doing everything within leap wallet. I'm so doing transfer of to Usdc and A leap wallet and then doing the IBC transfer all within Leap wallet is going to be introducing something called taka forwarding soon that it's gonna make this process, even less cumbersome. So again if someone was really interested in stable payments it's definitely possible today obviously, both from SDL perspective so we documented the inclusion of stable payments in SDL documentation several weeks ago. And then in the last couple weeks out of this stable, payment deployment, documentation, there were some bugs and leapball that we had to Wait for ratification before I could publish After the last meeting at upgrade. But those are solved. So again. + +Scott Carruthers: I don't think it's incredibly cumbersome, but it's a little bit cumbersome. Using stable payments today but I will just become easier and easier. Over time. so, that's probably the biggest documentation addition, since our last session the other one is not Necessarily an addition, but more just a shifts. and as I announced to insiders in Vanguards, over the last several weeks were now, supporting sandbox. We have a significant enough resources to use the sandbox as our preferred method for new user experimentation, which is obviously great taking away some of the manual efforts of Supplying new users with Akt, fossil hasn't been working for a while because of fraud protection necessities. So it's been a manual process to get users started. But now we have enough resources in sandbox again to Love this. Be our + +Scott Carruthers: Suggested method for experimentation. So I shifted the sandbox documentation from periment Now into the production, Documentation under deployments. I think that's and obviously there's been weekly. There's some requests that come up for minor edits. I'm sure there's been some of that over the last several weeks, as well, but I think those two documentation ads are the only real significant additions. + +Scott Carruthers: That days here. Someone has their hand up. + +Tyler Wright: Yeah, Scott quick question on the sandbox front or is there still a requirement for whitelisted wallet, addresses for folks that are using the sandbox? Sorry if this is common knowledge and I just didn't read + +Scott Carruthers: Yeah, and so We're gonna. Start a gauge. How sandbox is used over the upcoming weeks and months we took the safeguards off those guardrails off of the white listing for now. So no directly answer the question. You don't need to be on the address whitest about to use this sandbox currently. So those guardrails have been removed to remove some of the friction and new users getting started. There's also other safeguards in guardrails that we might need to put into place eventually as time goes on. So the most prominent or obvious one is potentially, if we see some abuse from mining activity and other kinds of activities, we may need to put in policies in place where + +00:10:00 + +Scott Carruthers: workloads that are running for more than 24 hours or 48 hours or whatever. That threshold would be automatically removed in Kubernetes. We haven't seen that kind of abuse of people trying to run long running persistent workloads yet. So we're not putting those guardrails in place on day one, but we may need to if possible, we couldn't reenact the address white listing and the duration of deployment workloads in the future, but we don't find any for those guardrails currently. + +Tyler Wright: Excellent, Scott. Thank you very much. + +Scott Carruthers: Sure. + +Tyler Wright: One other thing I go ahead, Denis. + +Denis Lelic: Sorry was muted one. Quick thought regarding the wallet. I know Kepler has been kind of like our to wallet but I've been hearing a lot of good things about the leap wallet. + +Denis Lelic: Is there, I'm not really sure if it's possible to deploy with it through cloudmose. I haven't tried it. + +Scott Carruthers: Yeah. So Yes,… + +Denis Lelic: Because I don't. + +Scott Carruthers: we would agree that I think people that have used leap wallet find it to be a superior experience. So, I would have to go back and check. I know that the cloud most team was looking at adding leak wallet support. And I think it actually might already be in place or there's a PR in place, that's eminent. + +Denis Lelic: Know. + +Scott Carruthers: So, it's either possible today or will be possible and then your future to use leap wallet and cloud most for deployment purposes. So yeah, we completely agree. We would prefer to I'm altered sleep. Well, + +Denis Lelic: So let's then we would need something like, additional section at the documentation for we were talking about tokens and wallets, Like something for the leap wallet. + +Scott Carruthers: Yeah as soon as it's in place and tested it ready. + +Denis Lelic: Cool. + +Scott Carruthers: Yeah we'll definitely need some documentation around. Leapball is yeah. + +Denis Lelic: Yeah, that's it for my side. + +Tyler Wright: Good call out. good color. + +Tyler Wright: Is there any other documentation from anybody that's working with people in the community or anything else that might need updating or any other documentation? Anybody wants to talk about right now? + +Tyler Wright: Who. again if there's nothing else then I can certainly cut this short to manage folks time from folks that are in the insiders. And vanguards please spread the word that we're certainly interested in folks that want to contribute to documentation. There are Akt rewards available for folks that want to contribute to documentation. So, feel free to reach out to me or feel free to throw a message and sing documentation if you want to help. Again, there are folks in the community are thinking about video guides. So again, if anybody wants to contribute to those conversations or contribute to developing those guys, feel free to drop a message documentation as well. On top of that. Again, Scott mentioned, all the documentation that's going to be updated or excuse me, has already been updated and when + +Tyler Wright: Leap wallet available for folks that will be made available as well. The documentation will be updated as well. Is there anything else? I know that we got a couple of new folks here, we've been talking about some of Scott went over. Some of the changes that have been reflected in the current SIG documentation. We talked at a high level about Scott Carruthers, who's been leading efforts through support and has been doing a line share The documentation over last year has moved more into an engineering role within the Overclock Labs Core team. So we're really hoping that more people from the community want to step up and want to potentially earn Akt, rewards to help, write new documentation update, current documentation or see where again documentation can be improved and help support the documentation is open source. So we've been talking about again, getting more contributions. + +00:15:00 + +Tyler Wright: The community there. And again, we also talked about, there was an effort from the quasarch team. + +Tyler Wright: For many of the special interest groups and the spring and early summer around Docks 2.0 the efforts around the Dock 2.0 which makes improves the user experience around documentation has been passed off to Piyush and his team that are working on the website revamp. So, all that documentation that is now on Docs.com network will be moved to a network slash docs and is being optimized by Piyush and his team. So that again we can continue to optimize the user experience for those that are new and existing users that are trying to do different things from set up providers with ipleases, persistent storage or trying to deploy different kinds of workloads on Again, we have a great community of folks that is live and giving real-time feedback in discord, telegram and elsewhere, but we want to have the documentation, be a resource that people can, start and continue their own journeys. + +Tyler Wright: Something else that's also been talked about is adding videos to the docs for specific items. So maybe their best way of understanding is not through reading but maybe through video tutorials again. There's some folks in the community that are putting together some pitches and putting together, some examples of the kind of video that we want to have live on the documentation and in you and on YouTube, And then finally, again, we talked a little bit about leap wallet, which is something that's coming to the Akash network, it may live right now on cloud most. And once it's been tested by the internal team again, there will be some documentation added to docs out of cashnet.network. That will reflect how to use leapball, how to set that up and how to deploy using the wallet. + +Tyler Wright: Does anybody new or existing to this call? Have any questions or comments about anything documentation related that they want to talk about? + +Tyler Wright: Cool. + +Samuel Walker: Hey I'm new sorry about that. I'm leading you I think a nice thing… + +Tyler Wright: You're? + +Samuel Walker: which you will I am looking and have been kind of working with some of the documentation even to get my own kind of clusters. I've got my own stuff set up this morning on the main thing. + +Samuel Walker: Work meeting that had to do. So I guess based on that, are there developer guidelines related to your method of documenting things, or just kind of add things as any kind of standards have to follow when many these PRS. + +Tyler Wright: It's a great question. Scott. I know you've been leading a lot of efforts. Is there any specific guidelines that you put in place when you're thinking about documentation that we can share with the community? + +Scott Carruthers: I want to really say that for our developer documentation at docs datacos.network, I want to really say that there's any established guidelines other than obviously, you could just look at the structuring and the layout of existing documentation. But no, I want to really say that there's any hard guidelines. So, Just it may be a process where if you submit your first PR for a documentation ad, there may be some back and forth with some suggestions on maybe based on your review of the documentation site. You might pretty much now at the first time if not, maybe there'll be some initial back and forth and then probably going forward will be even easier process. But aside from looking at the documentation examples, on our documentation side, there's really not any additional. Guidelines are schema for our documentation. + +Samuel Walker: And I said, Thank you. + +Scott Carruthers: Okay, sure. + +Tyler Wright: Again, Sam, if you have any other questions, feel free to drop them in SIG, documentation, or if you want to get more involved in writing documentation, feel free to reach out to me. I'm Tyler at Core team or I think you've been working with Andy, but I know there's a number of people in the community that can help point you in the right direction of next steps. + +00:20:00 + +Tyler Wright: Other than that, is there anything else documentation related to anybody wants to discuss at this time? + +Tyler Wright: If not, then again, we can certainly end this call early. We try to be conscious of people's times but a much appreciate everybody for joining and participating. Today we got some clear action items and again Samuel look at those PRS and then hopefully we can get more engaged with you over the next month and talk a little bit more about contributing. Damir. I know that you've talked about other ways in which it contribute. So hopefully we can get contributions on the documentation side, amongst many other things that you all do. + +Tyler Wright: If there's any other updates related to documentation as it retains to the Akash website, we'll make sure that those get dropped in the special interest group for docs So that folks, on this, call in this group, can kind of see the folks that aren't here, can kind of see the updates on what's going on with the Site. And then we can certainly go from there. I think we got someone else joining who also is from the website group as well. But again, if there's nothing else. Hey, Arthur we were about to wrap up this call. We talked about everything documentation related, including some things with the website Is there anything specifically docs related that you want to cover today before we let folks go + +Tyler Wright: Arthur. If you have anything that you want to talk about, that's where they feel free to drop it in discord and we can go from there. But again, much appreciate everyone's time today. yeah, we'll talk certainly between meetings online and please, we'll look out for some more documentation updates when Leapball is available. But again, if anybody has any desire to support documentation, feel free to continue, coming to these meetings, and make yourself known in discord, so that we can talk offline and figure out where documentation updates are needed. And again, put some Akt rewards behind it. But much. Appreciate everyone's time today. Thank you, Sam, for the context on some of the work that you've been doing over the last day or so, again, if anybody has any questions comments about anything, UX related documentation, or otherwise, feel free to continue to drop those in SIG, documentation. We can talk about those during these + +Tyler Wright: meetings every month. Hope everyone has a great day, Appreciate everyone's time. Today. We'll talk online. Thank you very much. + +Scott Carruthers: Thanks everyone. + +Meeting ended after 00:23:13 👋 + diff --git a/sig-documentation/meetings/011-2023-11-28.md b/sig-documentation/meetings/011-2023-11-28.md new file mode 100644 index 00000000..cffe88e2 --- /dev/null +++ b/sig-documentation/meetings/011-2023-11-28.md @@ -0,0 +1,385 @@ +# Akash Network - Docs Special Interest Group - Meeting #11 + +## Agenda +- Update on Documentation. +- Docs 2.0 Effort. +- Community and Support Contributions on Documentation. +- Discussions Video Documentation. + +## Meeting Details +- Date: Tuesday, November, 28 2023 +- Time: 7:00 AM PT (Pacific Time) +- [Recording](https://na7gjhjowrrxc37tzk76rixczxf4st6b3rjpfjrzktiln7yxuckq.arweave.net/aD5knS60Y3Fv88q_6KLizcvJT8HcUvKmOVTQtv8XoJU) +- [Transcript](#transcript) + +## Participants +- Denis Lelic +- Rodrigo Rochin +- Scott Carruthers +- TG (Thomas Greco ) +- Tyler Wright +- Zach Horn + + +## Metting Notes + +### Community Involvement in Documentation +##### Tyler Wright: +- Tyler opened the meeting by emphasizing the purpose of monthly documentation meetings: reviewing new documentation, addressing necessary changes, and discussing documentation handled in the past year. +- Scott has been actively involved in both support and documentation to ensure the shared information aligns with community needs. +- The group aims to broaden the community effort in tackling documentation, encouraging more participation in creating and revising documentation. +- Recent discussions have centered around "Docs 2.0," an initiative to further enhance the structure of documentation. Scott has played a pivotal role in managing this initiative, supported by other team members. +- Tyler shared positive progress, noting contributions from community members, including insiders and vanguards, particularly focused on Leap Wallet documentation. +- Emphasis on ongoing efforts to encourage more contributions from the community. +- Introduction of documentation bounties as an incentive for community members interested in contributing. +- Details to be clarified in the coming week, with a clear explanation provided in the Akash network documentation repository. +- Operational process outlined: Open contributions will be reviewed by the core team for functionality and checked for typos. Approved pull requests (PRs) will be merged, and contributors will receive payouts. +- Tyler emphasized the need to fine-tune the process for clarity, with details to be documented in the repository. +- Planning for the next steps involving key members attending the meeting, who have shown interest in contributing to documentation. +- Aim to collaborate on laying out the specifics and next steps for community involvement. + + +### Discussions on Merging Technical and Developer-Focused Documentation +##### Tyler Wright: +- Tyler provided an update on the website and documentation page, [sharing a link](https://akash-network.vercel.app/docs) to the staging website for the community to review. +- Structural changes discussed in previous Sig Documentation and Docs 2.0 meetings have been implemented by Scott, Luna, and other community members. +- Piyush and his team at Human HQ are actively involved in migrating documentation to the updated URL (akash.network/docs). +- Design decisions for the docs on the website are still pending, and a link to the staging website was shared for participants to review. +- Stakeholders were expected to discuss design decisions during the meeting, but due to their absence, a follow-up conversation will be scheduled. +- Two distinct user experience items discussed: + - Documentation for users interacting with Akash Network (deployment, becoming a provider, validation, etc.). + - Engineering documentation for those building applications and contributing to the core code base. +- Challenge identified in merging technical engineering documentation with user-focused documentation. +- Participants encouraged to brainstorm and share thoughts in the Sig Documentation Discord Channel for follow-up discussions. + + +### Layout of Specific Documentation (Docs 2.0) +##### Tyler Wright: +- Tyler introduced the second point of conversation, focusing on the layout of specific documentation on the website. +- Noted that there was a previous agreement on the structure during Docs 2.0 discussions, but there seems to be differing opinions as the website revamp progresses. +- Described the historical changes: from long continuous pages, to steps and sub-pages, and the potential thought of returning to longer scroll pages with a side menu. +- Raised two user experience items for discussion: + - Long Continuous Scroll: A single long page with steps, using a side menu for navigation. + - Step-by-Step Pages: Each step on a separate page, as currently implemented. + + +### Community and Support Contributions on Documentation +##### Tyler Wright: +- Tyler addressed the importance of community involvement, support, and contributions on the documentation site. +- Emphasized the goal for increased community contributions in 2023 and moving into 2024. +- Operational guidelines for community contributions will be outlined soon, aligning with the new website structure. +- Identified areas for community involvement: + - Review and Improvement: Community members to review current documentation, identify areas for improvement, and suggest changes. + - Additions to Existing Documentation: Opportunities for adding small items to documentation based on user interactions and community needs. + - Creation of New Documents: Community members encouraged to create entirely new documents, such as guides for new wallets or other tools. + +### Discussions on Video Documentation +##### Tyler Wright: +- Tyler discussed the community's desire for video documentation as an alternative learning style. +- Emphasized the goal of creating more video documentation accessible through YouTube, blogs, or the Akash website. +- Called for community involvement in video documentation and suggested dropping suggestions or issues in the Sig Documentation or support repository. +- Introduced the idea of preliminary bounties for specific documentation tasks, especially for areas identified by community members. +- Acknowledged the ongoing effort to determine the bounty structure and costs for different documentation tasks. +- Encouraged community members to provide input on the operational aspects and potential costs associated with documentation efforts. +- Mentioned that Andre, Zach, and himself would review documentation contributions, outlining the need for strict standards. +- Quality standards discussed, including guidelines for high-quality screenshots and specific formatting for code blocks in the new website structure. +- Tyler highlighted the importance of clear and structured documentation due to contributors coming from diverse backgrounds and language proficiencies. +### Incorporating Video Documentation +- TG suggested the idea of having video documentation corresponding to written documentation pages, providing an alternative learning style. +- Tyler and Scott expressed support for the idea, considering video content on the same page as written documentation. +- Scott highlighted historical challenges in storing and organizing different versions of video content. +- The suggestion of including video links within the written documentation was considered a favorable path forward. +- The discussion emphasized the importance of having a cohesive place to store and organize videos, with a potential solution being video links on the documentation site. +- Zach pointed out the significance of having videos in documentation and emphasized the opportunity to build out the Akash YouTube channel as a technical resource. +- Zach outlined the goal of organizing the YouTube channel into sections for different technical topics, creating a comprehensive resource for users. +- Tyler expressed agreement with the goal of building a technical component on the YouTube channel, seeing it as a way to enhance the overall user experience. +- Rodrigo mentioned existing videos by community members, suggesting the addition of a "Tutorials" tab under the "Resources" section for easier access. +- Tyler agreed with Rodrigo's suggestion, emphasizing the need to ensure accessibility and visibility of video content. +- The discussion highlighted the conservative effort to introduce steady bounties for video content, with ongoing fine-tuning of the operational process. + +### Preference for Chatbots and Quick Information Retrieval +- Scott highlighted the importance of considering how people prefer to consume content, acknowledging the shift towards video documentation and the use of tools like Chat GPT. +- Emphasized the significance of quick and easy information retrieval, possibly altering the way documentation is written. +- Scott mentioned the ongoing efforts in creating effective paths for quick and concerted options of the documentation site. +- Discussed the impact of emerging technologies, such as Chat GPT, on the writing and presentation of documentation. +- Zach expressed agreement with the importance of adapting documentation for future consumption methods. +- Tyler emphasized the need for tracking and making adjustments over time, considering the evolving landscape of content consumption. + +### Other Matters Discussed +- TG congratulated the team on the seamless upgrade process, completing the upgrade in under five minutes. +- Tyler expressed gratitude for validator and community support, highlighting ongoing efforts to improve the upgrade process. +- Tyler encouraged participants to think about potential contribution opportunities, considering the impact, time, and preferred methods of contribution. +- Tyler call for feedback in Discord on user experience decisions to finalize documentation for the new website. +- Acknowledged ongoing work to finalize the documentation structure for contributions. + +## Action Items +- Tyler to Clarify details of documentation bounties and update the documentation repository. +- Tyler to arrange a follow-up conversation, potentially on Discord, to discuss the two separate user experience items. +- Group to determine the optimal user experience for distinct sets of documentation. +- Group to continue refining the operational structure for community contributions to documentation. +- Group to continue refining the strategy for incorporating video documentation into key areas of the Akash documentation. + +# **Transcript** + +_This editable transcript was computer generated and might contain errors. People can also change the text after it was created._ + +Tyler Wright: During these documentation monthly meetings the group goes over any new documentation that's been created any documentation that is necessary or any documentation changes. That need to be made previously through much of last year and through the first half of this year a line share. The documentation has been handled by Scott Carruthers who's on this call. He is one of the core Engineers that has had to do a fair amount of Support over time and also documentation to make sure that a lot of again think that we're sharing with the community are working properly. As he is a continued to get more involved in engineering efforts and core code efforts. It's been more of + +Tyler Wright: A goal of this group to have more of a community effort in tackling documentation. So again getting more folks whether they be insiders vanguards or just members of the community that care about writing technical documentation to either again help with new documentation help with revising documentation and figuring out no new ways for us to connect with users that are trying to interact with the cost. Most recently. We've been talking about docs 2.0 his in effort to again continue to improve the structure of the documentation. Has been handled much to this point by Scott with support from other members of the team. + +Tyler Wright: We have got started to get some contributions for members of community including some insiders in vanguards who have contributed to documentation around leap wallet. And again, we're going to continue to look for contributions from the community. There are going to be bounties that are going to be made available for folks that want to contribute to documentation. Added from an operational process because again everything that cost network is open those documentation that documentations will just be reviewed by members of the core team just make sure that their functioning properly and then make sure there's no typos. And then those DRS will get merged and those down people could get paid out. So again, that's something that it will be fine-tuned to make very clear. + +Tyler Wright: Over the next week or so and laid out in the documentation's repo inside the Akash network, but I wanted to get together with some of those key members right here that usually attend these meetings that have shown some interest in getting involved in helping to write documentation to be involved in the process of kind of laying out the next steps. One other thing that was on the agenda for the item that is going to be moved is we were going to be talking about some of the work that's been happening around the websites with the documentation page. I'm going to drop a link to the documentation page inside of the chat for people to look at the staging website as it stands today. what has happened is based upon the structure that has been previously discussed in + +Tyler Wright: sync documentation and docs 2.0 meetings, which you could find here inside the sigdagmentation o. There was been some updates that Scott Luna and other members of the community came together to talk about just ways to improve architectural structure of how the docs are laid out those conversations have happened and again push and his team at human HQ have implemented that structure and our continuing to migrate many of the documentation and much of the documentation from the Dark Side as you say today that Dot Network to updated URL which will be again a network slash docs and you can kind of see again the staging website right here. + +Tyler Wright: There are some design design decisions that still need to be finalized. I was hoping to have some of those design decisions made here today, but because against the stakeholders aren't here today. I'm going to have a follow-up conversation. For those that want to participate in that conversation, we might have that conversation a little bit and Discord between now and the next meeting those two points of conversation are happening around again two separate but very specific user experience items. The first is and again, I'm just gonna talk about these at a high level before we move on with the agenda. first there is a documentation that you see right now that again is reflected in this current state of network and this is + +00:05:00 + +Tyler Wright: Folks that are interacting and using the Akash Network, this is geared for folks that again are deploying. I'm looking to become a provider looking to validate and looking do a number of other things on the notebook. So this is the documentation as you kind of see it today. Scott Carruthers who was on the call has also been working on. Engineering documentation, which is more geared to folks that are looking to build applications on top of Akash are looking to contribute to the core code base and need to understand how Akash works at its deepest technical level. + +Tyler Wright: And so trying to find a way to merge this very technical documentation. That's for an engineering Focus audience with the documentation. That's more focused for developers that are again looking to use the account network is one point of conversation that we're trying to figure out from a user experience standpoint. I know there's a couple of varying opinions on how we should lay out those two very important, but very distinctly different set the documentation. From a technical standpoint the tool Astro allows us to implement both of these specific markdown repos and onto dock site. But again how we lay out that user experience and how people are interacting with the different sets of documentation. It's something that needs to be discussed. + +Tyler Wright: So that's one point of conversation if anybody wants to again think about that in brainstorm a little bit about that. I don't want to go into detail about it now, but we can start to put any thoughts in the sick documentation Discord Channel and then we'll have a follow-up conversation very soon about this. The second point of conversation is around layouts of specific documentation. So as an example. In the current structure of the website. This is something that was agreed upon and docs 2.0 but there seems to be as we move to the website revamp again a little bit of difference of opinion on user experience. + +Tyler Wright: Previously there was a version where the text on the page was very long. And so if you were going down as an example to build a provider, you would just scroll down from step to step to step and it would just be a continuous page scroll. + +Tyler Wright: At some point last year Scott's made a change where he moved everything into steps. And now you just go step by step in each page is a new Step. So again, you just start with step one after you're done with step one and you complete it then to go on to the next step. And so again, that's how the website is kind of structured right now with the steps and kind of sub pages that kind of walk you through how to do specific things on the Akash network. But again with the most recent revamper is the potential thought around just having basically these longer Pages where you just going step by step. And again, you have this side menu on the right hand side, but instead of having specific Pages for each step. it's a longer scroll that you're having to go through. So again, these are just + +Tyler Wright: Are two user experience items that I want folks on this call and folks in the community to? Talk about and think about a little bit more as we approach getting this website live. I know that docs are one of last things that's being worked on and being migrated. And so there's so again some outstanding user experience decisions. Does anyone have any questions? I don't want to go into detail about anyone's opinions about these decisions right now, but does anyone have any questions about The actual user experience items that are up for discussion. + +TG: A show I have one question. By the way, I'm realized I'm signed in this TG. This is Thomas Greco. I'm kind of new here. so the current documentation. + +TG: if it has the developer docs and the main net docs all merge together. Is that correct? Whereas the new documentation it's gonna be split out and focused on people. Just trying to deploy. + +Tyler Wright: So the current documentation as it's built today does not have any engineering documentation in it. It just has everything related to understanding the network technically having to you how to set up wallets how to use wallets how to deploy using Cloud modes how to deploy using the CLI, use of the sandbox and you can kind of see all these steps related to the actual use of the Akash Network. So that's the documentation as it stands today. There is a separate effort that's been done by Scott Carruthers on the core team where he's been developing engineering documentation. We kind of highlighted this in the six support meeting where there are folks that are trying to build. + +00:10:00 + +Tyler Wright: Clients on top of a cost and they need to understand how to set up an engineering environment and how to set up a validators and how to do all these more technical things that allow them to build on top of a cost that documentation is not in the current iteration of the documentation site, but was going to be added to the revamp version as a second set of documentation that more focused towards an engineering audience or again potentially combined with this documentation so that it all webs in one area on one page. That's the user experience decision that's being figured out + +TG: Okay, cool. Thank you for the clarification and + +Tyler Wright: Yeah, no problem. Does anyone else have any questions about kind of the user experience decisions that will finalize at a later time? + +Tyler Wright: awesome All again, one of the other items that we wanted to talk about at a high level is community and support and contributions on the documentation site Frankly as we finish out 2023 and to move into 2024. The goal is for more folks in the community to actively be contributing to developing new documentation and again, + +Tyler Wright: The guidelines for the operational part of how that will be done will be outlined very soon. Once we have that kind of set up with the new website structure but a couple of things that I want to highlight and we talked about this a little bit last meeting is we are looking for folks that one to either take a look at the current documentation. These also folks that we know are in the community active in Discord Telegram and other channels. Dealing with users and if there's any spots that maybe can be improved so that maybe there's language that needs to be added or specific items that the community continues to run into that should be added to documentation. We want to have an area where again people can add small items to documentation. + +Tyler Wright: There's also another bucket that we're looking at where folks can add entirely new documents, whether it be a new wallet is made available and we want to add documentation on how to use that wall and how to implement that while with some of the clients and that might just be a new Wright that's from scratch. that's another bucket of documentation. And then again we talked about this in the last tax monthly meeting maybe the last two monthly meetings. + +Tyler Wright: There's been a desire from folks in the community. You have video documentation where for specific areas. There's maybe a different style in which people learn where they might not respond to reading things off of page but might respond better to seeing it done in video form. And so something that we want to do a lot more of is video documentation that is either made available on YouTube made available via blogs or other A cost website so it's easily accessible for folks that want to interact with it. I know there's some folks on this call that again previously showed interest in supporting writing documentation. + +Tyler Wright: One of the things that we want to do at least in the short term is because we want to see where people want to get involved from an operational standpoint. We would like for folks in the community, I'll call out Rodrigo because I know he's very involved. Roger I'm sure he's seen documentation improvements that he has an idea in the back of his mind or things that he's seen from the community if there's ever an area that you see that hey I want you I think documentation should be added to this page and this section because I'm getting feedback. From in the short term I would just love for people to drop that into Sig documentation or make an issue specifically around that documentation inside the support repo. + +00:15:00 + +Tyler Wright: And then maybe put a preliminary Bounty around it. One thing that we're still trying to work out is how much some of these efforts cost, obviously creating a video from scratch or creating documentation from scratch and having to go through the steps and outline those steps is different than just updating maybe a few lines of copy or just changing some Text so we're trying to figure out the Bounty structure. So we love some help on Broad Jazz an example hey, I want to update this document. I think it will take me about one hour. This is how much and from that we can start to standardize over time what some of these tiers are for different kinds of documentation support. But again, we would love the team's effort and there is some + +Tyler Wright: akt available for folks that want to contribute to documentation. + +Tyler Wright: Does anyone have any initial thoughts questions about anything? I was just talking about in terms of more Community contributions and some of the initial operational structure around that. + +Tyler Wright: cool Again, Andre who's on vacation right now will usually attend these meetings and it'll be a combination of myself Andre and Zach. that'll just be reviewing the documentation as it comes in. There will be some. Again structural items we want to make sure that the screenshots are as high quality as possible and we'll have some specific standards around what quality and what size we're looking for screenshots. They'll be specific examples and guidelines around how you should drop in copy or excuse me our code. + +Tyler Wright: Because again in a new website structure those code blocks will have a button where people can just easily click them and add the code wherever they need it. So they'll be specific guidelines about how things should be formatted and laid out. So those will be coming soon. And again if anybody has any feedback about those as they come out feel free to drop it in either the pr or in Discord and we can talk about it. But we want to have as strict standards on the kinds of contributions because again, we're getting them from a wide array of people where English is not always folks first language and people come from different backgrounds. So we want to make sure that there's as much structure in place as possible. So it leads little to the imagination when folks are writing documentation. + +Tyler Wright: I saw a couple of hands up or maybe there was just thumbs up. Go ahead. + +TG: I might have raised him. so just for example could. some upgrades possibly look like essentially the new documentation just in video format. but what I'm saying is a page goes setting up a specific part of the Akash Network. Good. It's just an idea of an example each page has a corresponding video, for people who? Don't particularly learn well reading or would rather watch video. + +Tyler Wright: Yes, I think that's great again. There's a number of places that I imagine video documentation living one of them being particular on the page where maybe it's on the same page as The written documentation but There's a couple other areas on the website that have already been outlined where Community contributions can go again. It can go on the Akash YouTube channel as well and we can create specific. Channels there but there's a couple of places go ahead Scott. + +Scott Carruthers: Yeah, I actually really like that idea and I had the same thought as So I think historically we've been challenged that when video content is created. There's a number of different versions of it. And there's never been a cohesive place to store these videos. These are all things that are being worked on and we make it there through other vehicles, but they suggestion of including the video actually and the documentation site I think would be and possibly in parallel to this video content existing in other places. I think that would be an excellent path forward. So if you were to go to the provider documentation and we put out a bounty for someone to go through the build of a kubernetes cluster for a cost provider and a very top of that related written documentation we could + +00:20:00 + +Scott Carruthers: Yeah have something in the states if you're more inclined to? Follow technical videos have a link right at the top of it for that. So yeah, I was thinking the same thing and I think eventually that would be a really optimal path, to have that video links actually within the written documentation as well. + +TG: Yeah, cool. I'm not great at I Google meet. So I'm not with the reactions. Everyone's giving hearts. but I would given the hearts and… + +Tyler Wright: Just don't even worry about it. you just + +TG: everything if yeah, don't touch anything. + +Tyler Wright: Yeah, no, you're good. Go ahead Zach. + +Zach Horn: Yeah, yeah lots of Hearts going around. the point on YouTube is important because I think having the videos in documentation is going to be key to the point that everyone's making around that some people are going to have a better time following the written documentation. Some people probably want to watch a video. + +Zach Horn: But ideally and this is something that we've had on the back burner for a long time, but I think this is going to be the opportunity for us to bring into reality is having our YouTube channel built out with a more technical component. So people can be working within the documentation. But ideally they could click through to YouTube and find entire sections of our YouTube channel that have been split out with How would you describe it sections for each technical topic so ideally I see this is a way that we can organize these videos within the documentation but also start to build out our YouTube channel as a technical resource. We just haven't had the technical capability up to this point to really produce that video content, but that's one high level goal that I've had for a long time that I think this could dovetail nicely with what we're talking about here. + +Tyler Wright: Absolutely. + +TG: Yeah. Yeah I agreed. he's gonna say it seems like there's endless. + +Tyler Wright: So again from a I'll go ahead Tom. + +TG: Areas that kind of need documenting and it's only going to continue kind of growing. with the network For having to sort of strip probably is definitely gonna be really important. + +Tyler Wright: Absolutely. + +Zach Horn: Yeah agreed. + +TG: So people can + +Tyler Wright: Yeah. + +Zach Horn: Most definitely one point that I've been thinking about a bit that I'd be curious to hear what the rest of the broader Community thanks is if we had to shortlist places within the documentation that we want to prioritize for video content. Where were those places partially it's obvious in some ways where you could do, getting started but the deployment setting up a provider and going through those steps like there are places that make more sense than others, but I'd be curious if there's a hot button place that the community is seeing lots of people asking for more documentation or clarification that we get prioritize if we're going to start somewhere with these videos. + +Tyler Wright: rodri I know that you're very active besides just again doing your first deployment videos and setting up a provider either with the prador tool or with Helm do you see any other areas that folks should focus on if they're thinking about a video documentation. + +Rodrigo Rochin: nothing that comes to mind right now from what I've seen recently in this group of mostly people asking about some mining stuff and providers and adjusting as the health, but that's not in the Ducks. So + +Zach Horn: That's actually a good point because one of the things that recently happened was we had a large influx of Zach miners Zephyr. I don't know too much about Zephyr. So I can't speak one way or another about what the project is, but I do know that we have lots of people that were interested in doing that coming into the network and spinning up deployments to do proof of work mining for zapper. + +Zach Horn: maybe that's something that lives in the documentation at some point the feature. Maybe it's not, I'm here nor there on that. But one thing that did come to mind is Rodrigo's point. Is that on social some people not even really affiliated with the Akash Community all that much made videos of how to deploy a Zep Miner on Akash, and those did really really well both with people in the Zep community and people within Akash saying wow, this is great that we have these walkthrough videos of exactly how to go through Cloud most and how to set up the deployment and how to customize it and all that so, that's one place and it doesn't have to be as ever obviously but It's clear that there are definitely areas within how to interface with Akash where people want really step by step instructions of how to set up deployments. + +00:25:00 + +Tyler Wright: I think that's good. + +TG: Yeah, I carry agree with all that I mean quickly and being so I'm heavily embedded in the agoric community and they're really interested In kind of getting a better understanding of how to deploy, that node on a cash and then even is something like a front end, Just like a web application like I see interest there in weekly meetings. + +Zach Horn: Yeah, the front ends are something that we've been talking about for a really long time, but think that's almost. I don't want to say low hanging fruit in a bad way. But like I do I do think that deploying front ends is really the better way to say would be an easy touch point for people to start using a caution get used to what a dependent feels like on So I think that's great. I might even be worth a conversation directly with a goric to see how we can help them get up and running but more broadly front ends are a great first touch point for people who want to get started at the point. + +TG: Yeah, I definitely don't speak. Or to so let me take there. + +Zach Horn: For sure. + +TG: I think there's some limitations in just deploying a front end. I don't want to go up on a tangent and this specific topic but I think that there's some value in having to go a little bit deeper and an sdl file. Or using the STL language then just grabbing a front end image. heading to + +Zach Horn: Yeah. most definitely agreed + +Tyler Wright: Scott correctly… + +Rodrigo Rochin: that + +Tyler Wright: if I'm wrong, but I think we could also just besides all the videos that have been talked about and suggested. even technical content that might be video based around specific topics like the what a provider is and maybe even how they are conscient network works, would be something that I think some people even technical folks don't truly understand all the way. And so if we had some content that a lot of people like, all right, what it actually makes sense. This is what actually is then it can help in their development process or whatever the case may be, but that was just something I was thinking about as you all were talking. + +Scott Carruthers: yeah, I definitely think that there's a place for some Akash architecture or topology videos, that would be useful I think that we've attempted that before and a lot of times are they being produced with? some more guidelines and where did these videos exist so I know that we'll get there and again this goes back to I'm sure there will develop other. Frameworks and hosting strategies for this or Zach talked about the YouTube channel and if that's formatted then it can be conducive to this. But I also again you could just really go down the documentation site and + +Scott Carruthers: create videos including overviews and then deeper technical depth content. I mean Google or just go through the documentation site and create a video on almost every talk. I found the documentation site and then have a link to that within the documentation site, I think would work really well as far as Deploying the front end on I think there's also been some attempts at doing those kind of videos. So there's different perspectives and different angles that you take on this, but if I think they biggest friction point for people deploying front ends on Akash is maybe not necessarily the deployment on Akash that that might be the easy part. It's having the front end exist in a containerized image and so walking through that, but I know that we have some very capable. + +00:30:00 + +Scott Carruthers: people within the community that could produce a 30 minute video on taking a react app containerizing it which is not overly complicated process and they could pretty much just be copy and pasting of a Docker file to get there and then hosting on a public repository. So I think that's probably where the most friction is and creating web front ends. But I definitely think we could create some very useful video documentation around that and then again, it's just a matter of ensuring that people are able to find it far easier than they've been able to historically + +Tyler Wright: Scott I think that's a great call out. Go ahead Roger. + +Rodrigo Rochin: yeah, and agree with what Scott and everyone says you said, there's actually quite a few videos or invites already. For example chimpa here from Arrow plots has a few weekdays, but creating a validator with Cosmos apnigos and stuff, but it's hard to find them in and they're not in the Box what I see in other documentation and projects. Sometimes it's for example that the bottom of our current talks and the resources tap other resources that Right under there, there could be a tap that needs to tutorials. For there's another what are these called subtitles? That's a tutorials title and then it leads to either. videos or written guide + +Rodrigo Rochin: And we could maybe add those Under a tab make it easier for everyone to find it. + +Tyler Wright: I think that's a great suggestion Roger. + +Tyler Wright: Yeah. Absolutely. + +Tyler Wright: So I think we're on the grill about the importance and value of video content as a part of this documentation strategy, especially if we move to 2024 one thing that I want to emphasize is there's going to be a conservative effort. And again, we're fine-tuning it right now to make sure that there are steady bounties available in the operational + +Tyler Wright: is today I just needed myself is optimized because one thing that we want to do is + +Tyler Wright: make sure that the docs is a community effort and it's not something that is Reliant specifically on members or Really Scott on the overclock Labs core team something that we've certainly trying to get him to pass on to other members of the community for a while. And this is something that we think that the community is able to handle because again, there's such great support that's given inside Discord when folks have any issues. So hopefully people will be proactive and kind of looking at documentation and seeing how they can get involved. And then again, we'll make sure that the battery structure is fair and paid out accordingly and as officially as possible, I think Huey does a great job of doing that to this point, but we'll continue to be focused on that and that folks aren't contributing. + +Tyler Wright: To the degree that I'm going to start to reach out to folks in the community and just ask them to see if they're still interested because again a number of I think nine people are so interest whether it be public or privately to help contribute to writing documentation. Some are focused on the provider, but many just want to contribute to writing and contribute to documentation. So as we move into 2024, I'm really going to be relying on those folks, too. + +Tyler Wright: Join this monthly meeting when they can if we need to find a better time. I'm happy to find a better time. But I would like this special interest group around docs to be a community run effort around making sure that documentation is optimized because again, that's one thing that we've gotten a lot of phrase about in the past as the Akash Network gets grown is that the docs are easy to understand and it's easy for people to onboard themselves. And then when they have issues with the docs, there's great support from inside of the vanguards. And so it's a network continues to grow and continues to expand new audiences and more audiences whether they be web to focus. It's really going to be important for the documentation to stay up to date with all the new features coming and all the new things happening on the network, but also serve it to people in a way that they can easily digest it and feel like they can use the network. + +00:35:00 + +Tyler Wright: pretty quickly that makes sense that low head talk. I just gave so as next steps from an operational standpoint, I I know that we'll start moving towards. + +Tyler Wright: Getting the YouTube together and they're making talk about that in future meetings again. There will be some guidelines. I'll be shared and Discord around contributing to documentation, but I would love for folks to start to look at the documentation as it is today and start to think of ways that can contribute. I think that what not. We will wait until after the website we did website to start making documentation changes so that everything is in the upset new repo in the migration isn't affected and that is planned for December 15th. But in over the next couple of weeks, we'll just again assign work and start the process go ahead Scott. + +Scott Carruthers: I just might be a worth a quick match in that so as we accept and discuss this notion of how people consume content and their preferred method to consume contents along with possibly. some individuals preferring video documentation over written documentation. I also think that we live in a time that people want to be able to get information from my chat GPT and tools like that instead of having to scour throughout volumes of documentation as well. So I think that will be interesting as well. when we think about this in totality that Zach. I know that + +Scott Carruthers: obviously you I worked on some efforts in the past on this that we've now gone in different directions just based on time investment, but I think if the community hasn't heard that it's important to note as well. So I think we're very focused with how people like to consume content today. So along with our video documentation. I think we're going to have very effective pass to allow. Very quick and very concerted scrubs of our documentation site in the future. I also think it's interesting when you start to think about that deeper and we start to talk about Community contributions to our documentation site. Maybe there isn't much to this or maybe there is but it'll be interest when I was focused on creating chatbots for our documentation site. I started to think that + +Scott Carruthers: Theoretically maybe it even Alters to some degree how you're writing documentation. when you're having your eye I'm like if we have chatbots out there that are going to consume this information and it may be presented in that format either primarily or always had a pretty high volume, do you alter so I was starting to think about if we were having a chat GPT type of experience for a cock documentation as I'm writing documentation. Do I want to massage it in any way that + +Scott Carruthers: knowing that a lot of information is going to be consumed enough format. So maybe that alters documentation right in significantly or maybe a dozen but the overall point being as we start to think about our next generation of content consumption. I think that's along with video content going to be very key as well. And I just want to briefly mention that in case people in the community weren't aware that were very rapidly heading down that path as well. + +Tyler Wright: I love that's about that. + +Zach Horn: Couldn't agree with that more. That's Everything that's happening with material augmented generation and all this next Generation language model retrieval. That happens when you're querying these models I've been thinking about this non-stop. it's all very down the line because this stuff is both evolving really quickly and also there's lots of work going into to your point how documentation is written today to think about how it's going to be accessed in the future. But yes, that's very top of mind. I'm glad you brought it up. + +Tyler Wright: so as we continue to meet month over month, this is something certainly that we can track and make adjustments whether it be to the guidelines to the structure to make sure that we're optimizing for however people receive documentation. I know that there's been some main that's nine. + +00:40:00 + +Tyler Wright: Documentation that's been written again. Shout out to Scott who has been leading those efforts again as we continue to move forward some of the documentation that's consistent is just, structurally kind of templated there and I just swapping out information and so some of those efforts will again, but made that It's a documentation and the midnight nine Akash May 9 upgrade happened this morning. And was successful, but that documentation Is there any other documentation that's new or does anyone have any specific question about any existing documentation that they want to talk about? During the special interest group. + +Scott Carruthers: Yeah, I think from my part really the only documentation of significance over the last. Month has been around a couple of different main net upgrades. I think there's been some small tweaks and adjustments to other documentation. But as far as Introduction of new documentation. I think that's been it. + +Tyler Wright: Okay. + +Tyler Wright: And the only thing I would say is there are some folks. Hopefully not that many but Roger just something to track in the community that eight documentation was on the sidebar but has been moved to other resources. So if there's anybody in the provider side that's still has an upgraded they're provider than they probably will have to go to this provider documentation here and then make sure that they're using Again, the most recent version of the node to go with it. So that documentation has just been moved just for as to not confuse folks as they were upgrading this morning. + +Tyler Wright: But yeah, does anyone else have any other questions comments about anything or any discussion topics and he wants to bring up right now? + +TG: yeah, my Firefox just restarted. So sorry for dropping there. I did just want to comment. And kind of congratulate you guys on that upgrade being so seamless. + +TG: under five minutes. It's pretty significant. So take really quick impressive. + +Tyler Wright: Thank you. And I know that again one of the many things that Scott is working on is continuing to improve that process both in the testing of upgrades prior to upgrade going live and we're continuing to improve operational process. So the last few upgrades had been very good and we want to continue to improve that process because there's a lot of new features coming so really appreciate the validators and people in the community. They're supporting for their help. So thank you all. + +Tyler Wright: I know we have about 13 minutes left, but I don't want to keep you all again. We've talked at a high level about some of the user experience topics of discussion as it pertains to the revamped dock site, if you have any feedback on either of those Please leave that feedback and Discord. We'll look to have a follow-up meeting. If not, Thursday some other time. I'm trying to work on some Logistics with some key stakeholders, but we want to finalize the docs for the new website as soon as possible. + +Tyler Wright: and make those user experience decisions one way or the other as soon as possible. So looking for feedback from the community hopefully during this call or right after this call and then I'll make this recording available as soon as possible. So that folks can have the next day or so to hear what's going on and get some feedback in addition to that. We talked about continued desire for contributions both in written documentation and video documentation and some strategies there. I'm looking for and hoping that folks on this call and elsewhere. We'll start to look where they can provide some impact start to think about what's kind of time May cost in akt and then either again send messages in the Discord Channel or would prefer in the state documentation Discord Channel, but we can also don't privately as we continue to work out what this like. + +00:45:00 + +Tyler Wright: me structure for documentation contributions could look like but hoping that folks can start to think about how they can contribute and we can start to throw akt to folks that want to contribute to continuing to make the documentation reliable and quality for all types of users. So + +Tyler Wright: Go ahead Scott. + +Tyler Wright: you I think Okay. + +Scott Carruthers: I don't have my hand. No. + +Tyler Wright: Sorry about me. you did have your hand out. That is a good point. + +Scott Carruthers: I'm I actually was going now so do I get bounties as I write documentation as well? + +Tyler Wright: Yeah, and retroactively I'm not sure about yeah, yes papa figure out… + +Scott Carruthers: Richard retroactively would be right. + +Tyler Wright: what their rate is, maybe it's like 25 akt her documentation section, not just + +Scott Carruthers: 25 ak2 + +Tyler Wright: But yeah, think about how we're going to incorporate the engineering documentation with a cost documentation. And then again the structure of how things are laid out on the page and we'll have those continuous discussions offline. And please figure out how you would like to contribute Scott is moving away from documentation. So he won't even have time to contribute hopefully, but for other folks that want to get more involved in documentation writing we're looking for more support as a community so much appreciate you all in advance. Zach roderie Scott is anything else? You'll want to say before we head out of here. + +Scott Carruthers: I guess just to put on the record in case anyone is listening to the recording or if you guys have any thoughts and maybe not today but as you think about it more so I've heard that and I think these are outside of discussions. I was part of making where they developer documentation is going to live and possibly making it directly in categories off of the Akash documentation site and maybe even the suggestion of doing it under validators specifically. so that documentation would cover + +Scott Carruthers: they Provider Services the node Repository. And probably eventually they Akash API repository as well. So I want to Make sense to have all that documentation under It could make sense to. Have the developer documentation split up into a validator. and node documentation under the validators category and they developer documentation for Provider Services Under the providers category, but just something to think about because again I've heard possibly in some other conversations there were some thoughts about that. So just keep that in mind if we were thinking about putting the developer documentation. directly on a network backslash Docs + +Scott Carruthers: we would have just think about the structuring a little bit more. I don't think it's complicated. Like I said, maybe it's just splitting it up between validator and provider, but that's it still a little bit work to make that happen. + +Tyler Wright: Of Roger I said, I know that you're off me to want to say anything before we head out of here. Don't feel obliged. + +Rodrigo Rochin: How good they're ready to help out. + +Tyler Wright: looking forward and Thank you for joining today. Feel free to you don't have to do it today. But if you hope that you continue to join these meetings and stay involved and we continue to hope to get to know you more. We don't like to tax people here. So as you get more comfortable with the group you can Say However, you want to say hello and we respect all lifestyles of privacy and otherwise + +TG: Yeah. + +TG: Yeah, for I mean. Yeah, I think I introduced myself as Thomas Greco Tom Greco and my Gmail is just signed into not my work. Yeah Gmail or else you've seen my name? But I did want to just say yeah. Thanks for today. And it was a great experience. + +TG: just having this call and it's clear as to why really a cautious documentation and just all of the resources that I currently provided to the users developers validators is because all the hard work you guys are putting in so that's + +00:50:00 + +Tyler Wright: Much appreciate it's a great community. So we hope to have you get more involved and can help us get where we want to go. Anyway, steering committee has been moved from this week to next week. Just because some key stakeholders will be out this week and we'll have one meeting in December for the steering committee and then have another meeting. That's usually at the end of December move to early January just like kick off 2024, but that has already been adjusted in the calendar. But again much appreciate everyone's time much appreciate those. That are going to get more involved. And again, I'll make the notes and the video available as quickly as possible so that we can get some more feedback and contributions but much appreciate you all. Hope everyone has a great rest of their day. Thank you. + +Scott Carruthers: Thanks, everyone. + +Zach Horn: Thanks guys. + +TG: against + +Rodrigo Rochin: Thank you. + +Meeting ended after 00:51:19 👋 + diff --git a/sig-providers/meetings/010-2023-10-25.md b/sig-providers/meetings/010-2023-10-25.md index c6ca0ddb..63e11c40 100644 --- a/sig-providers/meetings/010-2023-10-25.md +++ b/sig-providers/meetings/010-2023-10-25.md @@ -1,21 +1,19 @@ # Akash Network - Providers Special Interest Group (SIG) - Meeting #10 ## Agenda - +- Presentation on Auditing providers tool +- Discussions on Content Moderation. - Follow up discussion on GPU Provider Setup. - Update from Praetor on all of the work that they have been doing. - Open Discussion on all things related to Akash Providers. - ## Meeting Details - - Date: Wednesday, October 25th, 2023 - Time: 08:00 AM PT (Pacific Time) - [Recording](https://2aefpzwgiwj6jzkl5fdsn7us3pjprpnpkoqqrrsu6bjaukktnxya.arweave.net/0AhX5sZFk-TlS-lHJv6S29L4va9ToQjGVPBSCilTbfA) - [Transcript](#transcript) ## Participants - - Andrey Arapov - Benjamin B - Byan @@ -29,32 +27,65 @@ - Tyler Wright - Zach Ross - - - -## Notes - - -- Benjamin shared some information on a provider auditing tool that he and his brother submitted for the Akash-a-thon. -- Benjamin shared some strategies that he created which are easy to introduce to price scripts. ould be worth looking into deval: https://github.com/figurestudios/designing-price-script-guide. -- Sam Walker asked where the tool will be hosted. Almost everything will be powered by Akash. -- Sam Walker mentioned an issue that he found https://github.com/akash-network/support/issues/137. Tyler mentioned that this issue was talked about during sig-support biweekly meeting #20. -- Deval gave an update on Content moderation. -- Wallet addresses can be blocked. Deval showed a demo. -- Shimpa asked what would happen if the naming was being changed. -- Zach mentioned that he has been using Andrew Mello's chaperone OS tool for a couple of weeks. -- Andrey mentioned Praetor's solution will be the first line defense to filter out the bad images so the provider won't bid. Chaperone service is a deeper solution. -- Samuel mentioned some of his kubernetes experience. -- The group talked about Andrew Mello's chaperone tool: https://github.com/cryptoandcoffee/akashos/blob/main/chaperone.py . -- Samuel mentioned some tools they are using including https://kyverno.io/ and https://www.openpolicyagent.org/ . - -### Action Items: - +## Meeting Notes +- Tyler mentioned the community pool grant awarded to the Praetor team for their work on tools for aspiring providers. +- Tyler Acknowledged the progress made by the Praetor team, including basic functionality and work on content moderation and API improvements. + +### Benjamin's Presentation on Auditing Providers +- Benjamin described a proof of concept created for automatically tracking and benchmarking providers. +- Their goal is to create an auditor tool that assesses providers on different levels based on factors like uptime and reliability. +- Benjamin suggested a tiered signing approach, where providers meeting certain criteria would receive different ratings. +- Mentioned the collection of historic data and its relationship with the concept. +- Benjamin discussed the hosting of most services on Akash and noted that the database could also be run on Akash. +- Tyler Wright encouraged participants to [view the YouTube](https://www.youtube.com/watch?v=jg90U1£82uU) video shared in the chat and provide feedback in the "providers" channel on discord. + +### Demo from Praetor(Content Moderation Solution) +- Deval began to present the content moderation solutions, starting with wallet address blocking and demonstrated the use of a modified Provider service through the deploy tool from cloudmos. +- Deval demonstrated content moderation solutions, including wallet address blocking and Image URL blocking. +- Showed how a blocked wallet address prevents deployment and mentioned the management API, which will allow providers to close leases themselves. +- Presented Image blocking, demonstrating the blocking of URLs containing specific domain names. +- Explained that successful deployment requires whitelisted wallet addresses, whitelisted images, and no use of blocked domains. +- Showed a successful deployment of a game and played the game on the provider's side. +- Mentioned plans to make the system more dynamic and allow block and disabled items to be enabled from Praetor app itself. +- Discussed the upcoming implementation of the management API and plans to release an updated version of the provider service. +- Andrey inquired about whether the provider code was modified and suggested submitting pull requests upstream. +- Deval Patel: Confirmed that they would submit pull requests once the dynamic codes and blocklist code were satisfactorily completed. +- Damir raised a question about what happens if someone clones an Image and renames it, suggesting that the image might still run. +- Andrey shared an experience of trying to run a miner and having the process killed, indicating that some systems can be employed to detect and address such issues. +- Deval explained that the management API would allow providers to inspect the content of images and potentially close them. +- Zach mentioned that the Chaperone service can block specific processes or look for specific file types. [Shared a link](https://github.com/cryptoandcoffee/akashos/blob/main/chaperone.py) related to this. +- Tyler mentioned that there is an issue in the Akash project roadmap related to content moderation. +- Tyler encouraged Deval to update that issue with the details mentioned during the meeting. +### Other Matters Discuused +- Andrey advised participants to follow announcements from the provider announcement channel in Discord. +- Andrey encouraged providers to report issues in the "providers" channel or directly to him. +- Tyler Mentioned the "support" special interest group that addresses open support tickets related to the core product. +- Tyler discussed issue [number 137](https://github.com/akash-network/support/issues/137), indicating it might be a known issue, and mentioned potential tooling to address it. Offered to discuss the matter further with Samuel after the meeting. +#### - Discussion on Security and Container User Privileges +- Zach discussed pod security standards and the fact that Akash deployments run containers as the root user, which raised security concerns. +- Zach Inquired about the possibility of creating a separate Akash user for container deployments. +- Andrey responded that blocking the root user for user deployments and specifying a non-root user in Docker images would require deeper consideration and a feature request. +- Andrey mentioned remapping user IDs as another option. Suggested starting a discussion in the Akash repository. +- Tyler suggested that Zach drop a discussion on the topic of user permissions and default user settings in the Akash Repository. Mentioned the upcoming steering committee meeting where this could be discussed further. +- Zach Expressed willingness to join the steering committee meeting tomorrow and contribute to the discussion. +- Samuel Shared his experience with [Kyverno](https://kyverno.io/) and Open Policy Agent in the context of enforcing security policies in Kubernetes clusters. +- Smauel mentioned that Kyverno can be used to prevent deployments that don't meet specific security criteria. +#### - Discussion on Notifying Users About Rejected Images +- Samuel asked about the process for notifying users in advance about rejected images due to security policies. +- Andrey suggested that this topic deserves further discussion and mentioned leveraging provider attributes to notify users about rejected images. +- Benjamin mentioned that it's not possible to send information back to users whose deployments were rejected +- Benjamin suggested a solution of saving and encrypting logs in a way that only the tenants can decrypt. +- Deval explained that the error messages are given during deployment, but the problem may arise when users don't check the logs or ignore the pop-up messages +- Deval Discussed the need to also handle deployment history and rejections on the client side. Proposed discussing this with the client team to find a suitable solution. +## Action Items: +- Zach Ross will create a discussion in the Akash Repository about user permissions and default user settings. +- Group to explore methods for providing users with better feedback when their deployments are rejected. - Group will continue to monitor the content moderation work over the next month. - Ben and His brother will share market research and open up discussion on audit tools. +- Deval to update Content modeartion Roadmap on Github - Chaperone tool will continue to be worked on by Andrew Mello. -# **Transcript** +## **Transcript** _This editable transcript was computer generated and might contain errors. People can also change the text after it was created._ diff --git a/sig-support/README.md b/sig-support/README.md index b0e4cbcd..c19a7d7c 100644 --- a/sig-support/README.md +++ b/sig-support/README.md @@ -35,9 +35,9 @@ sig-support is responsible for defining mechanics of how support works at Akash | #17 | Wed, September 13, 2023 07:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-support/meetings/017-2023-09-13.md) |[Link](https://github.com/akash-network/community/blob/main/sig-support/meetings/017-2023-09-13.md#transcript) |[Link](https://xq6srn6ahx4vqkqnzhre5fw2vxfxuzroz2avfkvagkimxe5e7uba.arweave.net/vD0ot8A9-VgqDcniTpbarct6Zi7OgVKqoDKQy5Ok_QI) | #18 | Wed, September 27, 2023 07:00 AM PT (Pacific Time) | | | | #19 | Wed, October 11, 2023 07:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-support/meetings/019-2023-10-11.md) |[Link](https://github.com/akash-network/community/blob/main/sig-support/meetings/019-2023-10-11.md#transcript) |[Link](https://4bnijv3wt46kxmijhgq67y4tjt55h36c3yz7ubtakslbdyjord2q.arweave.net/4FqE13afPKuxCTmh7-OTTPvT78LeM_oGYFSWEeEuiPU) -| #20 | Wed, October 25, 2023 07:00 AM PT (Pacific Time) | | | -| #21 | Wed, November 08, 2023 07:00 AM PT (Pacific Time) | | | -| #22 | Wed, November 22, 2023 07:00 AM PT (Pacific Time) | | | +| #20 | Wed, October 25, 2023 07:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-support/meetings/020-2023-10-25.md) |[Link](https://github.com/akash-network/community/blob/main/sig-support/meetings/020-2023-10-25.md#transcript) |[Link](https://tiycqjxd7fzfrflpcqvbtv6urvk4vtbljtwr7kfpebsrd2p7hhvq.arweave.net/mjAoJuP5cliVbxQqGdfUjVXKzCtM7R-oryBlEen_Oes) +| #21 | Wed, November 08, 2023 07:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-support/meetings/021-2023-11-08.md) |[Link](https://github.com/akash-network/community/blob/main/sig-support/meetings/021-2023-11-08.md#transcript) |[Link](https://tiycqjxd7fzfrflpcqvbtv6urvk4vtbljtwr7kfpebsrd2p7hhvq.arweave.net/mjAoJuP5cliVbxQqGdfUjVXKzCtM7R-oryBlEen_Oes) +| #22 | Wed, November 22, 2023 07:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-support/meetings/022-2023-11-22.md) |[Link](https://github.com/akash-network/community/blob/main/sig-support/meetings/022-2023-11-22.md#transcript) |[Link](https://l5yeilkhvwmpqetchbk2pax4nxmu6miv23cxy7iszl7nvgbk4lka.arweave.net/X3BELUetmPgSYjhVp4L8bdlPMRXWxXx9Esr-2pgq4tQ) | #23 | Wed, December 06, 2023 07:00 AM PT (Pacific Time) | | | | #24 | Wed, December 20, 2023 07:00 AM PT (Pacific Time) | | | | #25 | Wed, January 03, 2024 07:00 AM PT (Pacific Time) | | | diff --git a/sig-support/meetings/021-2023-11-08.md b/sig-support/meetings/021-2023-11-08.md new file mode 100644 index 00000000..a9cf1988 --- /dev/null +++ b/sig-support/meetings/021-2023-11-08.md @@ -0,0 +1,286 @@ +# Akash Network - Support Special Interest Group (SIG) - Meeting #21 + +## Agenda + +- Participants will look at issues in [Akash Support Repo](https://github.com/akash-network/support/issues). +- Artur will lead triaging issues, and discussion of implementation for issue fixes. +- Artur and Anil will lead discussion putting severity on issues. +- Scott will discuss Support from the community and ask for any community feedback. +- Participants can have an open discussion of any other issues or support related items on Akash Network. + +## Meeting Details + +- Date: Wednesday, November 8th, 2023 +- Time: 07:00 AM PT (Pacific Time) +- [Recording](https://tiycqjxd7fzfrflpcqvbtv6urvk4vtbljtwr7kfpebsrd2p7hhvq.arweave.net/mjAoJuP5cliVbxQqGdfUjVXKzCtM7R-oryBlEen_Oes) +- [Transcript](#transcript) + +# Participants + +- Andrey Arapov +- Benjamin B +- George Pro +- Julius Haus +- Max +- Scott Carruthers +- Tyler Wright + + + +# Notes + +- Scott led the group through the issues awaiting triage in the support repo. +- Scott talked about [issue 137](https://github.com/akash-network/support/issues/137). Scott tried to reproduce this issue when it first came up with DCNorse. Another user found the issue more recently. +- Scott will assign to Andy. Andy has not seen this issue, but he will try to reproduce this issue. This issue is marked Sev2. +- Scott talked about issue 139. The default order https://github.com/akash-network/support/issues/139. Andy made a work around for it, and shared in Discord. This is marked P2 right now. +- This issue is assigned to Artur right now, and more research will be done later. +- Scott and Tyler talked about MaxUnit limits. This is issue 140. The limits will be raised again today. +- Scott and Benjamin talked about how the limits were signifanctly lower in the past. They were raised last year. +- Benjamin agrees the limits should be raised, but asked a question about resource allocation. Scott mentioned that there are internal discussions. Concerns are known, and the internal team is thinking it through. + + + +## Support + +- ZJ had an issue with a provider. The provider crashed because of an SDL. ZJ will share the SDL. +- Benjamin and the group talked about ways to improve process for govenerance proposals. + + +## Action Items + +- Improve process for governance proposals. +- Artur to look at [issue 139](https://github.com/akash-network/support/issues/139). + + +# **Transcript** + +_This editable transcript was computer generated and might contain errors. People can also change the text after it was created._ + +Tyler Wright: Arm around this time. If anybody has any conflict with this time, please feel free to let me know we've talked about this in the Akash insiders group as well as the number of other meetings. Thank you to all the Insiders that are here. We are looking for more participation from insiders because again many of the Insiders are involved in + +Tyler Wright: Forward it can help figure out, some of the lurking issues some of the big issues or can talk about any of the issues and the Usually Archer walks us through the support repo. But today we have another member of the core engineering team Scott who will be leading us through any issues that need to be triaged if anybody has any questions about any open issues whether they're new issues or waiting for us or whether they're existing issues that you want to update on. Please feel free to put a message in a chat or raise your hand at that time. And then after that the next part of the agenda is I'll be asking folks on this call. I see Andre Julius Ben and Max who are oftentimes working with members of the community in Discord and other channels and I'm just want to get a sense of is there any themes that you all see in terms of ways that we can maybe improved documentation and prove process? + +Tyler Wright: Improve anything on the support side to make it more streamlined for new and existing users. So without further Ado. I'll hand it over to Scott. + +Tyler Wright: You can talk about that later today because I have strong thoughts about that. But let's go through the triaging of issues first and then be able to go from there. So without further do I hand over to Scott and I'll just be taking notes in the background. + +Scott Carruthers: Thanks as I look at the issues that have been created and the ones that have come up since our last session. I believe there's only a couple of unassigned. So I think this can be pretty quick and then we can get into some open discussion. so to go through two issues that have come up and in terms since our last meeting I'll start with. it's titled issues with the cost provider Miss bigger worker node. Perhaps I was actually looking at this prior to the call and as we could see we have a reference to DC Norse who I've actually had conversation. He wasn't the individual that opened this issue. He had a similar issue and this was I probably say eight weeks ago something like that where for some reason the + +Scott Carruthers: a worker node and a provider kubernetes cluster is erroneously representing a very high number of GPU quantity. So obviously extremely large one good thing about this is some of the sanity checks that called most team runs in their analytics and actually when this breaches upper threshold for quantity and basically when we hit this before + +Scott Carruthers: A cloud most was not reporting this within analytics. So obviously we could do a very drastic Miss representation of how many gpus are on the network if we actually reported this number, but again, thankfully there are some safeguards in place in Cloud motion others of this breaches a per threshold and it wouldn't have that impact. when this first came up Again, many weeks ago. I tried to reproduce this issue and was unable to their initially thought that it was mislabeling of a node which really shouldn't have any impact on inventory and reporting of resources, but I tried to do anything that I could possibly think of to reproduce this issue and was unable to when this first came up with DC Norris and I believe there's some conversation about this in the issues as well. He thought that + +Scott Carruthers: possibly the way to reproduce it was removing a GPU card from a running server. So after I got through pretty exhaustive testing DC North throughout that hypothesis and I didn't have the ability to test that because the host that I test GPU providers on our Cloud instances, and Lambda Labs other lab instances, and obviously I don't have the ability to remove a GPU card from a running server host in that scenario. So that's a lot of the backstory and a lot of further description in the issue. + +00:05:00 + +Scott Carruthers: Andy, I was wondering as I was looking through this morning. Would you like me to assign in first of all, I'm wondering if you've had any conversation with DC Norse in these regards and in the second. Would you like me to assign this to you initially and you can have some conversation with DC Norse and see obviously to Most likely if we want to review this from a code level we need to be able to reproduce the issues and I was unable to do that. Would you like to take a look at this and see if you have any Ability or able to isolate a means of reproducing this issue. + +Andrey Arapov: Yeah, yeah. No problem. I have never seen this issues of myself and I've been playing with GPS quite extensively and I was disabling enabling and plug-in stopping and renabling and stuff. I haven't been able to reproduce it. But I'll try to focus more on my video. I'll do this. I know but we'll try. + +Scott Carruthers: Before either across dozens of GPU providers that I've set up and was completely unable to reproduce the issue. But I'll sign you and maybe through some conversation with DC Norse and some further investigation we can Try to reproduce. + +Andrey Arapov: Okay, it's all good. + +Tyler Wright: Are you marking it? P2 or anything like that. I see Pete except you got your attention. + +Scott Carruthers: but yeah. + +Tyler Wright: Thank you. + +Scott Carruthers: and then the second and last issue is one that Andy identified says five days ago so mid last week and Andy out let you jump into if you'd like to describe this but essentially Andy detailed this and in great detail, and essentially it's if a deployment as created with a array or a list of different GPU models the bid will choose the last element in the array or in the list and the sdl and we'll + +Scott Carruthers: bid on that and obviously if it doesn't have that type of GPU model. So again Andy goes through and describes Us in detail, but it could be a circumstance where a provider bids on this workload because they have a a100 but in the bid it's going to select the last element of their array which would be the 40 90 in this case and most likely wouldn't have that resource and would bid on that you've definitely detailed this and in great detail, but would you like to describe it any further? + +Andrey Arapov: I just want to add that it's not necessary picking the last in this deal, but it picks I mean First Source dictionary and alphabetically, so if you scroll down to additional information and a little bit down there you will see. + +Scott Carruthers: Yeah makes sense. it starts the dictionary and then it's the last element in the sort of dictionary. Okay. + +Andrey Arapov: Yeah, and if you go a bit more down you'll see that I played with the simple sort actually also played these are going to compiled it but shared in this particular should because I'm not sure if it does the same sorting in our version but going basically does the same sorting and I played this different deployments and actually it confirms that it takes The last one from the sourcing so it's kind of not so easy to reproduce without knowing this in beforehand. + +Andrey Arapov: Because exactly situation. But yeah, it's possible and if you scroll down to the comment from me, there's a partial background. Basically what I did, I modified the price script so that in this case if it happens, it just takes the highest price from the available price prices of the providers. So the provider this so nobody can basically kind of fill out. Of that abuse the provider in this kind of case. + +Andrey Arapov: Yet not it's partial background because if somebody knows that this particular provider has let's say cheaper GPU and if it happens so that if you sort dictionary of medically if it happens, it comes the last and while being sorted then it's possible to get the cheaper price for let's say higher and GPU so kind of tricky but yeah, that's why I named as a partial background. + +Scott Carruthers: Okay, and I say so that's part of the generic script now. So this partial workaround is baked into the script, okay? + +Andrey Arapov: Yeah. Now I also made an announcement on for that I think. + +Scott Carruthers: Yeah, I thought I remembered that. I know that I'm Archer wanted to wait to get into the session to do assignment, but I'm just going to assign and I'll Touch base with them as well, but I will assign Archer to this. For now, and again, I'll follow up with him to see if he wants to do anything differently. + +00:10:00 + +Scott Carruthers: And do we want to possibly would be? appropriate severity + +Andrey Arapov: Yeah, I think it's quite important not as P1, but it's beautiful for sure. + +Scott Carruthers: Yeah, okay. + +Andrey Arapov: It's over T. 1.600 1.3 something that's + +Scott Carruthers: Yeah, okay. Okay, and I didn't take a pause after we discussed the first issue, but I'll do that now and also for this one as well, is there any Comments questions about either of these issues that we reviewed. + +Scott Carruthers: Okay, and yeah without Tyler I think we're done with the issues review for this session. + +Tyler Wright: Okay, can I talk briefly about increased Max's limits? Because that's something that's coming up today issue number 140. + +Scott Carruthers: Sure. + +Tyler Wright: This Doesn't have to be assigned or triage right now, but this is something that is actively being worked on by Archer. I put a message in the validators chat last night. There is going to be a binary upgrade. It doesn't require a network upgrade but there will be some binary changes that are coming. Today. We're asking that all validators can make those changes around one PM eastern time. I think it's six pm UTC and these changes will + +Tyler Wright: Add limits so that's as you can see in this issue. So that larger deployments can be created on the Akash Network. I know that there was some limits set last year on purpose to try to continue to grow the network efficiently and not have too many outlying issues as people are trying to deploy maybe larger workloads. And all this may not be Network related. This might be something else but now because of a number large amount of demand from folks in AI ml space that require larger deployments. We're going to be again racing the limits and so that's going to be happening today. So if you're a validator or again anybody that's Here right now. That's a Insider or Works closer with the community. Please look out for those changes and there will be some provider changes that will be shared today as well. So + +Tyler Wright: Again, we're still looking to have that mainnet upgrade domain at eight on November 20th, and more information will be made soon. Obviously when the proposal goes online folks will have the block height, but this is a more pressing issue today. So I just want to highlight it real fast. + +Scott Carruthers: Yeah, and just some history on that when I first joined Akash So these are the current limits that are set within in the go code and does a Ascend any check on deployments to not reach these upper thresholds. When I first joined to Cache these were dramatically lower than they are today. So max CPU, I believe that when I first joined was 10 CPU per deployment. So approximately a year ago, we dramatically increased those limits some up to 256 and I'm just focusing on CPU but obviously others were raised as well. So we did a dramatic race, I think from 10 to 256, but now as Tower described with some AI workloads even 256 Max CPU per + +Scott Carruthers: Or per instance of a replica set is not sufficient, which is obviously great news that we have some demand for deployments that need more than 256 CPU. So we did raise that recently within the last year, but now there's a rather urgent need to increase it dramatically. Higher for those AI workloads like I may have heard a hand. + +Tyler Wright: Go ahead Benjamin. + +Benjamin B: And it's told to say two things the first things that I remember when these years were way lower as well. The other thing is that the though I agree with this change, I believe that this must be done. I'm a bit worried about having such high limits, but this not be problematic if up provider wants to build on two things at once, but they build on one thing with all the resources. They don't get that deployment and they missed everyone. So if two people were to try to deploy at once one word to take up. Maybe 100 CPUs and the provider has 105 maybe and the second one were to want to have the 20 CPUs. + +00:15:00 + +Benjamin B: even though the provider doesn't get the first deployment called the second note we missed because of this. I'm not sure how the resource allocation works. + +Scott Carruthers: Yeah, no, that's certainly so there's been some internal discussion and Benjamin you and I had some discussion around us some more. Possible concern for the network a few weeks ago. So yeah, we're definitely cognizant of that and that would occur if if they had 105 Us CPUs and somebody requested 10 which brings So those would be reserved during the bid process because obviously we need to reserve those while they bidding process is in flight. So yeah that would bring them down to 95 available during that five minute period or shorter depending on when the lease is created and those resources are free. So yeah that is a possibility and as + +Scott Carruthers: just the nature of the network today but yeah, the concerns that you and I discussed a few weeks ago are definitely known and are being considered. But yeah that is a possibility today. + +Scott Carruthers: any other thoughts or questions on this + +Scott Carruthers: Okay, I'm gonna stop sharing my screen and and obviously if there's any questions on that or anything else as we go along we can revisit. But yeah, I think Tyler we can move on the edge with the agenda for now. + +Tyler Wright: Thank you Scott for ing. working through those issues and support repo Again, if anybody has any issues that are related to Cloud most feel free to drop those in the cloud builds repo under the issues area. I know that Max and Max do a great job of Looking at those issues making quick fixes staying connected with folks inside of Discord inside the ecosystem Cloud most channel of many other channels. So again, if anyone has any issues specific to Cloud those feel free to drop them in there. And then if anybody has any questions, feel free to bring them up here the next usually joins his call or again reach out to the Max's on Discord because they do a great job of being very responsive. + +Tyler Wright: Cool moving on. I do want to ask because we have a number of folks from the inside of the community here as well as Andy from The Core team. Does anybody want to mention anything that they've maybe have seen in Discord or in other communication channels over the last couple of weeks that they want to talk about go ahead Julius. + +Julius Haus: I had the issues with a Boundary staking two weeks ago. I managed to crash his provider. With a specific sdl, and he told me that he would get in touch with you and would like to check if this happened maybe with Andy. + +Andrey Arapov: Nobody really conducted me in this regards, but I'm really interested in about this is the L. If you could just share it with me. I would try to test it on my provider Maybe. + +Julius Haus: Yeah, it happened because of different gpus and it choose the wrong and the wrong GPU and somehow it restarted. I will share the sdl with you and I'm not sure if you fixed it already, but he sent me a message that he will get in touch with you with the team and + +Julius Haus: maybe it was just a wrong setup, but I was not sure about that. I will send you all information. + +Andrey Arapov: Yeah, yeah. Thanks and when it happened because about a month ago providers had unattended upgrades enabled and it was causing a lot of issues how I can so maybe it's connected somehow. + +Julius Haus: No, it was two weeks ago on the 28th of October. + +Andrey Arapov: it's also possible that they didn't disabled or something. But maybe it's something else. It's very interesting. just waiting for this deal to look at things. + +Julius Haus: Okay, great. + +00:20:00 + +Tyler Wright: Terrific. Is there anything else Benjamin Bax George anything else that you all see? + +Tyler Wright: All Max asked a question that There's no need for a dove prop for the limit increase. No, there's not needed for prop which is why we're going about this way. Originally you're trying to determine if there was a good prop needed and then we're going to add it to the main net eight upgrade. But after further research, it was determining and upgrade is not needed which is why we're going about it and solving it today. + +Tyler Wright: Has anybody else here seen any? Specific themes inside support channels or any specific issues outline outside the issues that DJ rays that might be worth more visibility from the core team or just the support group in general. + +Tyler Wright: cool All right. again much appreciate everybody here who's gets involved and stays involved in Discord and other channels and is there to provide support for many new and existing users so much appreciate all of you. + +Tyler Wright: All right. That is the typical agenda. I know that there was some thoughts about having Around discussion pages in GitHub Benjamin. Did you have anything specific that you wanted to talk about there as it relates to just support in general. Go ahead. + +Benjamin B: I don't really know how to solve it per se but I know that the problem here is that not enough people got involved during the discussion period the proposal. was on the discussion pages for maybe a month into the split between two pages and I'm not sure if almost anyone continue involved in discussion besides me and + +Benjamin B: Basically, the proposal went to shame. And as soon as people started to discussing it people were against it. And I'm not quite sure how else to phrase it. + +Tyler Wright: Yeah, I have strong opinions about that. But I'm going to express them very quickly. I agree with you Benjamin. I would ask especially I'm going to talk to Adam wozni about this the Insiders in vanguards very least should be looking at discussion and participating discussions. I was disappointed frankly that I feel no or the other across Network a great deal. I care about bringing more demand onto the cost Network that is top of mind for me. That's top of Cloud parity, which we're a long way away from is very much top of buying for me and obviously finding more Builders like the Max's ZJ so many others in the community. That's what I'm really focused on as an individual. I feel as if a lot of people in the community have good intentions about. + +Tyler Wright: being available and have strong opinions about The College Community, but I would like to see more consistency. I know that everybody has a life and everybody has other things that they're working on I guess but I think that the bare minimum there should be at least more participation in GitHub discussions. I know that this group had talked about this a number of times as well as it was brought up during the steering committee, which people on this call. Were in there at the steering committee and during those conversation during those times. I feel like there was not that pushback Right. Nobody really said much of anything and SO waiting to the last Two minutes of the fourth quarter when something's already on chain, I think is less than desirable from a efficiency standpoint. But ultimately + +Tyler Wright: the community spoke and the vote so I think at the end of the day there was no issue. I would just ask that more people. That care about the community that want to see the community grow can just stay involved at the base level of just getting involved in discussions when some of these topics are talked about in Discord, which they were all talked about in Discord for a couple of weeks. I would ask them more people get involved in those discussions earlier on so that we can get a pulse of What's going on the community and what the community thinks? I think we didn't get a pulse of what the community thought besides Benjamin your thoughts before the weekend and again ultimately. The structure work then boating worked right? Because the community had strong opinions and those opinions have been felt but it would have been in my opinion better from an operational standpoint and there was a number of chances for people to get involved earlier. Go ahead Ben. + +00:25:00 + +Benjamin B: Another possible solution for this would be that our to create such a proposal. a requirements could be set to Have the market research be done. So just would you want this as a tenant on the network? Yes or no what you want? This is a developer. Yes or no. And from that it could be displayed on the proposal at least and then I very much agree with you. I believe that a discussion should have at least + +Tyler Wright: I agree with the first point I think is on the proposer. I think that's an example if Max. And the cloud most team won to do something. I don't think they would have to show a level of market research because they have a tool that They're having it. They've shown a track record and it's just building on pawn something if people in the community require market research then they could either say I'm not gonna vote for this proposal. until I get the marker research or whatever, but I don't know if that should be a part of the framework so I know Scott I cut you off and then Benjamin back to you afterward. Go ahead Scott. + +Scott Carruthers: So this actually wasn't why I raised my hand, but Tyler on your point about it being the responsibility of the proposer to do the market research Correct me if I'm wrong, but I think that may have been what Ben was suggesting why so in this proposal that was launched it would be and come in that proposer to do market research and include that market research within the proposal. + +Benjamin B: Yeah, I would say that it would go much better if they did this research before but I also believe that when in this example of cloud must not requiring. And if any market research instead, they have their numbers to prove it and just naming those numbers that they have done in previous proposals. I think that's good enough. That's one type of more research. + +Tyler Wright: No. + +Benjamin B: in my opinion + +Tyler Wright: for sure, but the Max's started from zero at some point just like any of the other teams right before. Cloud most was a thing. They were proposing an idea of what they wanted to bring into the ecosystem. + +Tyler Wright: And the kind of tool so that was only I agree and I agree with you that the best kind of proposal has all this information. and I believe that if somebody wants to have the best chance of it. Yes, then I would say everything that you're saying makes a lot of sense. I just don't necessarily want to make it a requirement because we did there are so many other requirements that we're making folks jump through if people don't want to do it then + +Tyler Wright: Yeah, then people just vote against it, go ahead Scott and then Max following. + +Scott Carruthers: Yes, I want to go back to the original thought here of that. This proposal had very little discussion before the proposal was put on chain, so this is just my initial perspective on this and I'm wondering if there's any disagreement with this agreement or in exactly what was done in this case, but The thought around that there wasn't enough discussion on this proposal. obviously the community and even some of the Akash core team, there's a volume of stuff that we need to focus on and it might not be especially from a community perspective not realistic that people are just casually browsing for open discussions. But to me, there's a pretty simple solution to this and that being it should be incumbent on the proposer. + +Scott Carruthers: To elicit discussion. So especially when you're seeking Fund in right? So if I was seeking funding for a specific project, it should be my responsibility within Discord to ensure that their significant discussion and so to me my point being it should be the responsibility of their proposer to ensure that there's those ability and there's active discussion and ensure that Significant or sufficient discussion has occurred before putting it on chain. There shouldn't be an expectation that people are just organically. Cognizant of these discussions. So obviously that's pretty simple solution. I don't know if anybody disagrees with that. But again, My overall point is it should be the responsibility of the proposer to ensure that there's visibility and significant discussion before putting an unchain, sir any disagreement with that? + +00:30:00 + +Tyler Wright: I go ahead. + +Benjamin B: I'm just Start. Okay. I'll go ahead. I just want to say here that I used to have a different opinion on this but after you've mentioned it kind of makes sense that more scalable method here is that the proposer gets the opinions and gets the people to engage in the discussions then? in accordance insiders the proposeries could just reach out to other insiders could tie them in The Insider Channel and say hey, could you please Tell me. What do you think about this? Could you add your opinions to the discussion pages to do this or not? They could also create a Reddit post with your posts. It's not that hard to reach out to people to get involved in the discussions. + +Tyler Wright: Go ahead Max. + +Max: Yeah, definitely agree with your approach Scott, I think. People that are requesting for funding should definitely work. Towards getting some feedback from the community. but also like you mentioned Tyler they presented or talked about the proposal during the steering committee. Which is good I guess but I guess yes, maybe an improvement to this process like having the proposals presentation to the community there. their project that they want to get funding from could be + +Max: we're having the funding process in a few steps the first step would be to obviously create the discussion or the issues. But put up. I think a discussion on the GitHub repo and then try to get some feedback from the community by communicating others. to the various channels + +Max: if let's say the proposal gets some decent feedback and the project itself seems to be worthy of getting funding. I think there should be a Next Step where there could be a Kind of like this sigme things, but just an extra meeting dedicated to that project for that project to present to the community. And having all the Insiders or anyone else that wants to icip joining on that thing to have. As much discussion as possible and see. + +Max: what the team is all about and just have a better graph grasp of the project is normally if you seek funding from anywhere in the world, you have to thank you presentation or something and have an audience that you can speak to. to get some feedback and see if it's worth funding and then after that The Proposal goes Unchained based on what's the result of that process I think would be a good Improvement. + +Tyler Wright: I hear what you're saying Max and I don't think from an operational standpoint anything that you're saying is necessarily wrong. thought my response to that is in the past when we've tried to facilitate more meetings or specific meetings about topics. I know that people in the past have been like all right, we already have too many meetings. Can we bring this into another conversation which is I thought what the value of the steering committee is, which is why again, we made it a process that nobody can put anything on chain. Ideally until they go the steering committee because that meeting where they can present to a large member of the community. I get what you're saying in theory and in theory, this makes a lot of sense right I would love for. + +Tyler Wright: Anybody to be able to pitch to the Insiders and have 30 to 40 people there talking about I like this. I don't like this that would be great. But the reality of it is that doesn't happen. We don't even get that consistent level of participation for The Insider office hours. So, I don't know when we be able to even get that kind of commentary which is why I think the GitHub discussions work. So Frankly Speaking. I looked at the Benjamin put an issue in the cloud most presentation, The cloud most asked from February. That was an ask from a team, another thing just not because Max is here, but that's and ask from a team that has shown what they're capable of has shown that it's a product that literally almost everybody in the community uses, right? + +00:35:00 + +Tyler Wright: But there wasn't much commentary even on that proposal up until Luna maybe had some negative things to say which caused Max to respond. And then there was an actual commentary from there prior to that there wasn't that much commentary from people in the community, even though again, the Max's had been known they shown what they're capable of they were just taking next steps on what they want to do some based upon working group sessions and other conversation with the core team. still again. There was one person that's A case of feedback and that started discussion. I think only six people got involved in. So I'm fine to try all these practices especially based upon what just happened but + +Tyler Wright: I don't know how to put it frankly again. I think whatever. it may not been smooth sailing to get us to this point. But whatever the voting structure worked right there was enough people that pushed back on the proposal. Even though is already on chain one questions in GitHub, even though it was already on chain had discussions inside our office hours and validated channels, even though it was already on chain and then again The votes have shown themselves to be what the community is looking for. So I'm gonna talk internally and I'm gonna talk to some of these insiders. I really want to have this discussion maybe with some more insiders during The Insider office hours tomorrow, but then we can figure out some small tweaks that we can make to the process? Go ahead Bend and then backs after okay Ben saying go go first max. + +Max: Yeah, I agree with what you're seeing about. too many meetings and also the participation might not be at the peak for these kinds of meetings, but + +Max: also the process is technically already there with this steering community meeting, but I feel like when it's done in the steering coming either there's so many topics that are talked about in that single meeting in that same hour that some things are Rush. Sometimes I feel like and that's the reason why I propose a separate reading for the bigger funding because there's not that many that are asking for 63 k for example, right now there's only just one. So I feel like having a separate one hour meeting or 30 minute meeting whatever length of the meeting is for. The bigger purple would be worth it. It might be maybe something to experiment with I don't know. But yeah, I wouldn't do like a meeting for. + +Max: for all the projects only a handful of project or the few ones that pass the discussion phase where it's seems like it's in project and we want to know more for example in that case. We would have that separate meeting for the presentation in discussion. So yeah. + +Tyler Wright: I think it's a good point. Do you think Max or anybody else? Do you think there's a threshold that you see in your mind is 50,000. The threshold is 25,000 the threshold because theoretically right we didn't have the same level of Discourse around metamask when I think the Mystic team got fifty thousand dollars for a metamask plugin. So is a threshold should we make it lower to make it higher Because we just have the steering committee conversation. They had a GitHub discussion that I don't know if it really got that much. Commentary then they live their proposal but on chain, they got voted through and they got the game. They got the money. so + +Benjamin B: Tyler I think the case series that it should be on a Case by case basis if I believe that's the discussion should be first and then if people in the discussion that want to understand more details, maybe they want to request a live demo with q&a's instead of just recorded the demo It's anything else that anyone wants to say about this topic. Otherwise, I will go back to something Tyler said earlier. + +00:40:00 + +Benjamin B: Tyler gave me the thumbs up and I don't see any All right, so going back to what you mentioned about the Tyler. I actually liked idea that we shouldn't put that money requirements out. When creating a proposal but rather we could recommend. What's to do and I believe that for the market research. I believe that Adam is already recommending this in a pin the discussion on the discussion page so I think that this document maybe could be improved if anyone finds an issues in it, but for the market research specifically not having the requirement but rather just this is what we recommend. + +Benjamin B: is good enough I + +Tyler Wright: I think that's a great point. I think maybe in the future. If anybody here Benjamin as an example, if you would like to see a live demo. Maybe that's something you can either put in Discord and I can see that and I can create a meeting or we could put that in GitHub discussions. And so that'll be like an ask for members of the community, but then we can set up a separate conversation for here to everyone's Point here based upon a case by case basis. and so if there's more demands from the community before they can feel like they can make an educated decision right? Maybe some things are just cut and dry. it's just like, all right. Yes, I understand what this community pool spend is being used for makes sense. We don't have to have part of the discussion but maybe other things like maybe this specific proposal that is on its way to being rejected that there's a request and Benjamin the max or anybody else like hey, I would like to have a demo that's more than + +Tyler Wright: the video that you all brought to the casathon then I'll see that in back, Yeah, that makes sense. We should create a separate conversation and then make sure that there's enough stakeholders available to have that conversation. I also like think that some of that async conversation with happening. Again, I just felt like and this is why I believe there's needs to be more participation if I can speak frankly, right? And this is just my opinion when there was no participation except for min. Through the first two weeks. I was under the impression that Benjamin's opinion was + +Tyler Wright: His own and it was isolated right? I know that Ben also had some issues with how the akash-upon was handled and maybe the first prize and so in my opinion because there was only Benjamin talking about it. I didn't know Benjamin Had through feelings about be what to this proposal would do in terms of creating more Demand on the Akash Network, having more users have more streamlined view or if it was more self thoughts about process is how this team had come from a casathon to now wanting to build a business out of it and put a proposal on chain for community pool funding. when more people got involved in the conversation and started raising different questions than just the akasathon and the status of the demo then + +Tyler Wright: it became more of like, alright, we need to have more conversation about it and they got to this point, so Benjamin, I'm not knocking you in any way, but I think to your point we'll do a better job of getting more insiders vanguards the members of the other community to participate in conversation earlier so we can have more depth of opinions earlier in the process as opposed to again once something's on chain for about again last thing I'll say is ultimately I understand and we want to optimize all parts of this process. But ultimately the community spoke. And the book and the proposal as it's been proposed right now is going to be rejected. So to me that's like a win for democracy, potentially + +Tyler Wright: Cool any other thoughts questions again? I want to talk about this a little bit further tomorrow during inside our office hours. I put the discussion that Benjamin's referencing from what Adam did on best practices for a college governance proposal. If anybody sees anything in that that they want to feel free to just drop either a comment in the bottom or just feel free to start a discussion insiders and then we can continue to optimize this document so that we all feel comfortable. + +00:45:00 + +Tyler Wright: Is there anything else support related or anything else in the community that anybody wants to discuss before we head out of here? + +Tyler Wright: No. All again if anybody wants to participate in Sig design is coming up in about 10 minutes and then there will be a Sig chain meeting where I think we'll talk a little bit more about the network upgrade as well as the max units changes that are coming today. So if anybody has any more questions, but believe members of the core team including Archer will be at that meeting in two hours. But again, of course gonna be an hour and 10 minutes, but prior to that we'll have a Sig design meeting that's kicking off shortly. + +Tyler Wright: A bunch of appreciate everybody that joined us meeting. We'll talk about issues and the support repo that need to be tries. But I really like the conversation that folks were having around again. The governor's proposal process. I would love for this group and others to just continue to be engaged continue to speak your mind and speak your peace on all things. If you don't feel comfortable doing it in public feel free to message me privately so that at least I know where you're opinions are and I can look to push them forward in a more public setting but again much appreciated everybody. + +Tyler Wright: All I hope everybody has a great day. Thank you all very much for all the discussion today. I'll make the notes available soon, but I'll get appreciating each and every one of Hope everyone has a great message that. + +Tyler Wright: All right. + +Meeting ended after 00:47:15 👋 + diff --git a/sig-support/meetings/022-2023-11-22.md b/sig-support/meetings/022-2023-11-22.md new file mode 100644 index 00000000..7080edc5 --- /dev/null +++ b/sig-support/meetings/022-2023-11-22.md @@ -0,0 +1,437 @@ +# Akash Network - Support Special Interest Group (SIG) - Meeting #22 + +## Agenda + +- Participants will look at issues in [Akash Support Repo](https://github.com/akash-network/support/issues). +- Artur will lead triaging issues, and discussion of implementation for issue fixes. +- Artur and Anil will lead discussion putting severity on issues. +- Scott will discuss Support from the community and ask for any community feedback. +- Participants can have an open discussion of any other issues or support related items on Akash Network. + +## Meeting Details + +- Date: Wednesday, November 22nd, 2023 +- Time: 07:00 AM PT (Pacific Time) +- [Recording](https://l5yeilkhvwmpqetchbk2pax4nxmu6miv23cxy7iszl7nvgbk4lka.arweave.net/X3BELUetmPgSYjhVp4L8bdlPMRXWxXx9Esr-2pgq4tQ) +- [Transcript](#transcript) + +# Participants + +- Andrey Arapov +- Artur Troian +- Benjamin B +- Deval Patel +- Max +- Rodrigo Rochin +- Scott Carruthers +- Tyler Wright +- Zeke E + + +# Notes + +- Artur talked about how busy the last couple of weeks have been. There was a mishap with 1 small edge case after the network upgrade. +- New Mainnet 9 coming next week, November 28th, 2023. This should be a quick upgrade. No action is needed for any clients. +- Artur talked about AMD support. This is something that has been thought about it since GPUs were brought onto Akash. +- Testing of AMD provider will be tested on the sandbox after the network upgrade. +- Provider will need to be upgraded when AMD is implented. +- Scott has been working on Feature Discovery. This is a "p1" issue. +- The group talked about issue 153. All issues need to be in proper formatting. Benjamin has talked to this user on discord. +- From experience, any feedback or recommendations i've given to the user has not been followed. there's no reason to waste time on someone asking questions but not listening to the answers. +- The group talked about issue 144. Artur mentioned that there is no way to fix it right now. +- Issue 148 was discussed. Andrey mentioned that this might be fixed with v0.30.0. We will monitor it. This issue was assigned to Andrey. +- Sig-chain mainnet 8 is closed. + + +## Support + +- Not all providers have upgraded to mainnet 8. +- Praetor team is working with users who had trouble during the upgrade, and did not use 1 click upgrade. +- Rodri noticed that there are old docs from old network upgrades. +- Rodri talked about his provider issue. He installed some extra stuff on his provider during the upggrade. +- Deval asked about how to decrease development time. Artur asked Scott to share link to development documentation. +- Scott shared documentation with Deval https://github.com/chainzero/akash-engineering-notes/tree/main/akash-development-environment. +- Artur gave a demo as apart of a new series with developer office hours during sig-support biweekly. +- The demo was around Akash development environment setup. + + +## Action Items + +- Track issue 148. ThiS may be solved. +- Discuss issue 153 after network upgrade to Mainnet 9. +- Max will be working on endpoints for Praetor team. +- Make a new issue for sig-chain Mainnet 9. + + +# **Transcript** + +_This editable transcript was computer generated and might contain errors. People can also change the text after it was created._ + +Tyler Wright: All right, welcome everybody. Who seek support monthly meeting I believe this is number 22 or student biweekly meeting number 22 during these six support biweekly meetings. The group goes over any open issues in the support repo anything that's a waiting triage and Artur and sometimes Scott lead the group through triassing those issues last week or excuse me, two weeks ago Artur was out of office of Scott. Let us through triaging and looking through a number of issues in the support repo. + +Tyler Wright: One other thing that we're looking to add as a part of the sixth support biweekly is after we triage issues and if anybody has any questions about any issues and those questions are answered we're gonna hand it over like we normally do to talk to Andrey who's been very hands on and support and some of the other members of the Insiders that are on this call to talk about any support issues or any issues that might need further conversation when it comes to new and existing users using We find in Discord and then after that if any time remains and usually we do have time to remains after that, I want to start opening it up to technical questions. So I know that Archer and Scott members of the core team along with Andre + +Tyler Wright: Are often at these meetings? And so again if there's any time left after triaging any issues and support repo and talking about General support in Discord and Beyond I do want to give some time for folks that have specific questions. I know deval's here today from the pray to our team. We've been working on content moderation and we'll hear a little bit more about that in Sig providers, but I know he has some specific questions related to the code base and so again, When the opportunity presents itself, I want to use some of this time for members of the community to meet with members of the core team to help with anything very technical. + +Tyler Wright: So without further Ado, I'm going to hand it over to Archer to get us going with triaging any issues initiating and the support retail. + +Artur Troian: Thanks, Hello, Alright, so last couple weeks were quite busy for us. So on this last Sunday we formed. successful Network upgrade There was a little mishap in one of the things, like the new feature it's Be attributes. + +Artur Troian: one of the functions Was implemented slightly right? So we are on the way to make one more Network Tuesday, November 28. It should be really quick and does not change doesn't alter any state. It's just + +Artur Troian: the behavior called function does cross validation between the order so hopefully it will be really quick and there's no actions required from any clients. It's purely the blockchain conversation. Moving on. Yeah, we have I think. Not that many new issues right now. So I want to talk about this one. + +Artur Troian: We have been thinking about MD my sense In southern our table and we have pretty much everything to support that. Right after Network upgrades next Tuesday. We will be a bread updating provider that allows users that allows provider to beat on MD. And gpus so right now this part is disabled intentionally. As soon as we do that we will be doing the testing on the sandbox. Say that you don't have any major issues and if everything goes it will be publishing provider. Vs. MD support. So once again from that perspective, there will be no updates needed by the clients. It's really The Wider part. of this feature + +Artur Troian: The next one is future Discovery. This is rather big Improvement and Scott is more money working on that. So we don't have any levels here one wider idea is that we want to improve visibility on Water Resources provider how as well as a remove manual lightly of the nodes for example, writing for the persistent storage and the gpus as well as this service will be updating provider attributes on chain. So the completely rules are user error. I mean users to provide owners still will be able to do that. They need to but we try to encourage to that's a provider features of our service is out. + +00:05:00 + +Artur Troian: Providers to just use automated thing as well as we still thinking that to add quite a few same into the future Discovery. It will be merged with the inventory service. and the gonna drastically improve visibility of the dashboards like Cloud boss. To see what actual amount of gpus and what exact model of the gpus for example available and given a Time. + +Artur Troian: Okay, and this one, what is that? my God. I mean Yeah, this is. + +Artur Troian: Let me see. + +Artur Troian: Let me just answer. + +Andrey Arapov: I think someone is just running a SSH service and it's getting killed. I think actually this one of the deployments that was causing all those zombies + +Artur Troian: and yeah, let's go start with promoting the sdl. + +Andrey Arapov: Yeah. + +Artur Troian: + +Tyler Wright: While archers are typing response go ahead Benjamin. + +Benjamin B: those wanted to say that this user has written in the Discord server as well and some of the suspected reasons to why crashes is that he's trying to deploy something with only one gigabyte of storage and then when it tries to install something that's larger than one gigabyte. Of course, it will crush because the STL and the lease is more limited than what he's trying to do. I wrote to him in this group that is trying to rent the persistent storage as 100 gigabytes or whatever depending on my stylus using but unless + +Artur Troian: Yeah, yeah, let's see. I've encourage everyone if you see such poorly formatted requests or the issues, let's start first of all with awesome them to promote it properly because it's just absolutely + +Artur Troian: Unreadable, right and why should anyone Vice the time to try to realize what's going on there? so yeah, I just made the + +Artur Troian: reply there. moving on. Let me see. + +Artur Troian: the first of all lost + +Artur Troian: Good. Yeah. + +Artur Troian: Yeah for this one. I don't think + +00:10:00 + +Artur Troian: I still in trying to figure out what's going on here. + +Andrey Arapov: Do you want me to tell you? + +Artur Troian: The problem the wider is going to take each other GPU it has available. so + +Artur Troian: let's yeah, we will review that after the upgrade I think Or maybe would fix this thing. If there is an issue is the MD support. + +Artur Troian: and yeah, so this is the sdlery design and there is no way we can improve it right now, unfortunately. + +Artur Troian: Okay, so that's the service count here. that you see. + +Artur Troian: All right, that one is done. So what happens with this issues is the wider statistics. it's purely the statistics of point. So it doesn't account the replicas for the cheap resource image On this objective marketing to fix that. + +Andrey Arapov: I think I've tested this. + +Artur Troian: that is + +Andrey Arapov: Sorry Artur for previous one. I think it's already solved but we'll see in all 29 or c0 that I tried setting one GPU encount to and it's seen us to request it. So, I mean, it's possible that your latest commit fixes this in all 30 Network. + +Artur Troian: Okay. Thank you. Okay, so I'm not sure what we can do here that is all already supported and I believe you talk about that. So the ram be + +Artur Troian: it does so as soon as label. Let's say not + +Artur Troian: this attribute is not quite actually correct. It has to be like that. + +Artur Troian: please + +Artur Troian: And so it has to be this way. mmm + +Artur Troian: Okay. + +Artur Troian: Yeah, so as soon as not is labeled and the + +Artur Troian: and why they're attributes labeled correctly into work so that I believe it all has invested in the you test not so. + +Artur Troian: Yeah, I don't think anything to do here. Is that okay? + +Artur Troian: double check + +Artur Troian: Okay, so you are here? + +Andrey Arapov: And I send it to me, I will go of his Foundry. I will try this attribute. + +Artur Troian: presentation All right,… + +Andrey Arapov: Thanks. + +Artur Troian: I think yeah, this one is done. + +00:15:00 + +Artur Troian: So that was when you don't date on 19. + +Artur Troian: okay, I think that covers any questions + +Tyler Wright: Thank you As Archer just asking anyone have any questions about any open issues before we move on to General support. + +Tyler Wright: After we talk about again any issues that need triage and if anybody doesn't have any questions or after we talked about the question related to any open issues and support o. The next part of the agenda is around just general support and Discord and in other channels with members of the community new and existing users that are interacting with the crash. I know that Scott has previously been giving some updates but now that he's more an engineering side and Andrey been helping a lot with providers. I'm going to ask Andre if there's anything he's seen in Discord on the provider side and then there's a number of insiders here that I'm hoping will continue to come to this meeting and give any updates that they see for many users either deploying or becoming a provider so Andre, I know that you're quite active in Discord helping again providers. + +Tyler Wright: Helping anybody that needs support with the cash. Is there anything that you're seeing over the last couple of weeks that might be worth note to the group here today? + +Andrey Arapov: August the main concerns that not all providers have upgraded to maintain or they may be have but they need to bounce the cash provider pod. Basically, they providers need to always check that they can beat after they upgrade probably added to the next procedure for great. So the ensure that The quality is there so I guess the only point and don't have anything else to add. I guess nothing comes to my mind as of right now. + +Tyler Wright: I said go ahead Deval. + +Deval Patel: Eight of our providers so far. I'll create that's what I know. I don't know how the objective later right? That was the number last night. I'll double check. today morning and find out. Yeah, that's right who is not being able to update using one? Click button or something? some people actually tried doing, the official document and one click great those people having issues somewhere, right? So I'm trying to help + +Tyler Wright: Executive all that's a good call out. One thing that will make sure that we do is clear as possible is because I did see this in a channel when myself or Andre are making announcements. what we tried to do is as early as soon as we can we try to share information with the page to our team. Sometimes it's running up against the clock and they don't have much time to be able to do one click upgrades. But again, we try to share that information with the parade or team as quickly that the provider upgrade had been tested and are ready to go out when we make announcements. We'll make sure moving forward to make it clear that if anybody's as upgraded or has used parade or path for their build to have Specific Instructions that will link to the ecosystem pray to our page and then Deval into gar will get the instructions on when things are ready to go there. + +Tyler Wright: just so we can try to avoid any extra confusion for folks again, even though both are using Helm charts. It seems like there may have been some issues for a couple of folks. So we'll make sure that the messaging is very clear and then in the provider announcement channels and the providers Channel moving forward for those that are again upgrading or using pretor for their bill versus using CLI at home + +Tyler Wright: Does any insiders have any other things that they've been seeing recently from the community that might be worth either potentially improving to documentation or moving to the process in general that might be worth talking about now. + +00:20:00 + +Tyler Wright: I'll take that as enough. All right. I appreciate go ahead Patrick. + +Rodrigo Rochin: Is I couldn't find the antique. Yeah, I had the little confusion the other day with a document an upgrade. I noticed that there are instructions in the docs from previous upgrade part of their necessary necessary still if not, maybe get rid of some. + +Tyler Wright: Thank you I think that's a great idea. comb through the site and see if there's any older documentation. This is a beautiful segue into there is a Sig documentation meeting happening. Next Tuesday as has been previously discussed. We are going to be relying on the community more in 2024 to help with documentation. There will be some bounties and rewards around those that are consistently contributing to adding new editing documentation. I know the onus has been on Scott for a long time and again with him moving into more of an engineering capacity. We just want to take that off of his plate Andrey and I will be there to help. + +Tyler Wright: Help with submissions and help with RS. Obviously I could help with a copy standpoint and making sure things are structure properly will have very specific instructions on how the structure of the facts should look how the quality of images Etc. So, there will be a framework in some specific rules that we'll discuss next Tuesday, but I know there's a number of people on this call that have shown interest in documentation and Andre will be there somebody that can look at the code. And yes, this makes sense and then, be a test and then again, we'll certainly be relying on the community as well because Andrea the number of other things that he's actively working on for overclock, so It'll be like a team effort. But we just want to make sure that we're getting consistent contribution from folks in the community that can contribute because certainly will need it. + +Rodrigo Rochin: Keep looking through doctors and I'll share the ones that I think are not relevant anymore. Will you do whatever you think of them? + +Tyler Wright: Excellent I much appreciate that Roger. + +Tyler Wright: cool, All right, so I'll go ahead. + +Rodrigo Rochin: through the upgrade recently, and I don't have for instance persistent storage enabled and there's this step that I was supposed to skip but I ran the command. I don't know if I messed up anything or not, I guess not because I think it's working. + +Tyler Wright: Are you saying that there was a command that didn't need to be in the documentation or are you saying that you're having issues with your provider right now? I might have missed that question. Okay, perfect. + +Rodrigo Rochin: from that and that document I ran the command on 2.5 step 2.5. Which I shouldn't have because I don't have presentation search but I didn't read about skipping that section after until afterwards. + +Rodrigo Rochin: I guess nothing happens if I run that. Or should I do something? + +Tyler Wright: So I think Roger's question is if he ran the command to ask for precision stores,… + +Deval Patel: yeah, I Know none,… + +Tyler Wright: but doesn't have persistent stores set up. Yeah. + +Deval Patel: nothing will happen if that command view run with the install then it might have installed. But other than that we should be fine. + +Tyler Wright: Again, we've gone through the part of the agenda where Artur leads us through triaging any issues that need triaging in the support repo. I know that the cloud most team does a great job of any issues that come through Discord or anywhere else that get put in the issues inside the cloud most o. They do a great job of responding to those issues and fixing them in real time so much. Appreciate the Max's Real quick is there anything Cloud most related that anybody wants to talk about as it partake to open issues in the cloud most repo? + +00:25:00 + +Tyler Wright: Yeah I know that they're doing a great job Max that you go out mute. I'm sorry. Did you want to say something? + +Max: Yeah, so when I say to develop that I'll be working on the endpoints that you guys requested to be built today. + +Tyler Wright: Okay. + +Max: So all the + +Deval Patel: Okay, sounds good. Thank you so much, Mike. + +Tyler Wright: Thank you Max. So again, if anybody has any issues related to Cloud please throw those in the cloud most repo and then those issues will be worked out by the Max's again everything continue to talk about those issues here during the six support meeting or we via the specific issues in that report. + +Tyler Wright: Cool, we've also talked about just general support and Discord and other channels. Thank you. Rodri Ben Max many people on this call Andrey that are just active and Discord and making sure that again users are getting the kind of support that they need. I know that it's a number of people that have written to me talking about how quickly they give responses and how it just an improve their user experience so much appreciate the folks that are active on Discord all the time. + +Tyler Wright: This part of the agenda again is a little bit new where we want to have folks that maybe have technical questions get to ask those technical questions Who members of the core team? I've asked of all to join the call. I know that he's been working on content moderation and as a result is been looking at the provider and provider code-based code a significant amount has been working on content moderation Deval. I know that you had specific questions that maybe Artur Others might be able to help with so I want to maybe give you the floor to be able to ask those questions. If anybody else want to drop off feel free. But again, this will be recorded and we want to use this time as a place for insiders vanguards and just Dental members of the community to ask any technical questions, whether it be around products that they're working on that are + +Tyler Wright: built on top of the cost or just the core code base. And again, we'll just try to do this every two weeks and just try to keep it to the hour time slot that we have. The Deval pass it over to you because I know that you had some specific questions at the pertains to content moderation implementation. + +Deval Patel: Thank you So a couple of things I want to give update and mention before we jump into any cool business stuff. So I'm trying to do the coding, in the provider Service as you guys already know what I do is that basically I fought the Ripple and tried as well as the provider and whenever I need to make some changes or taste it right. I push those changes in my frog triple in provider and help and then I tasted becoming provider and things like that, but is there any other way which I can use and do the development faster than I would like to learn that That's number one thing and that's most challenging because then I need to wait for I plan to be past and the talker Bill to be around and + +Deval Patel: things like that, So that will reduce my development time in terms of many hours Yeah, that's one thing. I want to learn. + +Artur Troian: Yeah, so there is a way to do that Scott. Can you please share link to the development environment documentation? So if you look into run Cube directory. That's the way it works. So there's a bunch of my commands and there's actually with me file in it if you go into. + +Deval Patel: I actually tried that right and… + +Artur Troian: Let me stay home and second if you go to run. + +Deval Patel: I was struggling to + +Artur Troian: Yeah, if you go to run read me runcube read me and… + +Deval Patel: okay. + +Artur Troian: just goes slowly step by step like how to initiate it. we take this out quite a few times and there's a documentation Scott you people point you. So the biggest challenge issues you have to use multiple terminal windows. So the node is running one and then you have a provider running and then you just have a third terminal. That you execute your commands. So once again, you check if you go through the readme file that step by step. It says I dedicated, separate or new terminal window for each command. If you just go step by step it will help you to start using it. + +00:30:00 + +Artur Troian: as well as once again,… + +Deval Patel: Okay. + +Artur Troian: yeah, there's a documentation on I believe that thoroughly goes through that and we have been testing it for quite a while and that's actually what we use internally to develop teachers and best things. + +Deval Patel: Okay, that would be very helpful, right? + +Artur Troian: Yeah, so yeah, just to summarize on that. We've been thinking on doing developer office hours. + +Artur Troian: Then gonna show people how to be more involved in the code bias. And so if I can actually try to demonstrate it right now if there is a lot of questions, I'm okay to do that. Okay. + +Deval Patel: which yes + +Deval Patel: Yeah, that would be helpful. so few things to go through that and the developer office hours is a great idea because that way we can learn about the s. There are So let's say the bead engine module the order module and things like that that would be a helpful for us to understand, this module does this stuff? Right? And this is the direction of the code or framework of the court, and that way we can be more productively involved in coding the provider service if needed to be right. So yeah, I don't have much because CID part I already kind of figure out right so I don't have question on part, that particles is all on my side. The next question I have is how to to close all these or at least closing trans. + +Deval Patel: Works and I wanted to understand the flow of the lease closed transaction. And because now we want to allow the providers to be able to close the lease as well rather than developers on deployers only So that part needs to be tricked in the provider Service as well as them if there is a node involved and yes then that has to be done. Right? But I want to understand that part as well. + +Artur Troian: Yes, so the easiest part from that is the least can be closed by multiple ways. So you either do deployment so from client perspective from Talent perspectively other than by deployment calls or is from provider side the provider discloses be and that's So as soon as provider issues transaction be close. The list will be closed. So yeah and that provider actually doesn't. + +Artur Troian: For let's say if the lease Not speeding up for whatever reason with image is wrong. Button doesn't exist. So what writer will do in five minutes if they lease is not healthy. It will actually close it by issues because + +Deval Patel: + +Deval Patel: Okay, another question. So when you say the least is not healthy right does it count as well that if the Manifest is not Properly deployed or it does not so let's say I want the leaves right? + +Artur Troian: you + +Deval Patel: But I do not send the Manifest or the Manifest has some problems like what happens at that point of time. + +Artur Troian: if the Manifest it has some problems that's the different issues. So by the time manifest is created. It's been validated that it's actually correct. So if manifest is incorrect, that means that the code base is wrong is having issues. yeah, but anyways to answer your question that counts as well. So let's say something wrong even the money fast. The provider will close the degrees by issues be closed. + +00:35:00 + +Deval Patel: Okay, okay, and we want to expose that using a transaction that will be initiated by provider through let's say command line or the UI from printer. + +Artur Troian: It is done automatically by the provider the issue is right now. They provider is the main user of the blockchain key and there's a thing called sequence number. So if you're gonna issues that command manually that will break sequence number and provider will click out. So there is a way but it's just not going to break things. So the beat close command must only come from the Provider Services in this stage. + +Deval Patel: Yeah, that's what I'm Okay providers service or… + +Artur Troian: but It's already implement. + +Deval Patel: okay, the very close command has to come from. + +Deval Patel: Okay. + +Artur Troian: Yeah, but that's already Implement. + +Artur Troian: I'm trying to understand what issues you're trying to solve here. + +Deval Patel: So we want to give the access to Providers where they will be able to close the lease if they find that lease is not appropriate for that. + +Artur Troian: I see. So the best way to do it right now is they have to stop providers Services first. Then they can be close. And then restart the Provider Services, that's unfortunately on the way to do that at this stage. Yes, we fully aware of this issues and we've been thinking require actually quite a while. On the ways to fix it. So this will be once we finish Provider Services split. And that's planned for some time next year. so right now the best way to do this is to stop the kill the lease by doing Because we start the Provider Services and then Provider Services will see that list has been closed. + +Artur Troian: And it will clean up the namespace for this particular deployment. So that's the way it has been done right now. + +Deval Patel: Okay, so that gives me clear idea what I need to do. And we really Implement that for now, right and you say we gonna change that in a cleaner way of doing things right at that point. We will make the new requests or make our modification as well right on the content conversation side. That's Okay with that. + +Deval Patel: Yeah, thank You are talking about the office hours. If I am done with all my questions and… + +Artur Troian: yeah, do you still want to we can do this kick on the Small version of office hours today and… + +Deval Patel: yeah. + +Artur Troian: show how to run the deployment how to debug things. + +Deval Patel: Yeah, but that sounds Really good. + +Artur Troian: Okay. + +Tyler Wright: as long as our arthritis + +Artur Troian: Yeah, so yeah. + +Artur Troian: just yeah. + +Artur Troian: it's actually probably. Let me just spare the screen. Is that on the second? + +Artur Troian: All right. let me know if you say my screen right now. Alright, so I'll just + +Artur Troian: so I'm gonna go to provider. + +Deval Patel: I'm not doing the commands with you because the recording will be available. So I'll be able to do that, on my own screen,… + +Artur Troian: Yeah, you don't need to do it. I'm gonna be showing it all… + +Deval Patel: right? Yeah. Okay. Yeah. + +Artur Troian: how to do that and… + +Deval Patel: Thank you. + +Artur Troian: okay, so, Wonder + +Artur Troian: build the example is runcube let's open. we need pretty much free internal Windows, right the top one will be. So let me just make sure everything is clean. + +00:40:00 + +Artur Troian: Up Foster. the + +Artur Troian: my Joker is dark little second. Let me Learn all that. okay. I'd like to sit down the previous cluster Starting from completely clean stage. The first command to issue is made you poster setup and this command takes some time maybe five minutes actually, maybe less what it does is it deals all of the binaries and Docker images required the local testing so for other services it builds nodes + +Artur Troian: Then what it does is it sets up, generates certificate all the keys and blah blah blah pretty much to spin up local version of the blockchain this one radiator. in Paradise Genesis and then + +Artur Troian: Right now so yeah back up on that. So first of all it builds Akash binary over here compiling a car you can see it builds it from vocal sources. Then what it does is it generates Keys then it creates the validators that then it adds the Genesis what it is. The Genesis is alright. and after that at some tokens then generates the For provider and the clients I mean until as keys. Once the account that we're going to use to deploy. When there's Genesis one more time. Then it builds the provider. + +Artur Troian: And then after that it spins up actual kubernetes cluster. Right now, so it uses time to do that. It starts control deploys whatever needed for full development process embody diets that the required deployments like engine X and other things are up. + +Artur Troian: it spins up the persistent storage if you need that and yeah, this process the last step of making sure that the nginx controller is updating sometimes Minter tool. and + +Artur Troian: Yeah, let's say now we are done. so what it does now it Applause the are images that we just build to their kind cluster and the cluster is fully up. So next command you to start the blockchain mode. We do that by doing that make node run. And it starts making blocks. So the next step will be to create the provider. So you use for that obviously separate terminal window do create + +Artur Troian: second. Yeah, right. + +Artur Troian: And it just creates the provider. until the transaction is successful so we can do make I believe very provider you can see that we have provider on the blockchain now, can this actually starts Provider Services. It was the inventory and it actually ready to accept this. So what we do right now is my deployment rate So this command runs if we take a look here? there is I believe one second. Let me double check file which as the past I believe it's gonna use this That one is yellow. + +00:45:00 + +Artur Troian: This is the deployment that you'll use to create to test. So if you do make deployment create by default, the sequence is one. So the sequence can be set as the environment as a variable. So you do like that. So this is the default one always and if you create my multiple deployments you just set to three. Four and so on so forth. and if the sequence is other than the zero, you have to include that in please create and deployment goals. I will show it in a second. So you do makeup on and You see it deployed deployment yellow and the provider you can watch here that provider actually code that. Feel it was a ration and submitted beat. So if you do make + +Artur Troian: query did You can see the Obviously the resources offer this is the recent feature from minute 8 and we're ready to create list. So what we do is make these And Chris leaves and starts to the coil. so we can see that it received manifest. + +Artur Troian: the lease is up if you look sitcl + +Artur Troian: Get an ass. To be here and it's not why? yeah, I didn't lose that manifest. That's so we do mates and manifest. + +Artur Troian: It's almost pass and you can see there manifest received on the provider Windows names and completely deploy. So if you do you get them spaces use our lease. In space and you can do Cube Ctrl and that ointment. so it has two Services as you can see one nine new and one train web and you can stay ports and if you have and point there, you can do the proxy and access it with the browser or see URL to close deployments that we do is make the tournaments close and it will shut it down. + +Artur Troian: Sort of completely closely, then you can see the provider actually immediately reacted there on that. So it unreservation and completed turn it down. You can check the spaces. Once again, you can see the reasoning space is gone. So let's say you want to create new deployment this because the sequence one already been used by this key. We need to specify different one. So it doesn't have to be consecutive. It has to be unique just all the time. For this sake of example, we're gonna use the sequence number two. Let's say the sequence to my deployment. Okay, I'm gonna use the same. manifest for that so the sequence tool it created deployment you can see for provider immediately reacted and submitted for humans and submitted bid as soon as we have beat do. + +Artur Troian: sequence to make a list rate that has been done provided is happy with that. And now we do once again the sequence to make money requests and manifest is done. And as you can see the provider completely deployed it and just double checking out. you see how business spaces using your namespace and you can + +Artur Troian: get services Yep, everything is hungry. And once again to pause it the sequence might want to close. + +Artur Troian: That's pretty much it. And to stop the provider into this Ctrl C that control see that and everything is stopped. Yes can go ahead. + +Scott Carruthers: Yeah, I just want to reiterate what you mentioned earlier Archer. So the link that I shared. In the chapter this meeting are detailed notes for this exact process. This is a + +00:50:00 + +Scott Carruthers: Documentation that I link to is currently I'm linking to my own GitHub repository. eventually I'll live on the cost documentation site, but we're awaiting they migration to docs 2.0 what did make sense to go through starting to bring this live on the current platform months or way until it's migrated to Not only this but all the developer documentation that created at the beginning of the year will be there. So Deval or anyone else is you're going through that documentation if you have any suggestions, it's definitely documentation that isn't vetted I think it's very clean and very thorough it just has by many people so clarific Answer additions that we can make please. Let me know. everything that Archer just went through from the creation of the local blockchain to spending up a local validator to creating the + +Scott Carruthers: provider and then also the steps make amends to create the deployment and send the Manifest and all that is detailed in that documentation. yeah. I mean as I let me know if you recommendations on where there could be improvements but should be pretty straightforward to use. + +Deval Patel: Yeah. Thank you Scott. And thank you Arthur for the demo. Thank you very much. + +Tyler Wright: Deval I'm sure you. + +Artur Troian: No problem. Yeah, all right. yeah. Thanks. + +Tyler Wright: Yeah, I was just gonna ask the ball. I know that you may have other questions. I really appreciate that demo and I'm sure we'll do more of those over time if anybody here has any specific topics that they want. Archer Scott Andre or others to do more of a deep dive in and pertains to either the code base or intricacies of using the class Network. Please feel free to message me or throw something in six support so we can add those as potential agenda items. Otherwise again, we do want to leave some time for folks to ask specific questions that are more Technical and give people the opportunity to do that with regularity. developers any other questions that you may have at this point. I know we only have five minutes left before some of us have to run over to Sig providers. + +Deval Patel: No, I'm good. Thank you. + +Tyler Wright: awesome again Archer much appreciate walking through the support repo and any issues that needed triashing. Thank you again to all the Insiders that give support around the clock to new and existing users that are interacting with the cash. I know it improves The Experience so much appreciate All again. Sig providers is coming up in about four minutes where we'll get an update on all the work to pray to our team has done this year. + +Tyler Wright: The kind of a look ahead on some of the things that they're thinking about for 2024 as well as I know that Benjamin is going to be talking more about his pre-draft discussion around an auditor. looking forward to those discussions in Sig providers. But again, thank you very much for joining. We'll meet up again in two weeks. I think after that we might take a couple of weeks off for the holiday. So if anybody has any specific things that need covering let's look to cover those in two weeks, but again much appreciate everyone's time today, and hope everyone has a great rest of the day. We'll talk soon. + +Scott Carruthers: Thanks, everyone. + +Tyler Wright: Thank you. + +Deval Patel: Thank you. + +Meeting ended after 00:53:48 👋 + diff --git a/wg-akash-website/meetings/012-2023-10-12.md b/wg-akash-website/meetings/012-2023-10-12.md new file mode 100644 index 00000000..67e3b436 --- /dev/null +++ b/wg-akash-website/meetings/012-2023-10-12.md @@ -0,0 +1,567 @@ +# Akash Network - Akash Website Working Group (WG) - Meeting #12 + +## Agenda +- New Website Section Proposal: "Development" +- Progress Update on the Website Revamp +- Update Discussions ( Current Website ) + +## Meeting Details +- Date: Thursday, October 12, 2023 +- Time: 6:30 AM PT (Pacific Time) +- [Recording](https://5gn7dg3s3faifxnf6w5uqoabieslbqre2ywps2nyhotoc54tvsiq.arweave.net/6Zvxm3LZQILdpfW7SDgBQSSwwiTWLPlpuDum4XeTrJE) +- [Transcript](#Transcript) + +## Participants +- Daniel Moore +- Denis Lelic +- Emmanuel Arthur +- George Pro +- Tyler Wright +- Zach + +## Meeting Notes +- Tyler provided an update on the most recent version of the revamped Akash Network website. +- Tyler Mentioned of Piyush seeking Docs 2.0 from Luna from the previous meeting. +- Tyler mentioned he has shared the Docs Docker image in the AKASH website working group chat on Discord. + +### Progress Update on the Website Revamp + +#### Denis Lelic: +- Provides an update on Human HQ (Piyush and team) working on the ecosystem page. +- Mentions technical features allowing users to filter deployed projects on Akash. +- Explains the delay in the weekly update on the page due to ongoing work by Piyush. + #### - Content Requirements + - Zach mentioned that Piyush needs content for around 15 pages. + - Denis provided insights based on Piyush's previous mentions and identified homepage as the top priority. + - Denis acknowledged that the homepage content provided by Zach is a work in progress and needs integration into the design. + - Zach emphasized the importance of coordinating with Piyush directly to discuss content requirements, urgency, and potential challenges. + +### Updates (Current Website ) + +#### Denis Lelic: +- Arthur's work on the "get started/deploy" page. +- Integration of Cloudmos and presentation of two deployment options on a single page. +- Denis shares the link in the chat for everyone to view Arthur's work. +- Mentioned that everything is functional, and the only outstanding item is the deployment tutorial. +- Emphasizes the need to find a way to embed the video in two tiles without overcrowding the page. +- Commits to creating mock-up options to determine the best approach to embed the video. +- Assures Arthur that once the videos are ready and uploaded to YouTube, he will be notified for page updating + +### New Website Section Proposal: "Development" + +#### Denis Lelic: +- Denis introduces a new concept called "Development." +- Presents a rough concept where the user can click on "Development" in the menu, offering two options: "Network Development" and "How it Works." +- Mentions including general information on providers, tenants, and options for adding network activity. +- Denis expresses uncertainty about where to integrate this new concept, considering the existing community section. +- Discusses the potential impact on the community page and suggests the idea of freeing up space for more focus on projects and meetings. + +#### Tyler Wright: +- Tyler expresses enthusiasm for the idea. +- Supports the idea of simplifying the user experience. +- Suggests the possibility of having more navigation headers if needed. +- Raises a concern about the delay in updating information from the community repo to the website. +- Proposes working with Piyush and the team to ensure more real-time updates, especially for meeting notes and other relevant content. + +#### Zach Horn: +- Appreciates the concept of the development page and suggests tracking conversions to assess effectiveness. +- Expresses support for the idea of making it easier for people to discover working groups without direct promotion. +- Highlights the opportunity for downstream discovery through calls to action on the website. +- Emphasizes the importance of minimizing clicks for user accessibility. +- Proposes brainstorming ways to visualize the interconnected information, such as using diagrams or visuals. + +### Calendar Module Exploration: +#### Denis Lelic: +- Suggests considering a classic calendar option for a good overview, citing examples like Airbnb. +- Explores the idea of leveraging a familiar user experience from well-known platforms and incorporating it into the website. +- Suggests consulting with Piyush and exploring the possibility of using a plugin to implement a module similar to the one seen on the Adobe Max page. +- Expresses the need to determine if such a feature is feasible within their current capabilities. + +#### Zach Horn: +- Inquires about the literal module, expressing willingness to look into it. +- Mentions Kubernetes as a potential reference for calendar structure. +- Inquires about the feasibility of implementing a module similar to the one observed on the Adobe Max page, questioning if it's within their scope and if it requires a plugin. + +#### Tyler Wright +- Shares insights on how Kubernetes manages calendars using Google Groups. +- Acknowledges the less-than-optimal communication in Google Groups. +- Highlights the shift to Discord as a more dynamic communication tool. +- Proposes the idea of having individual calendars for each special interest group or working group. +- Raises the need for people to easily sign up for specific meetings and suggests having a dedicated calendar for each category. +- Discusses the idea of breaking up content blocks, potentially using visuals similar to those seen on the Adobe Max page. + +### Other matters discussed +- Tyler suggests the idea of posting working group meetings on YouTube to increase visibility and participation. +- Tyler mentions the potential for a better user engagement on YouTube, similar to other organizations like Adobe and Kubernetes. +- Decided to explores the possibility of creating a distinct category on YouTube to highlight working group sessions. + + +## Action Items +- Denis to mock up options for embedding the video tutorial. +- Denis to Notify Arthur when videos are ready for updating the current website page. +- Tyler to collaborate with Piyush and the team to address the delay in updating information from the community repo to the website. +- Denis and Zach to consult with Piyush regarding the feasibility of implementing a module similar to the Adobe Max page on the Akash website. +- Tyler to explore the option of posting working group meetings on YouTube for increased visibility and better user engagement. +- Zach, Denis and Piyush to plan the next steps for implementing content on the homepage. +- Group to explore on how to make it easy for users to sign up for specific meetings. + +# **Transcript** + +_This editable transcript was computer generated and might contain errors. People can also change the text after it was created._ + +Tyler Wright: All right, welcome everybody. To this week's edition of the Working Group for the Akash website it's October 12th 2023. The Akash website meets on a weekly basis Akash website, working group, rather meets on a weekly basis to talk about the current Akash website as it stands today. I mean, there's also been a successful proposal from Piyush and the human HQ team where they're working on a complete revamp of the Akash website. As previously mentioned on a number of occasions Greg Started off this process by creating V1 of the Akash website where it was designed using github pages and designed to be something that can be open source and can be maintained by many members of the community. + +Tyler Wright: in that vein and based upon again, what Greg started Peters and his team are working to Take the Akash website to the next level by structuring some things a little bit differently. So it's easier for folks to contribute, they're adding tailwind CSS. And again they're optimizing some of the pages that Dennis Zach and others have been looking to optimize for some time. I could see Arthur on this call and Arthur again, was one of the first contributors from the community to help with the website. So we want to shout out Arth he'll always have that title of first contributor. And again Arthur has been helping, not only with the current website but we'll continue to help with the revamped website when it's available. + +Tyler Wright: I know Peers who I also want to shout out again represents the human HQ team. He is not going to be able to be here today at the meeting here at the conflict, but did put a message in the discord where again, many members of the Working group for the Akash website, discuss things between these weekly meetings. I'm going to put an update in the chats of the most recent version of the Akash Network revamped website. But without further ado, I'm gonna hand it over to Denis before hand over to Dennis. I know that there's one thing that Bold Panther It was looking for out of the last meeting, which was docs 2.0 From Luna. I've dropped that docker image in the working group AKASH website, chat, so that + +Tyler Wright: Be pierced to this team have access to it and then again, we can start to implement the docs 2.0 into the revamped website. So that was an action item. That was on me coming from last week and after some challenges getting it I was able to get it to him again, have shared it in discord inside the working group AKASH website. Discord channel. + +Tyler Wright: So again with that further ado, I'm going to hand it over to Denis to see if there's anything we want to talk to talk about related to the current website. Or if we want to talk about anything related to the website, read the app. So Denis, take it away. + +Denis Lelic: Thanks Yeah, you're pretty much summarize everything we did. And what happened previously? and thanks for sharing the link for + +Denis Lelic: Human HQ, aka Pierce and his team and to be able to check the recent updates on the website. As far as I know, they are working on the ecosystem page. which has + +Denis Lelic: some maybe technical features there where users are going to be able to Filter all of the deployed projects on Akash and everything that's happening around the Akash and so on. So maybe that's why we're not seeing The weekly update on the page. They probably need some more time to do that, which is Of course, reasonable. And one thing Arthur. + +Denis Lelic: Did last week is the get started, slash deploy. Your ad, where we present two products. One is cloudmose, and a previously. We had two tabs where users were able to switch between those two and now we have one page and two tiles to presentation of those two options to deploy. I'm just gonna, The link in the chat to everyone can see. What Arthur did? So, thanks. Arthur. Here, it's functional works and so on the only thing we owe you is the deployment tutorial. + +00:05:00 + +Denis Lelic: Yesterday, we talked about one option, where we would embed the it's not working. + +Tyler Wright: Maybe it's just me, but I just try to click on that link and I didn't work, so it could just be a meeting. That's why I didn't want to interrupt you. + +Zach Horn: Link Works. + +Denis Lelic: Anyone else has that issue? Okay, it works for… + +Zach Horn: the link works for me. + +Denis Lelic: So I don't know. Maybe try incognito. + +Denis Lelic: yeah, yesterday we talked about an option where we would embed that video tutorial which is in the making at the moment we have automatic 1111 for console and we have another example for cloud nose, and we just have to figure out Away. To embed that video in these two tiles. So we're not messing up everything and making it overcrowded. So I'm just gonna mock up a couple of options and see what works best. So yeah, Arthur we owe you those videos and as soon as they're ready and they're uploaded to YouTube, I'll let you know so you can update that page. + +Denis Lelic: Otherwise. Pretty much covered the progress from the last week. There's one thing I'm thinking about which is still kind of a rough concept. And I'm just going to share my screen. + +Denis Lelic: Here it is. + +Denis Lelic: So at the moment, it's called development. So this part here, + +Denis Lelic: there's also a menu option here In the Menu section here. So when the user clicks development, it's presented with two options. One would be like network development and the other one would be like how Network development is pretty much what we have at the moment with a couple of new things in the sidebar. Where we could? Present meetings roadmap and stuff like that and the other one how it works. is just like an overview of How? Akash network actually works. And we can talk about in general information providers, tenants and there's options to add Network activity, and + +Denis Lelic: Yeah, it's just a rough concept and all of the content here. Is taking out of bosses presentation, a news presentation, Greg's presentation where they talked about how the network works and what are providers, who are tenants and so on. And + +Denis Lelic: a while ago, me and Bob were just talking about how great would it be to Have that on the website. So it's not just Part of some close conversations, close presentation's, but something that anyone who visits the website, I can just read through and maybe it's gonna provide some information. And to provide some clarification for users to see what's actually behind it. And Yeah. What do you guys think? + +Tyler Wright: I love that idea. + +Denis Lelic: The only thing, I personally didn't know where to include it because we have the community section. and if you paid attention community page, is where everything ended up like everything that community wanted or internal team wanted from the overclock kind of ended up there. So just providing some new pages would kind of free the community page where we can focus more on the projects on the meetings. + +00:10:00 + +Denis Lelic: And stuff like that. So, + +Tyler Wright: Yeah, I think to your point, we should be moving some stuff off the community page and even if we have to have more nav headers, unless again, someone like Zach disagrees. I think that. I don't like for the user experience to be a little bit easier so that people can just one or two clicks to this kind of information as opposed to having a click into community page, and from there click into someplace else and just creates too many clicks. While I'm thinking about it and maybe this is something that I'm going to put in working group for the class website. + +Tyler Wright: but on the community page, I think it was their original attention of Greg to have things from the community repo inside the Akash Network organization automatically be added to the website right now, the way that it's being written the information from the community repo, Does not come to the website in any amount of real time there's a great deal of delay. So something I want to make sure that we talk about with Piyush and Team is making sure that again as working group. + +Tyler Wright: As the things get merged into the community repo for meeting notes etc. Hopefully those can get merged pretty quickly into the active website so that anybody that goes to the website and wants to learn more about Diggs and working groups can have the most up-to-date information as opposed to a dated experience. So that's something that I certainly want to work on with peace and for future meetings. + +Denis Lelic: Yeah, yeah. I agree. Zach, you have any thoughts. + +Zach Horn: I think this sounds great and I think one of the biggest things we need to do right now is make it easier for people to discover our things and working groups, without promoting them directly because I think we've exhausted the direct promotion we can do. But I think there's lots of downstream opportunity for people that are coming through. our calls to action when they land on the site that they might discover those groups and want to participate. So anything we can do to closer to the top level of the website the ties point about multiple clicks I think is good. Outside of that, I do like the idea of the development page in general because One thing we can do as we start building this out and getting, our analytics all the way set up is start tracking how we're converting on this pages, which would be interesting to me, if we start trying to drive traffic to them directly in blog posts and other assets. + +Zach Horn: Would you mind Denis real quick just zooming in on the development page? + +Denis Lelic: So, one thing I have to mention, why we don't have dropdowns in the menu is something that Greg didn't like and he tried to avoid it. But as the website grows, we're kind of keep adding stuff here. And Sooner or later we're gonna have to think about adding a drop down or something, for example. That's why. When you click Development, You have two options one. The other option would be like development and you click down or you just hover and then you're presented with these two options. Now you have to click this page is going to load and then you see, okay, network development, how it works. So network development, Is this thing? + +Denis Lelic: So we have the product strategy, community groups, current projects meetings Roadmap could actually be part of the other one. Or this one so because it's kind of overlapping. But did you had any question or something like really specific you wanted to see here? + +Zach Horn: No, I'm just taking it all in. we don't have to reinstall right now but One thing that has jumping to mind when somebody lands on this page is that we make it really easy for them to understand what they're seeing. I don't have a super great suggestion for that right now, but we can definitely brainstorm on that. Maybe it's something like a visual or a diagram or something like that, just something to visualize how this stuff all interconnects and Maybe it looks like a quick start or a summary section towards the top, just something to say, Okay, if you want to, what is Akash where we headed? maybe it's just as simple as a roadmap diagram. That just gives them … + +00:15:00 + +Denis Lelic: Yeah. We have. + +Zach Horn: where we are. And what's coming soon. + +Denis Lelic: We had a roadmap somewhere here. This is the latest one. So we had the mainnet 6 and… + +Zach Horn: + +Denis Lelic: the GPU and Multi currency support. So we are basically here. And there's another updated version of this, which pause I created for bus, but anyway, + +Denis Lelic: yeah, so I agree, we could kind of visualize This thing in a better way. And you're + +Denis Lelic: yeah. I'm just thinking, is it part of + +Denis Lelic: This community development of the project or is it about Akash or which is basically how it works. + +Zach Horn: Yeah, that's a good question. So on that product strategy and execution, I think that was the page that you're just on. + +Denis Lelic: Yeah. + +Zach Horn: What is the? I'm just reading really quickly. + +Denis Lelic: This is something that's on the current website as well. + +Zach Horn: So, this is that document, that lays out the entire product strategy. Right. Okay. + +Denis Lelic: Yeah. + +Zach Horn: I think this is great. I mean, it's obviously a really really build out document that gives people everything. + +Zach Horn: Summaries and high level. points would be something I would look to pull out of this. Could I just + +Zach Horn: It's something that maybe we can make a little bit quicker for people to consume. That would be My one immediate thing you go back to the top of that page real quick. + +Denis Lelic: And there's one thing like AI ml Workloads is at the bottom, maybe we could. Talk about that sooner in the upper section. + +Zach Horn: what tab is? I'm on my laptop screen so everything's a little small over on the left side. this. Document is under community groups. + +Denis Lelic: One can. + +Zach Horn: Right. Okay. + +Denis Lelic: So I'm just gonna share a link here. + +Denis Lelic: So, this is core groups and pro products that strategy, and it's pretty much the same content as on the current website. + +Zach Horn: Got up, okay. + +Denis Lelic: the way it's structured as you see those tabs on the left, + +Denis Lelic: it's just offered right away. There's no need for one, click on the Core Community groups and then a second one for the current groups and the current projects. And so on you basically just click through Strategy Groups Projects, Without additional drop-down menu. + +Zach Horn: The got it, okay? + +Denis Lelic: And then, of course, we have the Community contributions and insiders and Akashi edu. which, Could be part of the, classic not Community Development page, which kind of goes into different directions, still close to each other but + +Denis Lelic: I have a feeling like we could separate that just to provide a little bit more clarity and for users to consume all of this information. + +Zach Horn: Yeah. Yeah, that makes sense. + +Denis Lelic: because if we're talking, if we have a look at the community page, We have contributions so we can have I don't know, an article from George, Arthur, Robert Pierce. And so on and we can have events so we can post photos there from the recent conferences, for example. We could have. + +Denis Lelic: Bounties maybe, but still Bounties could be up here. + +Denis Lelic: And then we have Akash insiders, maybe a contributions board, where we list all of the recent contributors and we can pull that data from GitHub, whoever created a PR and we can just list those people here. + +00:20:00 + +Denis Lelic: Of course, The upcoming events for example. + +Denis Lelic: here we have cosmovers I'm sorry and we can include others as well. And of course we can provide a link for a car swag shop. This is more into. Community and community building and events and everything that's happening. And it's kind of like connecting with community and the other one would be still community but I would call it differently like development or something, because it's more focused around the projects product meetings and six working groups. + +Denis Lelic: Like roadmap, what's into plan? Or which meetings are happening today this week and so on, + +Zach Horn: Yeah, I'd like the vision of it. I think one of the things that Paige could do really well is This is just my theory. but that when developers come to Akash, If they're deciding where to spend their finite time and skill and all that they want a quick way to see Okay where are you guys like? What can I work on? what's the workflow? And this feels a lot like what that page would be, it's like Wait for developers just land to be like,… + +Denis Lelic: Yeah. + +Zach Horn: Okay I see where the project is today. I see what you guys are working on. They can get a quick overview of public working groups and all that. And then decided whereas the best place to jump in as we're, So if I'm thinking out loud, Developer lands on the development page. what's the top level page? They see when they hit that button in the NAV. + +Denis Lelic: so, the first starting from the homepage, You have development. + +Zach Horn: Yeah. + +Denis Lelic: And then you're presented with two options. One would be like how it works or about Akash or something. And then we talk about these different tenants general information network activity maybe pricing and then we have Something that I still don't know how to call it, but it's + +Denis Lelic: network development and everything. That's happening around the projects meetings working groups CIGS and so on, but I just don't find the right wording for it. So I know you're gonna do a better job than me here. + +Zach Horn: We can definitely iterate on that. So if they click through on network development, where do they go? + +Denis Lelic: Then they're presented with this product strategy,… + +Zach Horn: God, + +Denis Lelic: community groups, current projects meetings roadmap, we could add bounties here. We could add. Governance propo Guidelines here. + +Zach Horn: Okay, so okay, I see now. So The flow The UX of all this looks great. I see Greg's position on the dropdowns of the Nab. I also see your position that maybe it just be easier. If this was a drop down the nav and not have the Intermediate landing page where they have to see that. + +Denis Lelic: Yeah, this one. + +Zach Horn: It might also be good to have it. I could see that I'm here nor there on that but + +Zach Horn: So they land on the page, that drops them on product strategy. So, We have a content, not problem, but we have a content opportunity. We need more content for that page and probably a high level page that gives them an overview. Because I can imagine a developer landing on that page and + +Zach Horn: maybe not wanting to dive into all of the information. So they land on something that's like an overview page that quickly is here, I'm just thinking a lot, top three initiatives. Here's what we're working on in the next couple months. If you wanted to jump in today, here's where we need developers currently. + +Zach Horn: And then here's our second working group structure. And probably those things would be connected. So it's like, if you want to contribute to X, here's the working group the corresponds to that. So, here's the next meeting. Etc. Etc. So it's a quick start guide almost like, Here's what contributions. in this direction. Here are associated bounties here. The working group. That's the info. I think that a developer would need it, they land. And when I get started right away, + +00:25:00 + +Denis Lelic: So we need something which is Get started with Akash which presents options for becoming a provider deploying or just joining a community. So here we need something to get started. With your user's contribution or community members contributions. + +Zach Horn: definitely. Question for you. And we can sink offline if this is out of scope for now. But is there a way to show the calendar? On the website in a way, that's embedded without slowing things down and causing a bunch of problems. + +Denis Lelic: I think we could provide a list of + +Denis Lelic: of meetings. And then we could add a filter option, weekly monthly. so, we have Basically a button like a drop-down where you just switch between Show me, daily meetings, weekly meetings, monthly meetings and we basically just list them. + +Denis Lelic: Maybe something in this form. + +Denis Lelic: let's say this is working group. + +Zach Horn: Yeah. + +Denis Lelic: Our website. And then we have a small intro and add to calendar. + +Zach Horn: I see so it's not embedded, it's not programmatic, it would just be static content but we could still outline what they are and then have the Add to Calendar button, okay? + +Tyler Wright: We could because dar is a Google calendar with all the working groups in special interest groups. We could theoretically, just embed the entire calendar into the website. I do like that. I like Denis what you're putting forth, but I do like, The Zach's point of having more visual elements site wide. But specifically here something that people to look at and be like, all right, Monday Tuesday, Wednesday and no, + +Tyler Wright: And yeah and no. … + +Zach Horn: Yeah. that was my thought,… + +Tyler Wright: all right, cool. + +Zach Horn: is that when somebody's coming in, they just want to quickly, see what's coming up this week or next week, does that am I gonna be available all that? + +Denis Lelic: That sounds good. I'm just making notes. So that's something we can discuss with peers as well. And just explore different options. + +Zach Horn: Sure. + +Denis Lelic: It's either providing a list. + +Denis Lelic: Just having a good overview but I'm just thinking from other projects. What's out there? + +Zach Horn: Yeah, I'm definitely flexible on how it gets implemented. just my initial thoughts on this. I think that the high level goal is just to make these things less opaque because I feel like they may be a little opaque right now. If you're not already first where the stuff is, and how it happens and all that. + +Denis Lelic: Yeah, I for sure agree. We need to improve that Just to find a better form to present meetings, working groups, maybe we encourage people to join. And we'll just have to explore what's possible here. + +Zach Horn: Definitely. + +Denis Lelic: they have, just maybe something to think about. An example, it doesn't have to be like a Web 3 or something. I'm just thinking a classic calendar option where you can with a good overview, maybe like airbnb or something, or skyscanner or something. That's Out there that's familiar to users that has a familiar user experience and something that we could leverage maybe and just basically copy and put it here. + +Zach Horn: you mean the literal module? Yeah, let me take a look. The + +Zach Horn: so, if you're thinking about website flows and all that, obviously The airbnbs of the world are. Super smooth. The thing that is. So the one that always comes to mind is + +Zach Horn: Not for a calendar module, but Kubernetes in general because they have a similar working structure. I wonder how they do their calendar and that's what I'm looking for it. + +00:30:00 + +Tyler Wright: They do Google groups. obviously Kubernetes is out of Google and… + +Zach Horn: Do that, okay. + +Tyler Wright: so when I originally started and this is something I tried to basically copy early on when we're doing this open model, they do Google Group. So each stick and working group is a Google group and so basically they're individually maintained. So when you sign up to George, go to a meeting, you're only signing up for that specific Google group, they have conversations between meetings in that Google group. I think it was less than optimal. and where I think maybe not discord specifically but I discard tool beat it is just like it allows for more constant communication where I feel like we're falling short right now is I have everything in one Google calendar. and so it's either people can download everything or nothing and so it's about thinking art does each + +Tyler Wright: Special interest group or working group need its own specific calendar. So people only signing up for that and they're only getting added to a specific kind of meeting. Theoretically right now You can do that by just messaging me and be like, Hey I want to be added to only the working group for the Akash website and I can add you directly to the invite but people aren't taking advantage of that. So we got to think of That People can easily click and just have it and have one, maybe specific special interest group meeting, which I think is less likely. But at the very least have one special interest group category that they can kind of sign up for if that makes any sense. + +Zach Horn: It does make sense I'm looking at Kubernetes right now. That's their community group age. It's very, very similar to our current version. + +Zach Horn: I'm trying to sign up for a meeting right now just to see how they do it. Okay, so they use zoom links directly. So if you go to that page and you click one of the meetings like Thursdays at 10 am Pacific it literally just launches you right into. + +Zach Horn: that's good context. I think we probably need to. Maybe find a different way to do it. The Kubernetes is obviously, but a bigger than we are. But + +Zach Horn: It's good to see that they do it, as simply as that. + +Tyler Wright: Yeah, that's one thing I was actually thinking about doing was having the next meeting be at the top of the Readme file and people would just click right into Google, but because I'm only one person a Neil and others were like, We can't do that at scale, we can't do that for meeting every week. + +Zach Horn: Yeah. + +Tyler Wright: Which I don't know if I agree with especially if I have support from folks like George Pro and others, But again we decide not to go out direction the short term. + +Zach Horn: Sure yeah my high level point on scalability and all that as we may need to do things that don't scale until we reach scale but yeah I don't strongly disagree. + +Tyler Wright: Yeah, I like that and I think that makes sense. + +Zach Horn: Yeah. + +Denis Lelic: Yeah, I think this is a good example. I saw it a while ago, but I kind of also, some of the other content that provided care, code of conduct and stuff like that, which I'm seeing, we could have. A menu option here for. Governance Proposal Guidelines And stuff like that. But because I'm a designer, of course, found another example. which is this one and I kind of like This module here. Which is upcoming. and you can present three options that are happening today, and the others could be just Sessions all sessions and you can filter them just like Kubernetes Has it there. + +Denis Lelic: and we can just provide a headline, a short description, the time when it's happening, and a button to So, either Join or to add to calendar. + +Zach Horn: that this looks great and, no disrespect to the fine folks of Kubernetes but this is definitely a bit better designed + +Tyler Wright: I would agree with that. And again, I think I kind of said this three minutes ago. part of me for saying it again. But I do want to echo Zach's point. I did put a plus, 100 in the chat. I love the content on the current website. I do think that there's way which we can break up the content with some more visuals. I know that we want to be content heavy but I think Zach made a good point of even if it's big things up a boxes or similar to what we see on the page with Adobe Max here. I think we can do a better job of just breaking up content blocks so that it's a little bit easier to digest. + +00:35:00 + +Zach Horn: Yeah, definitely. + +Denis Lelic: And they have a great calendar actually here. + +Zach Horn: Yeah, this is very good. + +Tyler Wright: Yeah. + +Zach Horn: I'm taking it all in right now. What? filter by day and then by the Segment of meeting, and then each meeting is on its own track with the time. + +Denis Lelic: Yeah. + +Tyler Wright: I love this and hard You can add to calendar. do by region,… + +Denis Lelic: Yeah. + +Tyler Wright: we wouldn't have that necessarily but we can do it by Kind of SIG or working group or something, + +Denis Lelic: Yeah, and then you have details details for each of the either working group or six. + +Zach Horn: Yeah, this is excellent and if you go back into any of the meetings into that meeting detail page. It calls out the featured products that they're going to talk about which in our world could be roadmap initiatives that are being worked on. So you could filter that way as well. this is very good. + +Denis Lelic: Yeah, I like this one. It's kind of easy to track for what's happening for example today. And there's filtering options. + +Zach Horn: And you get localization, too. Wow, that's a little ahead of where we are, but yeah. I'm always thinking down the line like that. If we get to have meetings in different regions,… + +Tyler Wright: Yeah, we do need. + +Zach Horn: that would be excellent. + +Tyler Wright: Yeah, that would be amazing. I would even say before that we do need and discord does a good job of that right now but I do think we need timing localization. Because again, we have people all over the world even right now and so when meetings get assigned they see Potentially. it's gonna be nine, am Pacific having to do that math all the time. It's kind of sucks for people. But if it just localizes for them then that would be I think ideal + +Denis Lelic: yeah, even for the past meetings, for example, If you would go to the previous day you can just watch on demand and you just click and watch the recording? Yeah, we're kind of working only dreaming. + +Zach Horn: Yeah. + +Tyler Wright: Yeah. + +Tyler Wright: Yeah, exactly. switching 90 links per day, I'm about it, + +Zach Horn: A Denis. Could you Click View on one of those videos? I'm just curious what the actual player module looks like. So it's synthetic YouTube, okay? + +Tyler Wright: Yeah, I love the + +Denis Lelic: Yeah, something like that. + +Denis Lelic: or at least, just I don't know where it is, but if I saw it somewhere, + +Denis Lelic: At least having a detailed page for the sake or for the working group. Something to explain Who's the leader of a certain group or something like that. + +Tyler Wright: I are we as a tool? But I do wonder if we posted The working group meetings on YouTube if that would cause more people to know, they exist and then participate. I mean, if Adobe's doing it, I know Kubernetes is doing, or maybe the Kubernetes using zoom, but I know that other organizations are like, all right, they keep the content alive on YouTube, really going anywhere. and then it lets people know okay, I can watch these meetings without having to go to Github. And, yeah, I just think it's maybe a better experience, but + +Zach Horn: The UX is definitely better. My only thought on that is For something like Adobe Max. you can see these videos they're very produced. It's not a,… + +Tyler Wright: Yeah. + +Zach Horn: I'm not opposed to putting them on YouTube. I do, We really have to think a little about how that blends in with our other content though. Because they're working groups so they're not produced, but + +Tyler Wright: Yeah. Yeah I think that's a good point Zach. I was thinking maybe making its own category again, people just know they exist because slide it down but again we're not doing it right now. I'm not saying we have to do it anytime soon but I wonder If enough people come to YouTube and be like, wait they have these working group sessions with a talking about things and I'm interested in and maybe they would watch that faster than they would watch it via the read me and go to. Are we etc? + +00:40:00 + +Zach Horn: Yeah, I think that's definitely true. + +Denis Lelic: yeah, we could try and see + +Zach Horn: For sure. + +Denis Lelic: the Kubernetes. + +Zach Horn: so, obviously this is a very built out module lots of development and Lots of stuff happening behind the scenes for that. Adobe Max module, excuse me. + +Zach Horn: What is within our scope to do something? Even close to this direction? Is this possible for us? + +Denis Lelic: I mean we would have to talk to Pierce and… + +Zach Horn: Would it? What do you think? + +Zach Horn: Yeah. + +Denis Lelic: to see If this is, Maybe some sort of a plug-in. + +Denis Lelic: That we can use. If it… + +Zach Horn: + +Denis Lelic: would be great. So, just having a look here, + +Denis Lelic: If it's a plugin, it's great. + +Zach Horn: Yeah. + +Tyler Wright: Yeah, maybe we can either talk about this next week or drop it in discord and What? Piercings, that? It sounds like this is the Perfect, inspiration for us as late at least the highest level. Of what we like and maybe we can do some sort of version of this, possible. + +Denis Lelic: Yeah, I mean and what would be here then? working groups and six. + +Zach Horn: Probably the categories of what they fall into is the first thing that comes to mind. So could be website,… + +Denis Lelic: Yeah. + +Zach Horn: or network or something. Whatever. + +Denis Lelic: Yeah. + +Denis Lelic: It's good. + +Zach Horn: Yeah. Yeah, good find. + +Denis Lelic: I'm gonna have a look at maybe a different conferences. And if someone is using something that we could use as well, some sort of a plug-in or maybe it's like an open source solution or I don't know. We can hope for so we'll see. + +Zach Horn: Sounds good. + +Denis Lelic: And that's what live Here the right window. + +Denis Lelic: and this would live somewhere here under network development or some whatever we're gonna call it later. And we could provide that in the overview upcoming Meeting sessions, whatever. + +Zach Horn: Yeah, that makes sense. I like the development page a lot. I think we should Thank Richard, move forward with that. Definitely if you should. On board. + +Denis Lelic: yeah, and then we couldn't then we have space just dedicated for community and community contributions the proper community page where we're not talking about project and project building But just more, connecting and events and kind of the More loose version of that. more relaxed and I hope I made it clear. And I lost. + +Zach Horn: Yeah. + +Denis Lelic: I spent all of my English vocabulary. There's a limit limited characters per day and I guess I lost them all. + +Zach Horn: That's funny. you're on the free plan, you get limited use it. + +Denis Lelic: And I'm in a minute or so there's gonna just be a button to pop up like upgrade now. + +Denis Lelic: And about Page. This is something we could play around. I just grabbed those presentation that are floating around. And something basically just to cover from a high level what Akash is and how it works. + +00:45:00 + +Denis Lelic: yeah, I think that's something I personally wanted to discuss and to see your guys opinion on But thanks for the feedback. I wrote down some notes, and I'm gonna try and see what can we do here, especially, with this module for, and the overview page and how to Provide. More engaging content. Including the calendar and visual stuff you've mentioned. but, + +Zach Horn: Sounds good. I'd be interested, as well, as to hear what that calendar module. Looks like in terms of getting on the website One thing really quickly. + +Zach Horn: Piyush mentioned last week that he's in need of content for several pages. I think it was like 15. we can reach out to him directly and just see from him, but from your perspective, Denis what is the prioritization on those pages which ones are needed? Most immediately? + +Denis Lelic: Last time he mentioned I made notes so just one second. homepage would be the Priority number one. and then we have + +Denis Lelic: The token page. I think just one second. + +Denis Lelic: And pretty much The. Rest of the pages. + +Denis Lelic: Working on, for example, the Akash ecosystem page. We don't have much content here because we're just listing the projects that are currently living in the air table. And so, yeah. The first one would be the home page which you already provided some of the content. But I see you've marked it as a working progress. So some of it, it's not applied into the design yet. So whenever you have time, have a look at the homepage for example, and then we will take it from there and Find. What are the next steps? + +Zach Horn: Got it, that sounds good. Hey, Welcome. + +Tyler Wright: Go ahead, Daniel. + +Tyler Wright: Then your mic is on, you're not muted but we cannot hear you if you're speaking. + +Tyler Wright: sure, as to why Daniel. + +Zach Horn: You may be audio issues, Daniel but feel free to type in chat if the mic isn't working. + +Tyler Wright: Yeah, if you can hear us this is a working group for the Akash website. Again as previously mentioned this working group meets every single week of anybody from the community or anybody that cares about Akash Network wants to join and contribute. They're more than welcome, this working group is happening in two phases. There is a current website right now, which I'm sure you've seen access or you've seen network. There are some small changes being made to that website. And then there is a team that's successfully. Got community funds to develop a revamped website, that's built in Tailwind CSS, and it's going to be optimizing gonna have some more of the pages that have been discussed by this team right here. And that's being worked on right now by Push and his team. And you can kind of see the updates here. So again during these weekly meetings, we talk about various pages that need implementation or need design development, or copy development, from folks like Denis Back and others as well as + +Tyler Wright: where we are with the current revamp and making sure that again, it's optimized for folks so that when it goes live in a month or so it's a kind of user experience that everyone's looking for but Daniel we would love your contributions whether it's today or a future meetings. So feel free to jump in to discord and give any feedback, thoughts questions concerns or again, feel free to join these meetings and you're more than welcome to talk. I know you still have your hand raised. Have you been able to fix the audio issues at all? Daniel can you hear us at the very least? Can you give us a thumbs up if you can hear us? + +00:50:00 + +Tyler Wright: That's all right. again Daniel if you or anybody else on this call or who's listening to this, when the recordings made available, once wants to feel free, to join any future meetings, that happen weekly at 6:30 am Pacific on Thursdays, or again, feel free to get involved via SIG design or the working group for the Akash website. This will throw a message in discord and then again, we can make sure that your messages are heard and added to the agenda. Or again, you can join future meetings and contribute live. I do want to shout out George who've been helping out with note taking for this working group and some others. So again, thank you George for your help there. And we'll continue to again, merge, all the work that you're doing behind the scenes again. Just reminding you to update the readings as well. + +Tyler Wright: Daniel I don't want to cut you. But again we finished at 6:30 am Pacific on Thursdays every week. Yes, Daniel. And then again, addition at that time doesn't work, we can adjust that time. But again, we do have folks everywhere from the West Coast to Europe, New York Africa, so it's like India so it's like, folks all over the world and so 6:30 a.m. Pacific with the best time for everybody. I know it's like night for Denis. I think it's night Very late for folks in the end early morning for folks in America + +Tyler Wright: But again, if you have any questions, thoughts, etc. Feel free to drop those in discord where, again, we stay pretty up to date. You can see messages from push as recently as today and others? And you can again look at the current website. Leave notes, you can look at the website, revamp and leave notes and again, continue to contribute. It also be great Daniel if you could throw in a little bit about yourself and there, I know that Denis myself and Zach are from the Core team and Overclock Labs. George Pro is an insider based in Africa, and I think he's going to be coming to America soon for graduate school. Shout out And then again there's a couple of other members that are software engineers and web developers base all over. + +Tyler Wright: Anyone else have any Comments concerns before we wrap up this working group or cash website session? + +Tyler Wright: again a much appreciate everybody's time and discussion today we have a lot of next steps. Again, we can continue to talk online. Daniel, it'll be great to have you at future meetings or just again at the very least contributing in discord we're always looking for more folks that are interested in Shadow shout out everyone here again. We'll have another meeting next week and we'll continue to work in the meantime. So please let me know if you need anything, there will be a SIG analytics monthly meeting happening at 12 pm Eastern time, 9 am Pacific. But again, shout out everybody here and let me know if you Eating place, you can reach out to me. Tyler Core team and discord if you need anything else. Hope everyone has a great rest of the day and we'll talk online for Appreciate everyone. + +Zach Horn: Thanks, Kevin. + +Denis Lelic: Thank you. Bye-bye. + +Zach Horn: Thank you. + +Tyler Wright: All right, bye. + +Meeting ended after 00:54:10 👋 + diff --git a/wg-akash-website/meetings/015-2023-11-02.md b/wg-akash-website/meetings/015-2023-11-02.md new file mode 100644 index 00000000..6d36f59e --- /dev/null +++ b/wg-akash-website/meetings/015-2023-11-02.md @@ -0,0 +1,569 @@ +# Akash Network - Akash Website Working Group (WG) - Meeting #15 + + +## Agenda +- Website Revamp Progress +- Discussion on Website Revamp: + - Docs Integration + - Get Started Page + - Community repository integrating workflow + + +## Meeting Details +- Date: Thursday, November 02, 2023 +- Time: 6:30 AM PT (Pacific Time) +- [Recording](https://5yiuwpekrvtf2cbtg7nlfoox2nccndvl5iydxvqzbv2ppfyomvia.arweave.net/7hFLPIqNZl0IMzfasrnX00QmjqvqMDvWGQ1095cOZVA) +- [Transcript](#Transcript) + + +## Participants + +- Denis Lelic +- Emmanuel Arthur +- Piyush Choudhary +- Tyler Wright +- Piyush Choudhary + + +## Meeting Notes + +### Website Revamp Progress + +##### Denis Lelic +- Mentioned a discussion on cosmetic changes and UI polishing. +- Focused on using the latest Tailwind components to avoid previous issues. +- Denis had a question about the impact on build time when hosting the website on Akash Network. +- Denis requested Piyush for a short update on the progress made on the website. + +##### Piyush Choudhary +- Piyush dropped the link in the chat for everyone to see the live website. +- Significant progress reported on almost all pages except for docs. +- Docs page to start after receiving approval from the group. +- Minor design changes to be made based on Denis's directions. +- Real-time APIs are being implemented for the open metrics, and other real-time data updates every 10 seconds. +- Piyush explained that the build time would likely remain the same when hosting on Akash Network. +- Raised concerns about the feasibility due to the need for frequent updates to the Docker file and SDL file on Akash Cloudmos. +- Provider page also being worked on, with two audited providers already on the live website. + +### Docs Integration + +##### Denis Lelic +- Mentioned a discussion on the integration of the docs page. +- Noted the transition from Hugo to Astro, with Piyush and his team taking responsibility. +- Aimed for a longer-lasting and better user experience. +- Emphasized the importance of gathering crucial touchpoints in one website. + +##### Tyler Wright +- Tyler expressed the importance of considering the structure and frontend elements, particularly the sidebar, in the migration process. +- Emphasized the need to reference the existing structure and mentioned Greg's preference for it. + +##### Piyush Choudhary +- Piyush suggested asking Luna's team to deploy the structure to make it visible for reference. +- Mentioned ongoing work on the official website and proposed collaborating with Luna's team on the migration. + +### Community Repo Integrating Workflow +- Piyush explained that the displayed content, including meeting notes, is generated from Markdown files. +- New notes can be added or updated in real time by modifying the relevant Markdown files. +- Clarification sought by Tyler about the process of updating notes. +- Piyush clarified that updating the Markdown files is done within the website repository. +- Tyler inquired if updates also pull from the community group repository. +- Piyush confirmed that updates are specific to the website repository and offered to discuss the details after the meeting. + +### Inquiry about Pricing Page Design +- Zach praised the inclusion of tools for budgeting and expressed their significance for marketing purposes. +- Zach inquired about the design of the pricing page for hosting on the website, expressing the need to share it more broadly during external communications. +- Zach inquired about the real-time nature of the data and how it is queried. +- Denis shared a Figma drawing of the pricing page, explaining the two stages for calculating prices, including GPU options and a comparison to other cloud providers. +- Piyush explained that the Pricing data is real-time and dependent on Cloudmos APIs. +- Piyush mentioned an issue with the GPU part, as it's not implemented in Cloudmos's price calculator. +- Denis acknowledged the concern and explained the two options, one with GPU included when possible and one without for now. + +### Launch Strategy and Walkthrough Video +- Zach suggested recording a video tour of the website upon launch, showcasing its various features. +- Zach inquired about the timeline for the website launch. +- Piyush provided an update on the timeline, stating that the functionality part would be completed within a week or two, with final design adjustments to follow. +- Mentioned potential blockers related to content but expressed confidence in a three to four-week timeline. +- Denis emphasized taking the time to ensure everything is working and looking as intended before the launch. +- Tyler suggested considering testing strategies and planning for a walkthrough video to highlight the website's features. + +### Other Matters Discussed +- Tyler brought up Anil's suggestion to use a visual roadmap and inquired about embedding GitHub project boards. +- Shared the link to the GitHub project boards in the chat. +- Piyush expressed the need to check the GitHub API to determine if embedding project boards is possible. +- Tyler reiterated Anil's preference to sunset the old project list in favor of the new one he shared in the chat. +- Piyush confirmed willingness to explore embedding the GitHub project boards on the new website. + +#### Twitter Image Previews +- Denis raised a question regarding Twitter image previews, expressing the need for multiple images based on the content shared. +- Piyush acknowledged the need to explore Twitter's handling of links and image previews to determine if multiple images are possible. +- Zach suggested using graphics as social images for blog posts, incorporating some version of the headline in the graphic, and establishing a universal standard for post graphics. +- Proposed adding a label or badge to the graphics to quickly convey that it's a blog post. +- Denis agreed with the suggestions and expressed a willingness to explore the implementation. + + +## Action Items +- Group to discuss testing and launch plan for the new website in the next meeting. +- Tyler to collaborate with Piyush to understand and clarify the update process, especially regarding the community group repository. +- Piyush to collaborate with Luna's team on the docs migration process. +- Piyush to investigate the GitHub API to determine if embedding project boards is feasible. + +# **Transcript** + +_This editable transcript was computer generated and might contain errors. People can also change the text after it was created._ + +Denis Lelic: Hey everybody. Welcome to today's working group meeting for Akash website. We meet every week on Thursdays where we discuss. everything website related from content design and for the last couple of weeks. We've been working on website revamp. We got designs ready and we're discussing. + +Denis Lelic: Weekly updates with piyush and his team. They got a proposal. I think one and a half months ago. At least what's appears told us yesterday on the Syrian Community where he presented? + +Denis Lelic: Couple of pages and the progress there. They're making on the website. + +Denis Lelic: But for today's agenda, I'm not really sure where the start since piyush is not here to check on the update if anyone has that link of his I think it's been the same all the time. Please drop it And the chat section here. + +Denis Lelic: One thing we would like to discuss is the docs page integration where we had previously had a different team Luna and quo search starch. team Health transitioning dogs to who go and now since we're switching from Hugo to astral build piyush and his team are going to take care of another transition and hopefully it's going to be one that's gonna last longer. We're hoping for a better experience. and basically to have all of those crucial touch points gathered in one website. So I've good cohesive experience + +Denis Lelic: starting from docs ecosystem page, which is currently not part of the website and it's hosted somewhere else. + +Denis Lelic: yeah. That's about it a short retrospective and the current. Things we're working on me and piyush talk yesterday on. a couple of cosmetic things just polishing UI making sure we're sticking with Tailwind components + +Denis Lelic: me personally, I'm gonna try to make sure we're using the latest components. From the Tailwind Library we had some issues Console as everyone knows so I don't want to repeat that mistake, and I'm just going to keep an eye on those things, so they're implemented properly. + +Denis Lelic: Hey piyush. + +Denis Lelic: Hey piyush. We are already starting a meeting. But you didn't miss much just a short introduction… + +Piyush Choudhary: Yeah. + +Denis Lelic: if you would like to present. I know we talked yesterday during steering committee, but Maybe just a short update on the progress you've made on the website. Could you please drop that link of yours in the chat section? + +Piyush Choudhary: yeah. + +Piyush Choudhary: So yeah, I dropped in the link in the chat to see it live. So we have made a significant progress on almost all the pages except dogs. So we will be starting the dogs after getting a green signal. So I think they were certain discussions my own so I will chat. But that is to find those things on our dogs and then we will start. The dog space as well most mostly rest all the things are mostly done only they'll be some minor changes to the design as per the directions defined by Denis and we'll be looking for those. so the progress is good. And also we are implementing the real time apis. So it was still the real. Nuclear motor for the page. You see the open metrics. These are all real time. + +00:05:00 + +Piyush Choudhary: the data is being updated every 10 seconds that is best from the one you have and then we'll be implementing rising and network activity page. So it's real time data, of course, so we see the darkness and then we also have a provider page and Akash system, which will also have that to audited providers today. It's on the live website. So yeah, that's a + +Denis Lelic: Sounds good. I know you had some blockers from last week and week before that regarding content. + +Piyush Choudhary: he + +Denis Lelic: Is there anything that's not clear enough? Or blocking your progress. + +Piyush Choudhary: so we have implemented most of the condom you proceed. I want to development page. We saw that in the file and they get the welcome and Community groups always bring a spine but I need updated content on for these three pages sages wgs and ugs and I saw that There might be some work groups as well. Let's say there are total 500 overview. So + +Piyush Choudhary: yesterday I was seeing that an answer was presenting a momentum file related to sigs or dedicated sizes as well. So I think it would be good if we can create some MD files for a particular side you update or let's say there is a signal light X, So again, it's going to belongs to the Sig so we will have the meeting links and all Etc. Then what we can do is we can have the sub section. So all dedicated sigs. Let's say seeing light it's so we have second this. Then we have seen documentations lines. I mean those amplifiers we can have the latest update and latest Etc and the leadership and the team who is working there. + +Denis Lelic: Yeah. Tyler go ahead + +Tyler Wright: No, this looks beautiful. The only question I was going to ask is as new notes get added and updated will this update in real time? + +Piyush Choudhary: If so, basically what you are seeing here, let's take this. This is the meeting link, So this is nothing but md5. So if the new not needs to be added you just have to add you lines to them before and it will be updated in real time under website. so Basically as long as the markdown files are getting changed in the record,… + +Tyler Wright: Does it pull dark do I have to update? go ahead. Sorry. + +Piyush Choudhary: everything will be updated in here then on the website. + +Tyler Wright: Okay, and just for simple clarification sake when you talk about updating the MD files you're talking about in the community group repo or do we have to do something inside the website repo? Okay. + +Piyush Choudhary: website River So it's all a part of a website that you are soon. + +Tyler Wright: Okay, previously. I think that the website was pulling in data that happens in the community group Repro because again, I update all the notes of community group repo. I would have to figure out with you offline how You imagine Is it updating notes in two areas? That is the goal or how do you see it? Yeah, that's Emmy and… + +Piyush Choudhary: If Yeah,… + +Tyler Wright: we have to talk about this right now if you don't want. + +Piyush Choudhary: so basically What's Happening Here is let's say I'm on the development base, So there is a development folder inside the content if I go here. + +Piyush Choudhary: So these folders are nothing but this folder contains all the containing log down files. So even if you are seeing let's say the home page. So whatever you are seeing on the homepage the text and everything is coming from the Northbound 5, so you don't need to be equivalent to change the wings. So you just have to come to this model file and just add it the links or text whatever you want to let's talk about the development page. So this is what the development page is. Let me go to the point of the game. So I'm on the development is right. So this is the development page. So basically What's Happening Here is we have + +Piyush Choudhary: we have five sections as you can see welcome current projects for website and boundaries and similarly. We have all these things like welcome strategies current projects Community groups boundaries. So let's say I want to make a change to the Sig so it's nothing but among down file from which the data is coming. So I like which so I go to Community groups and I have the special interest groups as AGS and I just have to change the model as you can see. I just have to add if I let's see I want to add something. + +00:10:00 + +Piyush Choudhary: So meeting turning, right? + +Piyush Choudhary: if you see there are two datas, So each data we have the meeting then we have the information where we are adding the links and all right. So I just push it I've added one more thing. So it's in the markdown in form of content. you see So here it's visible. It will take two minutes to build so birds in progress previously. It wasn't the case. So basically what used to happen is it used to take around 20 to 35 minutes to actually build the file and here it is going to take only maximum one or two minutes to complete the will and the changes will be visible here. So you just have to make the changes in the markdown quality form of a Content. There is no technically involved by doing this. + +Tyler Wright: Okay, I think. + +Piyush Choudhary: and also we will also create a proper blog defining if someone let's say Jack wants to update so for example, we have a Proper guidelines like how to display this kind of box so we have written a custom thing. So you just have to add a single word box in the markdown file. So it will appear automatically here. So we will have a proper blog on how to update them out on file if something custom is needed what commands to use by updating them all done. So Yes, we can. + +Zach Horn: Hey piyush. Just want to say this is awesome. + +Piyush Choudhary: Yes. + +Zach Horn: I've been working with flat file CMS for a really long time. So this is great to see I mean and especially when we were dealing with PR based updates, over the past year or so, and we're dealing with that 30 to 40 minute build time. It's really tough to do that. So to hear that, it's what you say two minutes. + +Piyush Choudhary: So basically I posted it's already live so it took around 1 minute 5 seconds. So you see the third. + +Zach Horn: amazing + +Piyush Choudhary: Second is visible. + +Zach Horn: Fantastic, that's gonna make our lives much much easier a quick question for you. So on this page, I understand… + +Piyush Choudhary: please + +Zach Horn: what you're saying about, just going into the markdown file and making changes. I think there may be some copy updates that need to be made here that could Theoretically change the formatting of the page if you scroll up a little bit. Where you are? Yep to that light red call to action. I'm thinking that we could use maybe a different headline and some body copy in there. so I could go in and just change the markdown file to add that but I'm wondering if that's gonna Push that div around in a way that changes the structure of the page, if it's a significant amount of copy, what do you think about that? Do you want me to go in and make those changes now so you can have a look at it and restyle before this goes live or do you just want to keep going with development? Maybe we Circle back on this later. + +Piyush Choudhary: So basically as you can see the box that you are seeing here, so we're implemented with custom functionalities for it. and if we go to the markdown for + +Piyush Choudhary: Let me check. So if we go to the mount on file as you can see, this is the blog posts right so that you use to put basically text So basically what we have done here is if you see on the technical side. We're implementing the custom. Code but as a Content creative, you don't have to worry about that. You just have to write call to action banner and the banners this will appear automatically. So even if on the other Pages such Banner is required with this increase in between and the hiding so it is not possible through basic markdown passes, which we have just only the whole life easier and also if I can find + +00:15:00 + +Piyush Choudhary: This is a simple post as you can see. So this is how the code will look we have the copy sections. And also when it comes to the blog posts, we have multiple options. I don't know. + +Piyush Choudhary: this is the block So you just have to write similar to what is written here all to action Banner. We have the guideline on how to make it So. There will be different text even if you don't write it will be simpler one. But if you want to keep it like this, there are other options. I will properly create a block for this how to use such custom functionalities and it considering on the markdown, but even if you use the Current structure of yours, like whatever structure, it will be passed perfectly as in the front end as in different industry. + +Zach Horn: Yeah, this looks fantastic. + +Piyush Choudhary: and also Yeah. + +Zach Horn: To interrupt you Could you scroll back down to the code blocks at any of them? So these are + +Zach Horn: Okay, so you can copy and paste those full sections. that's fantastic. Can you do tabs at the top? just like + +Piyush Choudhary: Richard yeah this one. Yeah, we just have to write in the code would be. + +Zach Horn: Yeah, This is fantastic. I mean we've hit this for a really really long time especially the inline formatting that you've done, where you can see the highlighted text in line. That's really really great. + +Piyush Choudhary: What? I like to see this is the yellow one. We also have a single line word that you just need to add to the glove for and it will be like this or reddish. You just have to write danger for green. I just forgot what yours also I'll properly create and blog where everybody finding how to make the block for being red or whatever. Etc and properly pass things of + +Zach Horn: Okay, sounds good. + +Piyush Choudhary: So yeah, that's awesome. + +Denis Lelic: Up I have one question what happens when we host? The website on Akash Network. What happens to the build time? I saw you're using versa. it's + +Piyush Choudhary: so basically when it comes to hosting on the Cartoon Network, so + +Piyush Choudhary: The build time will remain same mostly but what happens is we just have to create the docker file, right? So after creating the docker file and I think it will not be feasible to post this on Akash Network because what will happen is whenever we make the changes to the record. So we will have to keep on updating the docker file again and again and then also updating the sdl file that is hosted on Akash Cloud nose, so it might be a issue for the developers or if the instant updates are needed. So when it comes to for example, the Cosmetic website is right now hosted on GitHub pages, right? So the version is full time will almost be saying they might be few seconds of difference. So right now as I push the change it took around one minute five seconds, so it may take one minutes 10 seconds. So that's all right. Now if you see the current web + +Piyush Choudhary: if I show you the current website, I'm not. + +Piyush Choudhary: even if the full on lines of code is getting pushed it is taking around 30 to 35 minutes to complete the bill. so + +Piyush Choudhary: as you can see for the build. It's soaked around 24 minutes and for deployment it took around 28 minutes to even build two lines of code. And while when I pushed to our website took around it total one minute five seconds to complete. + +Denis Lelic: Okay, Cool. + +Denis Lelic: and regarding the docs page Tyler you wanted to talk about it any questions or + +Piyush Choudhary: easy + +Denis Lelic: anything you want to share? + +Tyler Wright: No, no, I just wanted to reiterate that when it comes to just the structure. I know that it wasn't just Luna, the migration is one thing and I think it's fine for us to we migrate because I think there's a number of new documents that have been created since Luna's team did the initial migration but from a structural standpoint and maybe we could just reference. Let me see if I can find is real fast, either way the structure and the front end of the sidebar and how things were kind of set up. I know Greg really likes that which is why he had a Neil yesterday. He asked about it earlier in the week and the engineering sink. So I just want to make sure that we take that into consideration so that we don't get slowed down later. + +00:20:00 + +Piyush Choudhary: It's what we can do is we can tell the lunar stream to deploy it and… + +Tyler Wright: Yeah. + +Piyush Choudhary: if it's visible as you said it's already completed right so will not be a big class for them to deploy it and then migrated to the rockstar.com so you can ask their team to migrated if it's possible, but as we are also working on it for the official website, so I just have to ask you questions one is like as you can see in the content directory of dogs. These are the followers that will be visible on the sidebar and Cycles. Let's say I open buildings started. These are the MD files that will so + +Piyush Choudhary: there's one questions is I had a chat with Denis a last time you few days ago. He said that we don't. If I go to the Department. + +Piyush Choudhary: + +Piyush Choudhary: so even if I open the cloud most declared part, instead of having the proper MP5 anyone who I am having to subsections which is the same case here as well. So if you open this index code and We have the subsections. Let me see. if on + +Piyush Choudhary: what's wrong? + +Piyush Choudhary: from being technical support + +Piyush Choudhary: s + +Tyler Wright: So as I'm looking at this and maybe this is what you're saying the subsections are different in these new Docs. as + +Piyush Choudhary: right personally feel or maybe not so I just want Jack to take a look at the fullest structure and then defiles and the way MD files are being implemented here. because these folder structure will be going as if he's on the design. So let's say we have the getting started at first when I for example, let me show you how it will look. + +Piyush Choudhary: Let me open the double Point page, So this is the development page as you can see we have the header welcome Community groups current projects for website strategy roadmap and boundaries. So let's take this as an example. Let's say we have the getting started at first. So let's say this is the getting started that will be visible on the top when I will drop down similar in this case. it opened up the overview right? So when I will drop down on getting started I will have this overview I will have the homepage and then I have the options environment set up funding technical support your first plan. So I just want The content in to take a look at the content if it's hundred percent, correct? Because + +Piyush Choudhary: It is going to be a part of the dogs, right and dogs plays a very crucial role for the whole Akash the system. So I just want the content we make sure that the content that is depending all these prices hundred percent complete and correct. So when we migrate them to the Rock speech, they will not create an issues for the users. + +Zach Horn: Will probably need to pull on someone from our engineering team just to ensure that belt technically correct, but I'll handle that on our end and keep you updated. + +Denis Lelic: what about the let me just check quickly. + +Denis Lelic: I'm just looking at the current website and the working groups. and I'm just wondering if everything there is up to date or it's not building at all. + +00:25:00 + +Tyler Wright: No, it's not building at all. I was hoping ideally and… + +Denis Lelic: Okay. + +Tyler Wright: maybe we can have a separate call about this before next week. I was hoping I like the solution that appears put in and I know that Zach likes the fast build time so I don't want to mess around with it at… + +Piyush Choudhary: it's + +Tyler Wright: My one issue that I'm trying to think about quite honestly is right now everything. But I do from a note- from those taking standpoint lives in the community if we have to then update the community repost so that it's up to date there and then we also have to update. the website repo that might be less than desirable but not the end of the world. So I just have to think that through a little bit. + +Piyush Choudhary: Basically… + +Denis Lelic: + +Piyush Choudhary: if you see in case of the development Community groups this Siz the blue G and U G's are still not complete because I don't have all the details related to the meeting leadership contacts a project supposedly 11 results because it's Etc. So I just want the markdown file for these pages and once I upgrade them out on file into the website right with visible instantly here, so they will not be any major changes. + +Tyler Wright: Yeah, I'm not necessarily talking about major changes from the beginning. I think you all can do a great job of making it look the same my thought processes around me maintenance,… + +Piyush Choudhary: he + +Tyler Wright: I'm going to be maintaining and updating the readme file inside the community repo with all the information and then I'm gonna have to do the same thing inside of + +Tyler Wright: Inside of the website repo again, not the end of the world, but just something I'm thinking about also while we're on the subject right now. + +Piyush Choudhary: Yeah. + +Tyler Wright: I think + +Tyler Wright: Anil alluded to it yesterday that this section with the roadmap. I dropped it in the chat. I think he wants to use a visual roadmap. I wonder can we drop in embed those project boards from GitHub? I know that there is one already for engineering and road map. Yeah, I'll read drop chat, but I was wondering if we could do that versus the project list that you have shown up there. + +Piyush Choudhary: And this one? + +Tyler Wright: Yeah, yeah instead of that one. Look at the chat. There's a projects github.org slash the topic that one. Yeah, perfect. We do we looked at this yesterday a little bit. + +Piyush Choudhary: Really? + +Tyler Wright: And I know that a Neil wants to Sunset that project list board and just use this so I was wondering can this be embedded on that page? + +Piyush Choudhary: So I will have to take a look at the GitHub API. So if you allows us to embed it, so we will be able to generate it. + +Tyler Wright: Okay, cool. I think yeah, that would be better than project list because I believe that project list MD file that you are just referencing is going to be sunset. They're not going they don't want to use that anymore because it's too hard to maintain. + +Zach Horn: For the workflow things that you were just talking about I mean, is there an option where the website repo becomes the source of Truth for these things? So it's just one repo to update… + +Piyush Choudhary: e + +Zach Horn: which is the website repo. + +Tyler Wright: yeah, that's a good suggestion my fear is because so many people are used to community repo and… + +Zach Horn: Mm-hmm + +Tyler Wright: our error maybe wouldn't be an issue because they can just submit a PR on the website Repro. I think it's a good idea. I'm just worried about again people like changing their behavior and… + +Piyush Choudhary: he + +Tyler Wright: some issues going We post some of the project boards go in the community repo again. It's not that big of an effort To copy and paste but yeah,… + +Piyush Choudhary: really? + +Tyler Wright: I'll think about that. That's a good suggestion Zach. + +Zach Horn: Sounds Yeah good. I hear what you're saying on the duplicate effort part. But also yes, the fast Bill times are our ideal. So anything we can do to preserve those. + +Tyler Wright: Yeah, yeah, I will not whatever this I'd rather do duplicative work then sacrifice a build time. So I think what's the same page there? + +Zach Horn: pressure Okay, sounds good. + +Denis Lelic: What if we're not duplicating the work? meaning everything can live in the community repo, but we just add the links to the website repo. + +00:30:00 + +Tyler Wright: Yeah, that's what I'm saying that I don't think and maybe I over exaggerate so I apologize. What I think I would have to do is I would take the content that's on the readme file and that table that has the meeting links the transcript length and the recording and I would just have to copy that over and maybe just add a little bit of syntax on the website where you post I don't think it'll be that big of an effort, to be honest. + +Denis Lelic: or we could basically just link to the Community repo meetings notes and stuff on the website repo So when you let's say you're on the website you're scrolling through those projects,… + +Piyush Choudhary: just + +Tyler Wright: Yeah. + +Denis Lelic: whatever. And there's basically just a link that takes you directly to the GitHub. + +Tyler Wright: Okay. + +Denis Lelic: Community repo let's say I don't know Sig or working group or something. + +Tyler Wright: Yeah, that's a good call out. Basically. It's like a link to the readme file and then you click on that and you open up the readme file. + +Piyush Choudhary: So yeah, we already have that functionalities. So I think I go to implement this in this page, but when it comes to the block page, it will not be a big task. For example, if you want to update this blog. So we have the update post option. So it takes us back into the particularly file. So this will be the case for others as well. So I just lines of code. So when I am the Ducks and when I am on the development page, so let's say this is also coming from the readme file. I will just add update post section and when you will click on the update post people directly into the readme 5. + +Denis Lelic: I guess we'll see. In the next couple of weeks. What's the best way to work with this? + +Denis Lelic: I'm sure we'll figure things on the go so + +Denis Lelic: once back looking for my notes. So we talked shortly about the docs. That's quite clear for I mean, we'll see. when piyush creates The first section so let's say I don't know a home page for the blogs for the docs. + +Piyush Choudhary: he + +Denis Lelic: How that structure behaves the menu on the left and stuff like that. + +Denis Lelic: I couldn't find. the stuff Luna and his team did I just had one screenshot on my desktops living there so I could only refer to that and I shared it in the Discord with piyush and Tyler. But I Think We're Not Gonna Go Far Away from that. so it's going to be the same or better experience Yeah type. + +Piyush Choudhary: so just to give an overview on how the dot special look so we have four variants. So let's say on the left hand side as you can see, we have three sections when the phone get started and this is nothing but a table of content, so when it comes to the above talk to sections the home and get started the continual like They displayed on the whole page that you are seeing right now. It is taking the whole space and similarly when it comes to the website page. It will also taking the whole space as you can see and when it comes to the table of content. + +Piyush Choudhary: This is also. Place you So this is how the table of content will so we have the drop down section similar to what we did with the Development page as you can see we have the drop down options. So we just talked the line it so we will have the drop down options. And then when we click on the files the content will appear in the middle from the markdown by itself. As you can see here. And on the right hand side we have on this space section this similar to work there on the blocks or the customer. So this is how the dog's page will behave and the user experience will look like + +Denis Lelic: Okay, cool. Yeah Ty + +Tyler Wright: It's gonna say I found an old issue for the docs migration. I put it in the chat. It's issue number 86 inside that issue. I think you can find the spec for the hierarchy as well as some images as well for that sidebar. So I just want to have an additional reference. Let me know if you want. Luna's team to establish and we bring up some of those website, but I know Denis you gave feedback on some of these items. But again has that kind of structure. I'm not saying and just want to make it clear pH. Can you go back to the center of this image? I'm not saying doing anything with that middle box. I think that the way that you all have it with the main section is optimized and way better than what + +00:35:00 + +Tyler Wright: What suggesting docs 2.0? I my only concern is this left bar where the zero dot was zero one is because I know that again great has explicitly talked about liking that so I just want to make sure we keep that top of mind about Exactly just a category and… + +Piyush Choudhary: this one + +Tyler Wright: headers and where some of these docs are nestled. That's all I'm concerned about. + +Piyush Choudhary: and also as you said to ask him already completed the thing so it will be better if you can ask the lunar system to make it live and share the link so we can have some Lego view of how you understand. + +Tyler Wright: Absolutely, I'll do that. + +Denis Lelic: cool Sounds good. + +Denis Lelic: Yeah, the issue 86 you've shared Tyler. That's the same images. I found on while I was searching on my computer. So + +Tyler Wright: Okay. + +Denis Lelic: yeah, I don't think that's gonna be an issue. We're so gonna have this menu on the left. Yeah, and hopefully it's gonna be better. Experience than the current website docs and dark 2.0. So basically this is a dark 3.0. + +Tyler Wright: I love it. + +Piyush Choudhary: he + +Denis Lelic: Okay, anything else we have? To discuss anyone wants to share anything. + +Zach Horn: Yeah, really quickly the pricing page that we're thinking about now hosting on the website. How do we have a design of how that's going to look and the reason I'm asking because it's something that I'd like to share more broadly when we are doing external Communications and even designing lightly hands around pricing on Akash. I just saw the link usually click through. + +Piyush Choudhary: + +Denis Lelic: Yeah, I can share the figma drawing we have at the moment. + +Zach Horn: Okay. + +Denis Lelic: Let me know if you can see my screen. + +Zach Horn: I can't. I can't yes. + +Denis Lelic: You can. okay, so there's + +Denis Lelic: What two ways to go? Basically for the first stage, I'm not really sure if we can share the GPU stuff. To calculate prices. So the way it's set up now is you have a couple of options to choose from presets and it's going to change the bottom parameters here and then you just hit calculate price and it's gonna give you a price and the second stage you're gonna have a GPU optimized and… + +Piyush Choudhary: he + +Denis Lelic: you can add different GPU models and also change the parameters for memory and stuff like that and hit calculate price and it's gonna give you + +Denis Lelic: price estimate and Some sort of a comparison to the AVS Google or Microsoft. + +Piyush Choudhary: So yeah,… + +Zach Horn: Right. Fantastic + +Piyush Choudhary: so these one issue with the GPU part we were exploring the cloudmoss and I cleaned their price preparator the GPU. Stuff is still not implementing. + +Denis Lelic: Yeah, yeah. + +Piyush Choudhary: The GPU thing right now will not be possible but others since + +Denis Lelic: that was my concern also, because that's why I said we have two ways one is to include the gpus if that's possible. If it's not we're just leave them out and when it's possible we include them the Arthur other thing. + +00:40:00 + +Denis Lelic: Greg and O'Neill mentioned was the let me see if I have that here. + +Denis Lelic: provider incentives so we would just add a Text field and a call to action for the Prater calculator. So anyone who's interested in becoming a provider they can just hit this button and go to The Prado calculator and see what would their earnings look like? + +Zach Horn: Amazing because from a marketing standpoint, there's two cohorts of people that end up bucketing themselves when they're interested in Akash, and it's exactly what you would think which is how much does it cost if I want to deploy and I have resources how much can I earn so surfacing those two tools? I think it's gonna help us plenty of Thumbs Up from Ty and agreement + +Zach Horn: so yeah, I think would you guys have looked great looks great a question though when You may have just said this I was clicking through the site as you guys were talking. + +Piyush Choudhary: still + +Zach Horn: How are you pulling the data? Is it real time? Or are you querying some interval. + +Piyush Choudhary: So it's realized for example to open the open page. So it's a real time API and it's all more of dependent on how the cloud most is doing. So we have got the access to their apis. So we are implementing the same way the cloud Moses in on the basis. and personally,… + +Zach Horn: Got it, okay. + +Piyush Choudhary: I think + +Zach Horn: Okay, sounds good. + +Denis Lelic: cool + +Denis Lelic: Yeah, and there's also one section and that's called network activity. So I think that's gonna live on the website as well next to the pricing and stuff like that and they're gonna remove it from the cloudmouse. + +Denis Lelic: I think the block Explorer and stuff like that that's going to live on the website. + +Zach Horn: Right, okay. + +Denis Lelic: Yeah, because it's kind of not a deployment. thing so anyone interesting and how much? Akt is spent or something like that or what's happening on the blockchain? What kind of blocks was actions that are going on? You were just go about Akash page and there's gonna be a menu item on the left called network activity with a couple of sub items and you can just go through all of them. + +Zach Horn: This ecosystem page is Excellent, but definitely makes sense. + +Tyler Wright: agreed + +Zach Horn: … + +Denis Lelic: Yeah. + +Zach Horn: I was avoid, brainstorming on these meetings, but As I'm like watching you click through the website. I'm thinking that when we launch this we should have someone record a video of them essentially giving a tour of the website looking around and just showcasing all the parts and hadn't had that thought before right now, but let me draw that up and just see what that might look like. And we can chat about that as we get a little bit closer. what's the timeline a dentist? I think you had mentioned at the other day. But what's the latest to have this launched? + +Denis Lelic: I think piyush management mentioned yesterday three to four weeks. + +Zach Horn: Okay, sounds good. + +Piyush Choudhary: It can be released on not before but there will be lockers related groups the most they are mostly lockers related to the contents. So we are almost done I think within a week or two. The functionality part and everything will be done and complicated and we are going to start the final design. Leave you with Denis. So the things that are not aligned properly with the Tailwind CSS default layouts will be changed a little bit as for the directions defined by Denis and the protein and Currently there are no blockers. We can launch this a lot before but I think three to four weeks would be fine. + +Zach Horn: It's okay. + +Denis Lelic: Yeah. I wouldn't push it let's do it in a week when there's any events ahead of us or something like crucial stuff going on so we can just take our time and make sure everything is working properly everything looks and behaves properly and stuff like that. + +00:45:00 + +Tyler Wright: Yeah, and make sure the links are optimized and all that kind of stuff. So, yeah, I think after maybe a little bit starting next week, but after we should start thinking about my testing strategy and then a path towards I really like the idea Zach of a walkthrough video of all the work that piyush's team have done and just the experience. Go ahead. + +Denis Lelic: Are once one question just something that came into my mind. Let's say someone is sharing the website on Twitter. And there's that image preview. currently I think we have one image and it's called something Soren infrastructure the scales. What's the best way for us to have multiple images so we can switch? + +Piyush Choudhary: we + +Denis Lelic: Based on the content. We're sharing on Twitter, for example, because I know Twitter now is not allowing the headline from the things you're sharing. So basically you just see an image on a short link. So maybe we could leverage that to include some of headlines included in the graphic. I hope I didn't complicate too much. + +Piyush Choudhary: Don't I just have to explore how Twitter is and links? So when we share the link on the Twitter, I just have to look on how process the data while passing that links. So accordingly. I will try it's possible into the multiple images. So if I click on your Twitter on the Twitter. I will see if it's possible to have the multiple images in place, but I haven't explored that yet. So I will just take a look on how the Twitter is doing that and what data needs as + +Denis Lelic: Yeah that Zach. Do you have any thoughts on that? + +Zach Horn: Yeah, I think if it's technically possible sharing the graphic, especially for blog posts as the social images is ideal. And what we could do from a Content standpoint is make sure that some version of the headline is in the graphic. So when we share the link on Twitter and the graphic people can quickly see that it's a blog post and be what the headline is and Denis maybe we can come up with is a universal standard that we use for our post Graphics that includes some copy that says, Akash blog poster, something like that just so that we share the link there's a standard format. So people can quickly see that It's a blog post because they won't have the headline. + +Denis Lelic: Yeah agree, we could label it with some sort of a badge or something. + +Zach Horn: Yeah, definitely. + +Denis Lelic: Yeah, we can explore that. + +Zach Horn: Sounds good. + +Denis Lelic: Okay, cool. + +Denis Lelic: Okay, we have five more minutes left. If you guys have anything else to discuss, please let me know. Otherwise we can wrap it up. I know some of us have another meeting coming up. So. Just to have three minutes of break in between those would be nice. + +Denis Lelic: Thanks for participating Arthur as always it's good to see the progress. + +Tyler Wright: but + +Denis Lelic: We're making and you guys are doing so looking forward To the next meeting and… + +Piyush Choudhary: Also and… + +Denis Lelic: and everything. eat + +Piyush Choudhary: also in the last minute we discussed to update the deploy and application based on Akash network official website. So as you say that we already did it in around 12 days. It's like on this so we have fun. So from deploy page and there is only Cloud nose. + +Denis Lelic: Yeah, good call out. That's something we discussed previously and piyush was kind enough to remove the console from the deployment page. So we basically have just Cloud models there now, so thanks good call out and thanks for taking care of that. + +Denis Lelic: We'll talk offline and see you next week. Thanks again. + +Tyler Wright: Thank you. + +Piyush Choudhary: Thank you, Vermont. Have a good day. + +Denis Lelic: Thank you, bye-bye. + +Meeting ended after 00:50:33 👋 +