diff --git a/committee-steering/README.md b/committee-steering/README.md index 8dfb2290..dbd9ca6e 100644 --- a/committee-steering/README.md +++ b/committee-steering/README.md @@ -22,12 +22,22 @@ The Steering Committee is a special SIG that periodically evaluates the list of | Thursday, June 29, 2023 11:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/006-2023-06-25.md) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/006-2023-06-29.md#transcript) | [Link](https://n6o6hg3bmrlh53cz6ykmpokamvnzgusa3vycwvbr4vxmamusuh5q.arweave.net/b53jm2FkVn7sWfYUx7lAZVuTUkDdcCtUMeVuwDKSofs) | Thursday, July 27, 2023 11:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/007-2023-07-27.md) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/007-2023-07-27.md#transcript) | [Link](https://2uw2d6ylfq3v2btiav5izgx4kvsgcc2s72bb5vvymb5byck4jsca.arweave.net/1S2h-wssN10GaAV6jJr8VWRhC1L-gh7WuGB6HAlcTIQ) | Wednesday, August 30, 2023 11:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/008-2023-08-30.md) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/008-2023-08-30.md#transcript) |[Link](https://6bmxztaobmi5ox6n3nv5f6hgz7cwn7y7qxkp7ureegcbxswq4yxa.arweave.net/8Fl8zA4LEddfzdtr0vjmz8Vm_x-F1P_SJCGEG8rQ5i4) -| Thursday, September 28, 2023 11:00 AM PT (Pacific Time) | | | -| Thursday, October 26, 2024 11:00 AM PT (Pacific Time) | | | -| Thursday, November 30, 2024 11:00 AM PT (Pacific Time) | | | -| Thursday, December 28, 2023 11:00 AM PT (Pacific Time) | | | +| Thursday, September 28, 2023 11:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/009-2023-09-28.md) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/009-2023-09-28.md#transcript) |[Link](https://bw2dirmu4darmwcx74o24hzfkjzs7f33grrc5rdihgysff4kxyta.arweave.net/DbQ0RZTgwRZYV_8drh8lUnMvl3s0Yi7EaDmxIpeKviY) +| Wednesday, November 1, 2023 11:00 AM PT (Pacific Time) |[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) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/011-2023-12-07.md) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/011-2023-12-07.md#transcript) |[Link](https://k6mud4r2ua6xarj6c5zqtkxw6fzjrvzjzu6eotsyhsmotles2gaq.arweave.net/V5lB8jqgPXBFPhdzCar28XKY1ynNPEdOWDyY6ayS0YE) +| Thursday, January 11, 2024 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) | | | +| Thursday, March 28, 2024 11:00 AM PT (Pacific Time) | | | +| Thursday, April 25, 2024 11:00 AM PT (Pacific Time) | | | +| Thursday, May 30, 2024 11:00 AM PT (Pacific Time) | | | +| Thursday, June 27, 2024 11:00 AM PT (Pacific Time) | | | +| Thursday, July 25, 2024 11:00 AM PT (Pacific Time) | | | +| Thursday, August 29, 2024 11:00 AM PT (Pacific Time) | | | +| Thursday, September 26, 2024 11:00 AM PT (Pacific Time) | | | +| Thursday, October 31, 2024 11:00 AM PT (Pacific Time) | | | +| Thursday, November 28, 2024 11:00 AM PT (Pacific Time) | | | +| Thursday, December 19, 2024 11:00 AM PT (Pacific Time) | | | ### Typical Agenda @@ -40,7 +50,6 @@ The Steering Committee is a special SIG that periodically evaluates the list of The Steering Commitee is initially comprised of the following members who have the most familiarity with Akash Network but the meetings are public and anyone is welcome to attend and listen-in. -- Adam Bozanich, Overclock Labs - Anil Murty, Overclock Labs - Artur Troian, Overclock Labs - Greg Osuri, Overclock Labs diff --git a/committee-steering/meetings/010-2023-11-01.md b/committee-steering/meetings/010-2023-11-01.md new file mode 100644 index 00000000..6bd7bfa8 --- /dev/null +++ b/committee-steering/meetings/010-2023-11-01.md @@ -0,0 +1,442 @@ +# Akash Network - Steering Committee - Meeting #10 + +## Agenda + +- Review / discuss / address any community feedback, grievances, or conflicts. +- Review [projects list](../projects-list/README.md), prioritize / add / remove if necessary. +- A look at open discussions in [Github Discussions](https://github.com/orgs/akash-network/discussions). +- Open up to any other questions from the community. + +## Meeting Details + +- Date: Wednesday, November 1st, 2023 +- Time: 11:00 AM PT (Pacific Time) +- [Recording](https://4yrnmjlm3nco2ccfkbkv67s6cfgvgrge7op5dfwnv6gn46mueqxa.arweave.net/5iLWJWzbRO0IRVBVX35eEU1TRMT7n9GWza-M3nmUJC4) +- [Transcript](#transcript) + +## Committee + +- Adam Bozanich, Overclock Labs +- Anil Murty, Overclock Labs +- Artur Troian, Overclock Labs +- Greg Osuri, Overclock Labs +- Scott Caruthers, Overclock Labs + +## Participants + +- Anil Murty +- Artur Troian +- Cheng Wang +- Denis Lelic +- Deval Patel +- Emmanuel Arthur +- George Pro +- Greg Osuri +- Herman Drotz +- Jannick H +- Jigar Patel +- Julius Haus +- Max +- Piyush Choudhary +- Robert Del Rey +- Robert Koschig +- Rodrigo Rochin +- Scott Carruthers +- Scott Hewitson +- SGC | DCnorse +- Tommy Eastman +- Tyler Wright +- Zach Horn +- Zach Ross + + +## Notes: + +- Anil reviewed the structure of the meeting for any new members. +- Anil started the meeting by asking if there any feedback on how things are going in the community or any grievances? +- There were no grievances in the community at this point. +- Anil reviewed the project list. +- Cheng talked about the utility of AKT. AKT is always going to be front and center. + + +### Projects: + +- GPU support has done and is publicly released. This will be marked as released. +- Anil brought up the engineering board. +- Cheng mentioned that there will be a marketing and community board +- Anil wants to retire the table, and replace it with boards. +- Anil and Artur talked about Stable Payments. Still in progress with native stable coins. This may require a network upgrade. This could require packet forwarding, and there is a solution being worked on this. After that this can be marked "released". +- Piyush gave a demo on the work with website revamp. +- Events 2024 working group session is happening Friday November +- EDU certification is being restarted. More details coming soon. +- Anil asked about any thoughts or questions regarding the Akash Hackathon. +- Cheng talked about feedback he had about the hackathon. There was also a retro with participating members. +- Anil mentioned he saw variance of quality of submissions. +- Piyush will share a link to the docs page on the website over the next week. +- Anil talked about on-chain analytics. +- Anil mentioned that Piber brought up a good idea about analytics. +- Anil mentioned that there is an issue where provider attributes from Cloudmos get wiped when provider is restarted. Max mentioned Providers need to update their provider.yaml file to reflect the changes made on Cloudmos. +- Anil asked if Authorized spend management PRD is complete. Cloudmos has all of this working fully functional. This will be changed to "released". +- Deval mentioned that Praetor team will do another demo for content moderation. +- They are going to submit PRs to share binary. +- Tyler mentioned that there is a network upgrade coming soon. + + +### Github Discussions: + +- Anil gave an update on the Foundational model work with Thumper. +- Anil thought about doing model with stable diffusion 1.5. Doing stable diffusion 2.0 would have been 5 times the cost. It was noticed that Databricks had a paper that they were working on with Cornell to train with stable diffusion 2.0. +- Anil and the Thumper team weighed options and decided to run a foundational model with Pixart alpha. Pixart claims to produce images with the same quality as stable diffusion XL. Costs will be the same as asked. +- Shimpa is working on bringing of the provider now. There will be a lot of updates coming via Akash Network marketing channels. +- Piyush talked about https://github.com/orgs/akash-network/discussions/349. +- Piyush shared a demo for people to look at. Find it [here](https://www.loom.com/share/55b7f978c66b4153b23336a0702e8248?sid=81a11736-ff67-49ee-974d-0427e704e347). This will be built on top of Cloudmos. +- Anil asked what provider would this be trained on. Who is going to be the provider, and who is going to manage? +- Piyush said the model will be trained on Akash. The AKT requested. +- Anil mentioned that Zach Ross from Foundry has a100 researches. +- Anil asked how much the training costs versus hosting costs? +- Anil asked why the cost went up from $50,000 to $63,000. +- Julius asked how many people are working on it. Piyush mentioned his team has 8 people. +- Anil suggested using Foundry for training the AI. +- Piyush mentioned he would put the proposal on chain soon. + + +**Open Discussion:** + +- Tyler reiterated that there is a Network Upgrade coming soon. Messages will be shared in Discord and beyond. + +### Action Items: + +- Authorized Spend Management will be moved to "released". +- Piyush to figure out how many a100s hours are needed for training. +- Core team is going to prep for the 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: All right, welcome everybody to steering committee monthly meeting number 10. Usually these monthly meetings for the steering committee happened at the end of every month. But for this month it got moved. So thank you everybody for accommodating the date change. + +Tyler Wright: Again during committee's Anil and members of student committee Syrian committee walk us through project lists GitHub discussions. And then there's a time for open discussions at the end of anybody has anything that they want to talk about relate to the cash Network today is an added action item. I see piyush's on the call. So again a number of updates related to initiatives that are going on go on during specific special interest group calls. I know that the parade tour team does a great job of giving updates and all the work that they've been doing since receiving community pool funding on during sick providers calls and in Discord, you're just a great job of letting us know what he and his team are working on since they've received community pool funding for the website revamp during the working group of class website a weekly meetings. These are all again meetings that are open to anybody if they have any questions comments thoughts ideas, but + +Tyler Wright: I know the piyush is going to take maybe two to three minutes a day just to give the wider group an update on the work that he and his team have been doing on what the website. So I think that we'll have that after the GitHub discussions as an agenda item. But without further Ado again last month rather was a quieter meeting. I know a number of people were traveling because of Versa number of other meetings. So we talked about follow-up discussion from metamask as well as + +Anil Murty: Thanks, Tommy. Hey everyone's doing well. I'm gonna go ahead and share my screen and then we can go to the usual just things that we do. + +Anil Murty: Okay, so for those of you that are joining us for the first of all, welcome and just a quick rundown of what we do on these calls the idea with these calls is not to go into Super depth on any given topic. Although we might think one topic that people want to talk about on a different week just in the interest of time, but in general what we do on these calls is we review and address any Community feedback in terms of how things are running in the six in the work groups. As well as any sort of conflicts that might be potentially happening. So if there's any of those bring those up, And then we review the list of projects that are in the backlog as well as anything that's being worked on right now and just be at a high level talk about, potentially any blockers or any issues on those or if there's good progress, report on the progress. And then the third thing we do is review. We try to review. + +Anil Murty: most of the new GitHub discussions that have been posted since the last hearing committee meeting and if possible have a discussion with the person that posted that specific discussion. ideally what we like to do is have the person that created the discussion join these meetings and talk about, their vision for that specific proposal if it's a proposal or just agenda discussion. And then of course if there's any other questions from anyone we can take those up as well. Before we get into these are there any questions from anyone about the agenda? + +Anil Murty: Cool, I guess we'll get started with first one. Is there any sort of feedback from anyone about generally the cigs in the work groups or things that we need to talk about in terms of conflicts? + +Anil Murty: Never a couple of minutes see if anybody wants to bring up any sort of feedback. + +Anil Murty: usually get nothing in this part of the meeting so Nothing different from that this time. Okay, I guess we'll move on to the projects list. But if there's anything that people can think of later, please feel free to post it in the chat and we can go revisit it at the end. So let's move on and talk about the projects list. So for those that are joining the first time there is a link here to the list of projects. You can also get to it from GitHub in the project list directory. + +00:05:00 + +Anil Murty: that's out here. And one of the things I want to call out is in the last steering committee meeting one of the things we talked about was potentially using a project board for managing some of these projects. So what we have done since then is We've created a community board specifically for engineering and development projects and within the overclock engineering team. We've been using that to sort of Keep track of progress as well as priorities between various development tasks. So if you want to get to that you can just go to Akash Network the route the degree and for the root repository in GitHub, and then from here if you click on projects. What you see is a link to a cohesive product in engineering roadmap. So we click on this. + +Anil Murty: What you'll see here is basically a project board that shows you kind of, various initiatives or sub projects that are in progress as well as in the backlog for what the development teams are working on. So primarily in progress ones are the ones that are getting the most attention right now. And then this next one here is the up list that is a prioritize list of what we would potentially be looking at next. So if you haven't take any located yet, please do take a look at it. Once again, you have to go to the root Akash Network and click on projects to get to this. But some of the main things that the teams have been working on most actively are from the core team side. We've been working on. Provider feature Discovery as well as making provider attributes available in bids. This is primarily driven by the fact that we have seen, + +Anil Murty: Fairly active amount of usage of gpus on the network but one of the things we've noticed as a result of that is there are pain points in terms of being able to find the exact gpus that you want on the network and then when you actually go into a deployment, there's no way of knowing which GPU you're getting in cases where you don't actually indicate with GPU in the STL. So these kind of address those constraints are those problems. They're high level. There's provider content moderation. We'll talk more about that. things that the cloud most team is doing in terms of improving the GPU deployment experience as other things. take a look at the project mode. If you haven't had a chance to look at it. Oops. Sorry about that and definitely bring up if you have any questions about The other thing that we have talked about and Cheng feel free to jump in here if you're on the call. + +Anil Murty: We've talked about potentially building a similar project board for marketing and Community initiatives as well because obviously the list of projects in this table here span more than just development effort. There's a lot of community things that happen. There's even planning there is marketing efforts that go on. So one of the initiatives that we've been discussing so we've obviously been running the engineering meetings with an overclock team by looking at this project board and it's been working really well for us to keep things focused in have, a place where people can go and look at what the priorities are for the team. So with that in mind, the marketing team and the community teams have been leading towards using a similar process for their work as well. I don't know Cheng if you want to talk a little bit about that. for me to put you on this part, but + +Cheng Wang: No worries. Thank you il. Yeah, we're exactly just like following the footsteps that you've paved here Anil with regards to the board that you've built for the cohesive roadmap. We're currently internally collating a lot of the stuff that the community has been working with us on in order to prepare to get some of these things. + +Anil Murty: Thank you for the update. So going forward. Hopefully if we can figure out the board for marketing and community events as well similar to development projects then my hope is in the future. Maybe the next year in committee or the one after that. We can actually retire this table that's out here and just use the boards to talk about everything that's in progress. So that should basically make this a lot more streamlined and very clear in terms of what's in progress as opposed to having to change, the tags on these every time and move these up and down board lets you do that much easily. + +00:10:00 + +Anil Murty: So that's kind of the intention going forward at some point. we're going to retire this and we're just going to have boards for one board for community and marketing things in one board for our development things. And if you find out that there are things that don't fit in any of those buckets, then we'll consider creating a third board. But right now the thinking is we should be able to handle pretty much all the things that happen within the Akash Community between those two buckets marketing and community and then development product and Engineering essentially. But if there's any thoughts or questions on any of that do post them up on the chat or raise your hand and happy to take those on. + +Anil Murty: So for this time since we don't have both the boards, we're just going to go through some of the items on this list, but in the future, hopefully we can streamline it a better. I did update the state of this board right before the call. So my apologies if I missed a few things. I marked some of the things that last time we called out as being released as released in this so we'll skip over those and just talk about the ones that are either in implementation, but mostly an implementation or respect definition. So the first one I want to talk about was stable payments and settlement. This one last time Arthur you had mentioned that there was one thing remaining that needed to be addressed on this and so we wanted to keep this open. Is that still the case or can you talk a little bit about what? + +Artur Troian: Yeah, do you guys hear me? so Yeah,… + +Anil Murty: Yes, I can hear. + +Artur Troian: the stable payments idea has been implemented of actually available right now on the main ad there is a one thing we are still in progress with related to the native. coins and + +Artur Troian: It was probably requires Network upgrade. So still in the process to assess what things needs to be done from our cash prospective. First. One is Packet forwarding we have sort of drops for that and we will be testing it soon. But I think there's one piece missing. So we're gonna need to discuss it with the other chains. Just make sure that we pick all of the necessary features up for that and as soon as we have No squared out we can close this part. + +Anil Murty: Sounds good. + +Anil Murty: Awesome moving on to the next item. There's an implementation here is the Akash website revamp. I know Tyler you and you share family the folks working on this. Maybe Zach is a world as well. Can we get an update on what we are with all of this? + +Tyler Wright: Yeah, so I guess Pierce is here. This might be a better than doing a little bit later, but I know Dennis Zach, he used and many others have been a party's working group sessions. I guess PSU mind taking over the screen really quickly be shared a link to share the link in Virtual and can you give us maybe one minute about where the website is and what's up next? + +Piyush Choudhary: So first of all, thank you so much for a long introduction. So this is use a world Panther on Discord. So we are working on Apache website. We're going for about 1.5 months even more than that, but our proposal got exactly one point five months back from now. It was on I guess 720 of September and we have made significant progress and we have used the top class technologies. That is estrogen CSS, which makes it a lot and very smoother in terms of Music Experience as well as on the pages for that is wrong with it. So we have almost completed most of the pages that as you can see only thing that is left. Is there a few pages that needs to be addressed and the dog's patient. So I think within the next two weeks the website will be completely ready all the feedback strong the designers and the + +Piyush Choudhary: members so if they might be some minor changes in our desire when it comes to the design perspective, but it's all going really well and very smooth and we hope that with the next few weeks would be one official domain and it has also real-time features. So apis are also getting integrated into the website. So whatever the total metrics that are being split here is real time, which was not the case with the previous acrossful that is currently basically on the classroom Network and we are also working on the pricing stat space that is a part of basically the cloud notes. So we'll be designing the presentation from Zach here and we will have a real thing from Charities by Integrations with the cloud Mercury behind the scenes all the calculations and also the net protective. So yeah, that's all. + +00:15:00 + +Piyush Choudhary: And I have also dropped the link in the chart if someone wants to check it out on the liberation. + +Tyler Wright: Thank you Again. If anybody has any comments on the Discord for the working group for the cash website is very active where Denis Pierce Zach and many others are participating as well as the group meets weekly on Thursdays at 6:30 AM Pacific time where a number of folks get together live and talk about specific design element. So if anybody here wants to join those conversations and that time does not Feel free to message me privately and we can create some other time. But again, we have folks from all over the world on our call. So that seemed like the best time but yeah Pierce. Thank you very much for a short demo. + +Piyush Choudhary: presentation + +Anil Murty: Yes. + +Tyler Wright: Yes. + +Anil Murty: Thank you piyush. That was those great and I was going to ask I was almost going to raise my hand and I ask about the pricing page, but you already mentioned that so it's great and that's good context for something else. I was going to mention which is once we have the pricing page implemented in the website. The plan is to remove the pricing page from cloudmose. + +Piyush Choudhary: Really? + +Anil Murty: So Cloud most of the deployment tool it's awesome that the pricing pages in there, but it doesn't quite make a lot of sense to have it in there. So it's more of a marketing thing talk about price comparison. So that's kind of the intention is to move it out to the website and remove it from clouds. So then moving on to the next things in this list is the next three kind of fit together, I think. Certification event planning in Akash hackathon. I don't see Adam wozni on the call. I don't know if there's somebody else who can speak to these items Tyler, if somebody else could speak to him. + +Tyler Wright: Yeah, I know Chang Cheng before you speak. + +Anil Murty: right + +Tyler Wright: I know that Adam is still feeling a little bit down for the count. But there is an event planning session. I believe for 2024. I'm happening this coming Friday. I think it's a second of a working group session around planning for what's going to be happening in 2024. I know the hackathon has completed and I believe payouts and made to those that have one rewards shout out to Huey for that. And I know he's working very closely with omniflex to update and restructure some of the certification programs because it's easier for folks to use but China. Do you have anything you want to add? + +Cheng Wang: That's wonderful. Yeah. Yeah just was I think catching the gnarly bug that's going around. So that's why He's still active on internal comms and things like that. But yeah So eventually Just as Tyler said and on the hackathon as So we're I think planning phase for the next go around is going to commence on that soon and a lot of the budgets and proposals will be going on chain sometime probably within the next month because we definitely want to beat the holiday season and that's all for looking into 2024 for both hackathons planning and the edu program that one item is being restarted at this point in time. Now, there's a little bit more bandwidth and we have some more clear-cut parameters, so That's something to look out for not too many details to share yet on the edu efforts, but that's something where the Insiders and I don't have already been working on. + +Anil Murty: Sounds good. Thank you Cheng for the update. One thing. I was wondering does anybody want to share I think this is the first hearing committee meeting where we have that we have had since the hackathon ended is a sort of feedback from the hackathon that's worth sharing here, in terms of things that did not go Anything at all? If not, no worries. + +Cheng Wang: Yeah, a few things as far as the hackathon goes I think the items this was I think a really good test bed for understanding how the hackathons will look like under Dora hacks managing the kind of operations of it. I think the operations of it was well managed and that was fine. I think the challenges were primarily around in the initial days of the hackathon or initial weeks. They're just unavoidable. suppose baptized. I suppose people like that just kind of submitting whatever projects and praying and spray praying rather across a whole bunch of different hackathons. Just hoping they may sneak in and get a prize or completely unrelated to Akash. So that was one thing that we have to I think be cognizant of and really get people who are wanting to build I think within our hackathons right to have those properly geared up and incentivize before the hackathons even go live. That's number one number two, because I think + +00:20:00 + +Cheng Wang: That all the top three winners are existing community members and who have been community members for some time. So new entrants seems unlikely to join this particular hackathon, but of course that doesn't mean we won't continue to try right that's another part. And then finally I would say in terms of tracks and pushing something out there that is a bit more closed and Is something that we're thinking about just instead of having the hackathons be super open and then people can build anything they want, We might have two separate categories. I don't know yet. This is just early thoughts. But I have an open-ended side as well as something that's very specific that we would like to incentivize the community to try their hands on. So those are the current that's the other I guess third item. There is having a bit more guided path and in addition to the open one. + +Anil Murty: That's great. Thank you Cheng and let go the comment I think about. They're being a lot of variants. So when I was looking at all the projects that were submitted into haathon, I noticed that some of the projects had basically almost implemented a solution that could be deployed in scaled up right then and there was some projects which was basically three lines of hey, this was an idea that I have in my head effect. that's kind of impression. I got in so completely Echo your comment and on the way and so there but overall, I thought it went really well so nice work. By everyone that was involved. + +Anil Murty: The next one is Dockside migration. I know Luna in team have been the ones that have my privately driving this forward. I don't know if Luna's on the call. I was hoping it would be + +Tyler Wright: From the standpoint of sorry,… + +Anil Murty: + +Tyler Wright: and they are from the standpoint of the work that Luna and the quasar's team have done on dock sites migration. That work is released. I know that because they were doing the work in Hugo and now we've moved to Astro there is a little bit of rework that's going to have to done but the front end kind of look and feel menus and sub menus is going to persist into the newer version. Go ahead piyush. + +Piyush Choudhary: So I have a comment on that. So I simply got the access to the work that you mustn't read on the dots site and we have seen as we are building the cash website program from scratch and docs being a part of it. So everything will be from the design perspective. Everything will be going from scratch considering the different extract and personality migration and the content folders that are there in the Stream airport will be used as it is. So I will just us the protein members to take a look at the content again on what will not stream it that's because that is going to be on the docs page for the cost website. Thank you. + +Anil Murty: Sounds good. Thanks for the update guys. The only question I have is and maybe the answer is straightforward as it's already been taking care of his we saw the look and feel of the Dockside a while back. I don't know it was probably three or four months ago and the website effort is obviously ongoing in the last month and ongoing now. How do we ensure that? They both look consistent given you're just going to be pulling in those pages? + +Piyush Choudhary: So to maintain the consistency so we have lost the previous designs from the designers. I think that Miss and By having a property discussions during the workbook sessions. We will make sure that everything looks in consensus with the design. If not be a big trust in front of + +Anil Murty: Okay, Just wanted to make sure that was being considered as Cool any other questions from anyone on the Dockside migration? + +Anil Murty: Okay, sounds good. So tentatively is it fair to assume that the new Dockside would also go live at the same time as the website going like piyush. awesome + +00:25:00 + +Piyush Choudhary: yep, so within next week, I will always drop the link Google drops, which only will be able to see how it's written. + +Anil Murty: amazing. Thank you. All We'll move on to the next one, which is on chain Analytics. + +Anil Murty: I know Cloud most made a whole bunch of updates to their analytics last time. I don't think you guys have spent a lot of time on this since the last session but I did notice that there was one more person that was suggesting a new idea on the signaltics Discord Channel. I don't know that person is on the call here. But if you are definitely speak up and talk about anything that you're proposing in terms of Analytics. But I don't know max if you have any updates on analytics that you would like to share. + +Anil Murty: You maximum. Not sure if you're speaking but I + +Max: Oops like that. Thanks my microus unit. And so yeah, not so much on the casualtakes dashboard per se but last updates that we deployed were for the providers on the provider list page mainly the list. We added the GPU models and quantities + +Max: and yeah, that's pretty much it for the analytics for now. + +Anil Murty: Awesome, and I'm trying to figure out who the other user was. There was commenting on sync Analytics. + +Anil Murty: Yeah, so that person goes by fiber. I don't know they're on the call, but I noticed they posted a YouTube recording of potential hackathon idea that they didn't get into that icon in time, but it seemed pretty promising. It's pretty early. But if that person is able to join the call next time we can probably hear about. + +Anil Murty: awesome But what are the next thing and this is other things we plan to bring up. Provider attributes here. I know it's almost team has done a bunch of work to add a UI within Cloud most to be able to adjust and set provide attributes. There's two things. I wanted to bring up in the context of Provider attributes. And then max if you have anything else, please free to feel free to jump in as well. The one thing I was going to bring up was we did notice that there was an issue where if a provided sets the attributes using Cloud most UI and then the provider restarts itself, then the ethical skin wiped out. So that's something for people to be aware of it's something that we still need to solve. We don't have a solution to that today yet. So if you're using the provider attributes UI today, that's something to keep in mind is that there is a + +Anil Murty: I don't want to call it a bug but a limitation where it will wipe out your custom attributes that you create. The other thing that I want to mention in the context of Provider attributes is + +Anil Murty: In the next Network upgrade that's coming up in the next few days. Arthur is going to be adding support for being able to receive ributes some attributes in the bid requests itself. So specifically Arthur is going to be adding generally supporting attributes in the bit request and then specifically adding support for GPU attribute so that when you request GPU resources from the network from a provider, you can also see What GPU model you're going to be getting in those requests and that's going to be a huge ad because it's really hard to know what you're getting today because if you request a sdl with no gpus model specified you just get the provider name back and nothing else other than that. so, I don't know Arthur if you wanted to add anything more to that, but I just wanted to bring that up. + +Artur Troian: No, pretty much. I think we discussed it all on the sick chain last time. + +Anil Murty: Okay, sounds good. The next one's authorize pen management. I think most of the work that is outlined in the PRD here is complete at this point within Cloud most. That's correct. Right Max. So I was going to ask if if it's okay for us to change this to release at this point. + +Max: If it's okay to release what sorry. + +Anil Murty: Yeah, meaning are we done doing the things we wanted to do for Arthur I spend management. I think you've implemented most if not, all of the stuff that was called out in this TRD, right managing it from the grantee side all of that ux. + +00:30:00 + +Max: yes fully functional. The only issue is one that we talked about in that Arthur I think is working make The Artsy persistent for more than one deployment. + +Anil Murty: So yeah, and that's more of a core Bond. That we need to solve the core. and there's a issue open for that. Okay. Sounds good. So I'm going to go ahead and say this to release on this anybody Is released on this anybody has any concerns with that at least from a UI standpoint. + +Anil Murty: next one's content moderation Most of the work here is being led by the pretor team Deval and jigar. So I'll give you guys the chance to talk about any updates that you want to share. + +Deval Patel: and yeah, so for that we give the demo in the Sig providers meeting last Wednesday regarding attributes of blocking wallet address images and as well as the certain hostname we are working on the UI to the like to do that from the printer part as well as we are going to have the + +Deval Patel: CID for Content moderation, so we are working on that part. But we are making good progress and hopefully give another demo on the next required or something and before that even released to core team members the binary so it can check and we put the pull request like we're going to put the question as well. + +Anil Murty: Thank They will and this is also good segue to point out that there is a item on the Akash project board for this and there's updates in there along with the link to the video that they will be talking about. + +Anil Murty: And I think we can kind of skip or the rest of the items here because there's isn't any active worth happening on these unless somebody wants to bring up. Anything that we haven't talked about yet? + +Anil Murty: Square piyush + +Piyush Choudhary: Yeah, we haven't talked about the discussions that is and the kind of proposal that is on bit of discussions that is related to AI assistant deployment during the system lines the SGL generations to automation. + +Anil Murty: Yeah, so that's kind of the next item. So we typically go through the list of projects that are in progress and then we jump to the discussions, but certainly get to that. Good Tyler. + +Tyler Wright: Real quick. I think Anil you mentioned it very quickly, but there will be information that's going out to validators. Another folks in the community soon around that mainnet eight upgrade. there should be a proposal that's going up for vote over the next day or so. And then from there we should again have an upgrade at some point late next week for validators and providers archers actively working on a number of things and we'll again update documentation. So I just want to mention that to folks here so that whether they're validator providers themselves or they're an Insider or Vanguard, they can start sharing that more widely are just know that it's coming down the pipe and that's again related to I think. + +Tyler Wright: Feeling any of looking at it right now, but the issue here that was talked about an issue support number 124 that the big attributes requires a network upgrade. So again, that's what we're planning for. We talked about in sick chain, but just for folks that did not attend that all just look out for a validator node upgrade and it will be a provider upgrade. I think just a bump upgrade nonetheless happening over the next week or so. + +Anil Murty: Thanks for bringing up that Tyler and the main feature as Tyler mentioned is Attributes in the read requests and that issue here is on the board as well. So that's a primary reason for the upgrade. And then I think we had talked about potentially creating a main date upgrade issue as well. Right? Tyler, I don't know if that's still the plan. But if it is we can add that word. + +Tyler Wright: Yeah. + +Anil Murty: Thank you. Anything else anyone wants to bring up on the projects list before we move on to discussions. + +Anil Murty: move on to discussions So typically what we try to do here is we try to review most of the proposals or discussions that came up since the last time we met in the steering committee. But this seem to be a fair amount of those this time. So what I'd like to do is focus on only the ones that people are able to talk about so either the person that is written the discussion or somebody who's able to represent them. If they're on the call, then we'll talk about it. If not, we won't So I'd like to talk about one that I've been driving and that is this Foundation model retraining effort. So to give people a general update on this the proposal went on chain after the last steering committee meeting and it's been approved. And as of this morning we are in process of getting this training started. + +00:35:00 + +Anil Murty: The one key thing to point out here is that we initially thought about doing this training using stable diffusion 1.5 was what was proposed initially? + +Anil Murty: that was primary driven by the fact that stable diffusion is pretty popular and we chose 1.5 because you wanted to keep the cost low doing two dot stability in two dot o would have increased our cost potentially up to five times because of the serial number of parameters that stability into Rodrigo has as we were getting ready to get this going a lot of things we did were, basically testing out a cluster from a provider making sure that we can actually use that for this training before we actually commit to it. and over the course of that, that took a few weeks and as we were just about to keep this off what we noticed was that there was a new paper published by The folks over at databricks specifically the Mosaic ml folks working with the team at Cornell. + +Anil Murty: And this paper essentially talks about exactly the same idea which is taking a image generation model and using creative common data set to train it and those people are published. I believe on Wednesday of last week, so it's relatively new. And so once that people came out, they plan was to use table deficient 2.0 to train it with a Creative Commons data set and essentially to exactly what we were planning to do. So we basically had a discussion between Thumper and ourselves and we talked about, does it make sense for us to stay train with stable deficient 1.5 given that potentially going to be this model that's trained on stable diffusion 2.0 with the same Creative Commons data set and + +Anil Murty: One part would be to continue down the path of doing 1.5 and potentially be inferior to the southern model. The other path would be to switch to 2.0. But that would be a significantly higher cost than what we asked for in the proposal. A third path would be to pick different model that. Is very competitive to stabilifusion and luckily we were able to identify a model called art Pixar Alpha that is based on a diffusion model and claims to result in images that are of much higher quality than stable if you're in 1.5 so they came to be as good in quality as stability Fusion Excel, which is basically the most latest and greatest model from stability AI. + +Anil Murty: so what we have decided is to switch that portion of this proposal from stable decision 1.5 to fix art Alpha and the intention is we've done testing to make sure that we can actually do the training on that using the creative common data set and the cost of the training should be same if not lower than what it would have costed us to do stable decision one or five. And so that's kind of the plan right. Now. The training is expected to start this week. The provider bring up is in progress right now shimpa. I don't know if he's on the call is working on the provider bring up right now and you'll be seeing a lot of updates from our marketing team through our Twitter handle on this training as it progresses. So if there's any questions, let us know but that's kind of the plan with that, and then + +Anil Murty: I'll keep looking at the chat if there's any questions about that, but I want to move on to the next discussion topic piyush since you're on the call. Maybe you can talk about your proposals. So I know that you are initially proposed a much bigger proposal. The one that is outlined here that included four or five different things including this deployment tool and then Greg you and I had a conversation and we talked about how the deployment tool is the most important thing for us to tackle right now and since then your scope it down to just the deployment tool which is what this proposal is. So maybe talk a little bit about it and we can have a discussion about this. + +Piyush Choudhary: If so responding so much for and going roaming Productions and I would like to thank all the costs protein organizers and at the throne organizers as well. So we participated in the classic account with this project and we surprisingly gone the first price and very good to the choice for selectness as a first winner and we really appreciate it. So this proposal is an extended version of that project only. So basically what we are doing here is + +00:40:00 + +Piyush Choudhary: we have created a pipeline like even the new users for new to Apostle be able to deploy or get started with the cost within just requests. So what this proposal does is it combines AI or Mission capabilities using open source elements specifically trained on the data set of Docker file and hdf files. So basically takes the GitHub report and ask the users of degrades and we'll basically puts the GitHub report from the guitar users account and then it writes a doctor file and it's on and then it will say image as well on its own and then it pushes the + +Piyush Choudhary: The oper image to the personal Docker Hub of the user's account and then it also writes the perfect as working as dual file based on the users input how much his pleasure what's is and story is requirements and all so basically this is a combination of things It's a direct pipeline from GitHub repo the STL file, which can then be deployed using Cloud nodes to a caution + +Piyush Choudhary: I also have the video don't know so it's only wants to see and drop them into the channel. + +Piyush Choudhary: So it's just a quick and… + +Anil Murty: Thanks. + +Piyush Choudhary: it's just a quick and this and repeat that we did as part of backathon and this purpose are presents to Industrial standard product. That will be presentation if we get approved on a proposal. + +Anil Murty: Thanks piy Thanks for walking through that a little bit. So I guess I do have a couple of questions and then if anybody else has any questions you take those as well, but I guess my main questions are this I think is extremely useful as a tool. + +Anil Murty: The sort of three questions number one is outside of people asking the questions that they have using the language interface. + +Piyush Choudhary: up + +Anil Murty: Is it potentially going to be a option for people to do this manually as well as opposed to asking a question into a chatbot? + +Piyush Choudhary: Yep, so it will have the functionality of that as far as we are using that you see. + +Anil Murty: Okay, So basically if I can imagine how this would potentially look like from a user experience standpoint is people coming to Cloud most this is going to be built on top of the cloud most UI. They have the option of choosing either,… + +Piyush Choudhary: we + +Anil Murty: ask a question. Hey, how do I deploy blah application on Akash and it potentially comes up with a container image and an STL that they can use for it. or other option would be they would actually go, point the potential repo to GitHub people as a link and then you'd have a pipeline where you basically look at that create the container image and deploy. + +Piyush Choudhary: that's + +Anil Murty: Second question you talked about in this proposal and again apologize. I'm not read it in super crazy detail yet. I did notice you mentioned training this on a set of 178 thousand rocker files in GitHub folders structures published under MIT. so two questions on this one is if our primary focus is on how does training it on this entire data another way to ask is would this do more than just solve the use case for Akash? + +Piyush Choudhary: + +Piyush Choudhary: If so, basically we are not training on all the data of concerned with 8,000 is just for the reference. So we are refining the database. We are taking this Terror set and then defining it and dividing into small Trunks and then basically what does this data set content is it contains the coldest structure and + +Piyush Choudhary: Output of the file. So basically what will happen is as we are creating a proper pipeline from taking a bit of the code to writing the proper I still file right? So basically what we are doing is when the user is pointing I get to that point to the user interface. AI model is scanning the folder structure and writing the proper Docker file to build the So after writing the docker file on itself dates Docker image and then push the operating is to the personal Docker that the users account and then it sites as jail file using the image that it created on the record. So local file is a part of the pipeline and then also there's + +00:45:00 + +Anil Murty: Got it. how would you intend to manage this as the data set evolved? So is it going to be potentially updates to this as over time as you get new data and you need to retrain this? + +Piyush Choudhary: so Yeah, So basically what's going initially by going to gain the less data set for internal testings. And then I spell the response to the morals and how it's performing what are the responses the failureates ETC we are going to refine the data sets accordingly because we are not asking the uses to write the doctor file on their own we are. Also writing the local file inside the pipeline only in automated fashion similar to what we are doing for the SGL file. So even the users who don't know Docker Hub or Akash will be able to have the working sgc5 to just Deploy on Apache using cloudmuse in place. yeah, and there will be a bit as we train the models and of course the performance and I will also drop the docs that we created recently in the chat or the discussions for + +Piyush Choudhary: how we are going to do Invisibles. + +Anil Murty: Okay, sounds awesome. Just a couple of more questions and I see there's no other questions from anyone. So I'm going to keep going the provider that you'll be training this on. Have you thought about? Who that will be managing that provider? I'm assuming it's going to be an Akash provider. + +Anil Murty: And you did mention the types of resources you expect to use for this in terms of gpus in other things. Have you thought about who the provider is going to be that sort of thing? + +Piyush Choudhary: Yeah, so basically will be using the passion proc for the juices will be meeting the access to the a100 Jeep use about five way so we'll be looking forward to that and the budget that is being request will be spend on the training as well as the hosting part we've also mentioned that when somebody will be released completely for the industry for the public use we will also maintain it for the five months including the hostings maintenance and support. + +Anil Murty: but it Got it. + +Piyush Choudhary: from this budget + +Anil Murty: So a couple of things on that one is if you haven't decided to provide I think Zach os the call. So Zach Ross is with Foundry staking there are provider that has a bunch of a 100. So to be awesome if you could work together with them. To do this video like data set? + +Piyush Choudhary: Get the show. + +Anil Murty: Or sorry on that provider. and then the other thing I was going to ask was do you have a sense for the breakdown between how much the training cost or… + +Piyush Choudhary: So it will be hard to give the exact back we've done right now,… + +Anil Murty: the 63,000 is versus development and hosting + +Piyush Choudhary: but I can drop that out. within next viewers + +Anil Murty: Sounds but yeah, it doesn't have to be super accurate. If you can just get basically a sense of what even 100 hours are going to be and from that we can derive it doesn't even have to be like if it's with an image of 10 20% is fine just or if you can even like a breakdown of input as a percentage like 50 40 60 whatever that is. Okay. And… + +Piyush Choudhary: works + +Anil Murty: then last question is I noticed that in the first proposal where this. Deployment thing was one out of four items that he proposed the cost for the deployment thing was fifty thousand and already 63. + +Piyush Choudhary: he So initially we thought of doing the African giving a proper thoughts on part of the resources are required and… + +Anil Murty: It's like why? + +Piyush Choudhary: doing the property search that as you can see this proposition and also the Integrations with the cloud moves the building of proper APK and points for the proper and the smooth Integrations. So we increased it accordingly. + +Anil Murty: Got Cook sounds good. Yeah, that's all my questions. I think this is a great project amazing proposal really well written. I don't have this people that have other thoughts or questions Julius. + +Piyush Choudhary: Yeah, so Julius also of 8 to 10 people are including the first step developers designers where I am redox, so specifically AIML those are consist of trip people including a blockchain deaths on me and other so there are two blocks index three. Yeah milders who designers and straight instead of Developers. + +00:50:00 + +Anil Murty: Awesome, and I don't know Zach Ross or anybody from The Foundry seeking team if you were listening to this, but I think it'd be awesome. For this training to happen on your cluster or your service. + +Zach Ross: Yeah, I think that's exactly what we're here for. So let's collaborate on that and we're totally open to making that work. + +Anil Murty: It's Perfect. And I think this also give us good marketing. So thankfully you're listening as Yeah, let's see. I mean under any other opposition to the proposal. I think overall he seems like people are in favor of this… + +Piyush Choudhary: e + +Anil Murty: but most something on the comment as well. And so the intention piyush is you'll put this on chain sometime in the next. we go to + +Anil Murty: okay, sounds good. + +Anil Murty: Anyone else on the call want to talk about any other of these discussions? represent the person that has written them. + +Deval Patel: Okay. + +Anil Murty: Go ahead. They will. + +Deval Patel: I got a message from one guy named Joseph on Discord saying he has some Enterprise users he wants to. Put some workloads. You want to showcase us the demo of how the workloads can be uploaded on Akash and how we can host on the services right? If you want. I can give you a call between you and + +Deval Patel: like him right so you can go from there. I Yeah. + +Anil Murty: That sounds great. Yeah, please do hit me up. I'll actually vmu in we can figure out a call between us. + +Deval Patel: Okay. + +Anil Murty: Thank you for bringing that up. + +Anil Murty: Go ahead. + +Tyler Wright: Only thing I'll add I know we talked about in sick economics. I won't talk about it too long. But related to the proposal for the incentivize akt lending pool on nitron. I think there was some good discussion over the last couple of weeks and that proposals since gone on chain. I think number of validators have voted on it already. So I just want to just highlight that because again, it is an active vote being had right now. But again we talked about in the state economics a fair amount and there was some good discussion around it. So I know the person may not be here, but the way through the process and that again proposals up for vote right now, so just want to share that. + +Anil Murty: Great sounds good moving back to this. I guess that's about the extent of today's call. Is there any other General open questions from anyone that you would like to speak up at this point? + +Anil Murty: I guess I'll stop presenting in and things back to you. Later. Thanks, everyone. + +Tyler Wright: Perfect. Thank you very much. Anil for meeting us through the agenda. + +Tyler Wright: I'm again, if anybody has any action items over the next couple of days or weeks, please let me know if anybody wants to demo anything at the next I'm steering committee. Please let me know again, we'll go back to the typical agenda where these happen at the end of the month, but I appreciate everybody making the time today. I know that there's been more people getting active in discussions on GitHub so much appreciate that. I know there's a number of people that reached out about being able to support documentation. with memory many members of the core team being very high for focused on engineering efforts. I'm really calling upon the community to help with documentation. And again, there's a framework that's being developed right now to help structure community and put on documentation side. So, please look out for that soon. But again, please feel free like you can participate in any special interest group. We're working group. There's a lot going on a lot of great discussions having around happening around content moderation and analytics a number others specific action. + +Tyler Wright: teams if anybody needs anything between meetings, feel free to reach out to myself or Other members of the core team insiders in vanguards and again look out for more information coming around that may not main at eight upgrade happening shortly. But no one has any other questions. And again, thank you very much for your participation today. And we'll see you on Discord and in future especially interest group and working group meetings. Thank you all very much. Have a great day. + +Meeting ended after 00:55:58 👋 + diff --git a/committee-steering/meetings/011-2023-12-07.md b/committee-steering/meetings/011-2023-12-07.md new file mode 100644 index 00000000..f73c544a --- /dev/null +++ b/committee-steering/meetings/011-2023-12-07.md @@ -0,0 +1,388 @@ + +# Akash Network - Steering Committee - Meeting #11 + +## Agenda + +- Review / discuss / address any community feedback, grievances, or conflicts. +- Review [projects list](../projects-list/README.md), prioritize / add / remove if necessary. +- A look at open discussions in [Github Discussions](https://github.com/orgs/akash-network/discussions). +- Open up to any other questions from the community. + +## Meeting Details + +- Date: Thursday, December 7th, 2023 +- Time: 11:00 AM PT (Pacific Time) +- [Recording](https://k6mud4r2ua6xarj6c5zqtkxw6fzjrvzjzu6eotsyhsmotles2gaq.arweave.net/V5lB8jqgPXBFPhdzCar28XKY1ynNPEdOWDyY6ayS0YE) +- [Transcript](#transcript) + +## Committee + +- Adam Bozanich, Overclock Labs +- Anil Murty, Overclock Labs +- Artur Troian, Overclock Labs +- Greg Osuri, Overclock Labs +- Scott Caruthers, Overclock Labs + +## Participants + +- Adam Wozney +- Andrew Gnatyuk +- Anil Murty +- Artur Troian +- Benjamin B +- Cheng Wang +- Deathless +- Denis Lelic +- Greg Osuri +- Jigar Patel +- Joao Luna +- just may +- Max +- oo o +- Piyush Choudhary +- Robert Del Rey +- Rodrigo Rochin +- Scott Carruthers +- Scott Hewitson +- SGC | DCnorse +- Tyler Wright +- Zach Horn + + + +## Notes: + +- Tyler asked the community about whether or not anyone had any concerns or issues with the sigs or wgs. +- There were no issues from the community at this time. +- Tyler led the group through the agenda today, because Anil was in a place with a lot of background noise. Anil was still heavily involved in the conversation. + + +### Projects: + +- Tyler talked about the project list that was used in 2023. A lot of progress has been made across a number of different of projects. +- Anil introduced project boards for Product and Engineering. +- There are now boards for Product and Engineering, and another board for Community and Marketing efforts. In the Community and Marketing board, community members can also find bounties that are available to members of the community. +- Please feel free to access the boards here: https://github.com/orgs/akash-network/projects +- Tyler walked through some of the key items on each board. + + +#### [Product and Engineering Board / Community + Marketing Board](https://github.com/orgs/akash-network/projects) + +- Tyler talked about the work that Cloudmos is doing with GPU type in bids. +- Artur talked at a high level about the network upgrades that are planned for q1 2024. These items were discussed in sig-chain and sig-support. +- Tyler talked about the work that Zach and ZJ were doing around sdxl. +- Denis and Tyler talked about the Akash website revamp. The website is in the final stages, and a launch plan will be available soon. +- Adam talked about the wg-hackathon and the work they are doing to get ready for Akash Hackathons in 2024. [Find more here](https://github.com/orgs/akash-network/projects/6?pane=issue&itemId=43793394) +- Adam mentioned that he is planning the first quarter 2024 events right now, now that the budget has passed. [Find more here](https://github.com/orgs/akash-network/projects/6?pane=issue&itemId=43366707) + + +### Github Discussions: + +- Discussed [Community Support Proposal](https://github.com/orgs/akash-network/discussions/394) which was up for discussion for weeks, and then went on Chain for a vote very recently. +- Adam Wozney talked about the success of the program last year, and the continuation of the program, as we head into 2024. +- The group discussed [Github Discussion 406](https://github.com/orgs/akash-network/discussions/406) created by Benjamin. He and his brother want to continue development of work they pitched for the Akash Hackathon 2023, that involves auditing providers and helping with provider attributes work. Benjamin and his brother has been doing research, they have connected with Moultrie Audit, they have shared ideas in Discord, and have created a pre draft proposal in Github to get more feedback on their idea. Now they feel confident to got for community pool funding to bring this idea to life. +- Demos and more details on specific deliverables can be found in the Github proposal as well as the pre draft proposal. +- Greg asked how did they plan to build the business of the provider auditor after initial funding? Benjamin mentioned that they have been exploring business ideas, but will only go to the community pool once for AKT. +- Greg and others in the community want to think about ways to make auditing profitable on the Akash Network. Ideas can be explored on discord or in future working group sessions. +- Other members of the community asked questions to Benjamin, and shared their support. + + +### **Open Discussion:** + +- Tyler mentioned that this was the last Steering committee for the year 2023. +- No one else had any other topics for discussion at this time. + +### Action Items: + +- Benjamin to put proposal on chain for vote. +- Proposals for events and community support expected to go on chain. + + +# **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 steering committee monthly meeting number 11. this meeting has been moved back originally intended for Denver, but with a number of things happening in the community with number of people in steering committee. We've moved this meeting back to today the next steering committee. that is usually at the end of the month. It's going to be moved to the beginning of January with the holidays right around the corner again. We want to keep people time with their families. There'll be a number of things going on in their cost ecosystem over a next couple of weeks. But again, the next steering committee has been moved from the end of the month and it's going to be Thursday January 11th World their kick off, there'll be a couple of cigs and working groups that happen prior to that but it'll really be a kick off to 2024 and then we'll continue with the regular schedule of the steering committee's being at the end of the month with January. So again, we have a steering committee meeting happening today and the next one won't be for. + +Tyler Wright: or another month or so and then we'll have a follow-up at the end of January 2024, but a lot to look forward to Out of the last steering committee that we talked about a number of discussions that have since gone up for proposal. thank you to all those that participated in those discussions. And also those who voted also since then we were getting ready for mainnet 8 and as we kind of talked about in depth in Sig chain that just happened this week since then we've had successful upgrade to mainnet and then made that nine. There's no more plant upgrades for the rest of this year. But again, that's discussed previously in Sig chain. There's a lot happening in the first quarter of 2024. So a lot to look forward to there. + +Tyler Wright: again, there's a number of other items that you all can track. Every steering committee is transcribed. There's notes that I take during these meetings and again, then members of steering committee look at those notes and we make changes to a number of areas and GitHub a much appreciate again everybody that participates in discussions. But with that being said, I know that Anil is moving around a lot today. I'm happy to continue sharing or Neo. Let me know if you want to start the process. + +Anil Murty: Can you give me okay you? + +Tyler Wright: Yes, I can hear you. + +Anil Murty: if any issue with any point, they can always + +Tyler Wright: Absolutely. Yeah. + +Anil Murty: thanks for joining everyone. So as we do if you start with any discussion about feedback from the community. so it's just + +Greg Osuri: Yeah ideal. + +Anil Murty: just yeah. + +Greg Osuri: It's a bit hard to hear You're going in and out for some reason. Is there any way to bring the microphone closer to your? + +Tyler Wright: I + +Anil Murty: I just + +Tyler Wright: I know if you need I can also help and you can just speak when on Focus parts and… + +Anil Murty: Okay good. + +Tyler Wright: I can just do the agenda. No problem. Excellent. + +Tyler Wright: So it's a nail just mentioned as the agenda that you see on the screen right here. The first item that we do is we review discuss and address any Community feedback or even sister conflicts. So does anyone have any comments any issues with how things are being run in the open framework with special interest groups and working groups? + +Tyler Wright: One thing that and I've mentioned this an insiders as well. One thing that I'm looking to improve in 2024 is continuing to make the meetings more accessible for everybody. I also want to add some fluidity. there was a lot of structure in 2023 with the meeting times and I know that people are coming in from all over the world. So it's hard for some folks to make themselves available at the meetings of 2 am local time, but I want to do a better job of the 2024 is making sure that there's a number of key stakeholders at every meeting and so being a little bit more fluid with the meeting times. So that's something that I'm going to be focused on Robert. I saw your hand up. Is there anything that you want to talk about in terms of community feedback? + +Robert Del Rey: Yes, we will quickly. I just noticed that for next week. We don't have the Sealy working group called Adam. I don't know if that's something you can call me out. + +00:05:00 + +Tyler Wright: Yes, I'll make sure that gets added to the calendar. Thank you very much. + +Tyler Wright: Yeah, no problem. I'll add those two calls. So in the following Monday the 18th. Does anyone else have any specific feedback about Community groups? Again, the special interest groups working groups user groups Beyond. + +Tyler Wright: Again, if you don't want to leave any feedback now, feel free to reach out to myself on Discord or anybody else that you feel comfortable talking to and then we'll look to get those items addressed. + +Tyler Wright: cool as the next part of the agenda previously we've used the projects list, which is again a static table that we've been using throughout 2023. I'm gonna start sharing my screen Anil so I can just link people to that. So again previously we've used this table when we're tracking all the items that are being worked on in public. Obviously, you see everything from hackathon to economics 2.0 GPU support which some of these things are in various States released go ahead and deal. + +Anil Murty: Yeah, I was just gonna say hopefully you can hear me better now without the Bluetooth. + +Tyler Wright: Perfect. + +Anil Murty: But yeah, I was gonna say right now. Our project list is essentially split into two sections all the engineering and product work is being tracked in a project board. And then some of the non-engineering work for example events microphones any marketing things those are being tracked still in this list. So I think we can go through them. It makes sense really quickly. + +Tyler Wright: Yeah, no, absolutely. what I was going to say to that point is out of the last meeting. We talked about authorized spend and that is going to be moved into released but we are going to be sunsetting this project list in its current form as a table and instead we're going to be using as Anil just described there is a link and I'll put the link in the chat for folks. There are project boards. There's one for product and engineering and there's another one for marketing and Community efforts where again specific projects are being tracked. So we started using this last steering committee, but we'll start using it today and moving forward. So again, we'll start with the product and Engineering roadmap and we'll just highlight some of the big things that are in progress column and + +Tyler Wright: Up next and then if anybody has any questions, they can ask those here and then we'll move on to the marketing and community board and we'll do the same. + +Tyler Wright: So at the highest level again out of one of the most recent upgrades there. We're allowing for GPU models to be shown in bids. I know this is work to the cloud most team is currently working on and you can see some of the other efforts that are coming out of cloud most repo that Max it and Max are currently focused on and where the focusing their time and energy one of the other big things that's being tracked is a content moderation out of sick providers. the pre-tour team led by jigarh Duval have been focused on out of a working group that we talked about in great detail working group content moderation have been working on management API and moderation API they gave a demo at the + +Tyler Wright: Last six providers meeting and are continuing to work closely with the core team to implement some of these changes into the core code base. Yes. again, all of these items can be tracked and you can look inside and you can track conversations. We try to get folks to update these on a weekly basis. So even in between steering committee meetings folks that have specific questions can ask those relative to a specific project or task and then again look to get feedback from somebody from the core team or somebody else from the community that may be working on some of these efforts. + +Tyler Wright: Go ahead and deal. + +Anil Murty: yeah, I just want to add a high level just say that on the core size are based our main focus at least through the end of this year is on three main things first is implementing this Pro product feature Discovery service, which will let us look at various provider related things whether it's keep your models or the things. From the provider and make them available as a service. So that's kind of number one. This doesn't require a network upgrade. So that is a reason why they're not planning for any more Network upgrades this year. And then the second is supporting AMD and that doesn't require it and supporting amps important because + +00:10:00 + +Anil Murty: if you're in paying attention to the news AMD just had the event this week where they announced their latest generation chipset the mi300 and they've already had a mi 210 and my 250 which are all starting to be very competitive relative to Nvidia. And so, if we can support in AMD on our Network, which is a relatively small effort then, we become one of the clouds that starts to get AMD gpus on the network and that continues to drive demand. so kind of the main things following those two the next thing that is a significantly large effort is for us to look at supporting Secrets, which is important for us to be able to support private containers on the network. This is something that is constantly asked. + +Anil Murty: Was when we talk the customers as well as within the community one of the challenges today is if you want to deploy on akash, you have to make your container public and put it in a public container registry. So that's a significant limitation that you want to try to address. So that's kind of the next up next but the primary things that have been worked on right now at least from a 14 perspective are the provider service and the support for AMD and then of course from the community the Play-Doh team is working on content moderation. + +Tyler Wright: Thank you Again, I know there are a number of items that are being worked on by members of the community and also by members of the core team. Another did a great job of just talking at a high level about a number of things. Does anyone have any specific questions on the product or engineering roadmap in terms of participation. Does anyone see anything here that they want to learn more about and get more involved with? + +Tyler Wright: I know Artur talked again in great detail about the upcoming Network upgrades happening in Hopefully the first quarter 2024. He talked about that in detail during sick chain as well as Sig support. So I don't want to have him repeat himself a number of times. But if anybody has any questions about Network upgrades and planned that Network upgrades happening early in the New Year. Please feel free to look at those recordings. And again, if you have any questions, there will be support tickets made for each upgrade in the support repo where you can track specific items where that upgrade is how far we are from the upgrade time where the testing process is and Beyond + +Tyler Wright: Archer don't feel obliged, but do you want to say anything specifically about Network upgrades or anything else on the engineering roadmap before we move over to the community and marketing roadmap? + +Artur Troian: Just a little probably about planning. So in the past especially this year. we've done quite a few Network upgrades some of them were. Announced not pretty shortly the couple weeks notice what we're gonna try to do. Next year is we try to plan on grades for the quarter. So the next q1 is and having three upgrades scheduled I'm gonna try to lay them out approximately when they're gonna be happening so it's gonna give + +Tyler Wright: Perfect. Thank you Archer. Does anyone have any questions comments about the product and Engineering roadmap before we move on to the other board? + +Tyler Wright: again continuing on with our project list portion of the agenda as previously mentioned many of the items that community and marketing are driven are going to be in this board. So again, if anybody has any specific things that they want to add I know that Adam was head of community has been done a great job of outlining all the specific items, whether they be events for 2024 or other, hackathons or other specific initiatives everything from governance proposals down to again the specific events. So if anybody has any questions, you can kind of see here you can also track what's happening with zealy an effort that Robert and Benjamin are leading in this pilot stage right now. You can see some of these other efforts. I also do want to shout out something that kiwi as well. As other members of the core team are working on is a bounty board. So + +00:15:00 + +Tyler Wright: Again, when there's obviously the overclock lab team is very small and so with the open framework, it's always been a goal to have as many Community contributions as possible across a number of different items. And so making that more readily available so that folks can know how they can participate and can start to earn some akt is something that is going to be a focal point of q1 2024, but even beyond that, I don't know if Huey Cheng or anybody else wants to talk about this more detail. I'm sure there'll be more discussions happening in the future around specific initiatives, but I just want to call out for folks to be able to look at this master view that shows all the various projects. But then again this bounties view that you can get some more specific information. Has heard a hand up go ahead J. + +Cheng Wang: Yeah, thanks for walking through that Tyler and you're absolutely right just to kind of sneak peek a little bit. We're still fleshing out a couple of details but especially as we go into the holiday season, I suppose we passed that first Milestone already. We're kind of into the holiday season in terms of getting the community engaged and for example, Julie DJ has been instrumental part of building, sdxl on a caution others and we'd love to invite more of that on to the network and contributing so we'll definitely update the bouncy board and others to really invite more of that especially over the next couple of weeks and into the new year. So please definitely stay tuned on our Discord on the boards and all that stuff in our Twitter as well. So we will definitely have something come out soon for people to I think get excited about over the holiday season into the new year. + +Tyler Wright: Thank you Cheng. M specifically a couple of things that I want to highlight on this Board website revamp because I see some other folks on this call Denis included. This has been an active effort that's gone on since piyushen team have received community pool spend for the website revamp. They have been very responsive and since they've received funds we've been meeting in public on a weekly basis. I think we're about 20 23 calls deep on meeting again weekly to discuss everything from the website revamp to specific ux and UI changes Dennis piyush. Is there anything specifically that you all want to highlight in terms of the work that's happening with the website reading and obviously again inside here. You can see a link to the staging site where it lives right now and again once it's + +Tyler Wright: Once it's made available and it's public all that the site will be open source, and we'll be available in the website repo inside the cost organization. So I'll look out for that soon. But piyush or Denis you have anything that you want to talk about specifically. + +Denis Lelic: Thanks I think you're pretty much covered everything. We're in the final stages. So we're just at the moment focusing on refining UI and adding proper links content and so on and in the last couple of meetings, we were also covering. Another Sig which is dogs, and we just wanted to make sure that we have this good overall experience in the website. So dogs are becoming part of it as well. So we all hope for to go live quite soon. So hopefully in the next 10 days So, thanks. piyush if you have anything to share, please do + +Piyush Choudhary: So yeah, so since we started working on the gosh website we went. So as we all know that password site remember is being structured with gay police selected Just Technologies Tech and we are committee mostly working on it and we can two weeks. It will be officially I don't official domain astrotment. s + +Tyler Wright: Thank Again. There's a number of meetings that are being added to the calendar for folks that want to participate in helping with content. I know it's something that Zach and other members of the community are looking to again optimize ahead of the launch. So if anybody wants to get involved in some of these last-minute just checking various Pages making sure that the content is there making sure that all the links work feel free to join those meetings and help your part of the final stages of the debugging process. + +00:20:00 + +Tyler Wright: cool I know that again, there was an events gov prop that was on discussions for a while. And then I believe recently went up for vote since passed and it's like a text phase Adam. Is there anything specifically you want to be talking about in terms of events for 2024 and some of the things on the road map here. + +Adam Wozney: Yeah, this would be quick. So yeah, shout out the events of prop his past. So now I'm in the middle of working with three or four different upcoming events for potential sponsorship and figuring out what our presence will look like, but should have more updates on that before the end of the year, but we're on track to kind of get locked in for three upcoming events. + +Tyler Wright: excellent + +Tyler Wright: Next on the list is I know that again. There's a working group session happening around the hackathon tomorrow Friday. It's on the events calendar Adam. Is there anything specific you want to talk about with next steps in terms of the 2024 hackathons? + +Adam Wozney: Yeah, for So tomorrow we're looking to kind of finalize what our governance proposal will look like. Once that's ready. It'll go up to GitHub for discussions to get feedback. And then if there's not substantial feedback, we'll look to get it up for a governance proposal vote. + +Tyler Wright: So again, if anybody wants to get involved feel free to leave a note inside the specific tile or join that working group session that's happening tomorrow. + +Tyler Wright: Our Cheng set it at the top of the call, but I do want to highlight the work that Zach and ZJ have been doing around sdxl on If you go to the link and I'll just drop it in the chat for folks that may not know there's been significant work of just showcasing again the power of the cost Network and the gpus and so again, I just want to shout out Zach and ZJ for the work that they've done there. I know. I know it's a completed item, but I don't know if either of them want to say anything about that work or about any upcoming work that might be available to the community or that they've been thinking about + +Zach Horn: And not uphand stxl's live mystrals coming soon. I'll keep you guys posted as soon as that's ready to push. + +Tyler Wright: excellent again, but if you haven't used it, please feel free to use it. + +Tyler Wright: I know there's a number of other efforts up next and in progress. Is there anything on this board that anybody wants to talk about that hasn't been talked about yet. + +Tyler Wright: Cool, if anybody wants to add anything to this board again, you can add an item in a draft State and then it can be again converted into an issue. So feel free to reach out to me if you need any help with that process. + +Tyler Wright: All Does anyone have any questions again going back to the projects or does anyone have any questions about anything product engineering or marketing Community or related in terms of public facing projects in the projects list. + +Tyler Wright: All right as mentioned again,… + +Cheng Wang: I'd also like to say Sorry,… + +Tyler Wright: go ahead. + +Cheng Wang: I should raise my hand there. I'd also like to say if there are things that the community anyone here is interested in working on that hasn't yet been Scopes and you want to start a discussion or just hit us up on Discord wherever we're definitely open to ideas. So definitely, please if you have a thought or suggestion just one idea. Let us know. + +Tyler Wright: Go ahead Roger. + +Rodrigo Rochin: Hey guys, so I saw the Bounty for the blender. Sdl, but there had also been one already in the awesome people. Just wondering if the county is still ongoing not, I don't think it's been marked test complete but that is the others gonna be accepted or not. + +00:25:00 + +Tyler Wright: Perfect. + +Tyler Wright: Again, the project sport lives inside the cash organization. If you go to Project you can track in real time what's going on across engineering and product efforts as well as community and marketing if you're looking at specific tiles on a weekly basis, whether it be folks from the community or members of the overclock Lab Core team, we try to update those specific projects. So again, if anybody has any questions, feel free to drop a question and a project or just look out for those updates on that tend to happen on a weekly basis and again, shout out to pray to our team for all the work that they're doing the Cloud most team for all the work that they're doing and obviously remember many other members of the ecosystem that are helping with core product things and a number of other initiatives + +Tyler Wright: cool next up on the agenda. we'll go through discussions again our lab usually we go to discussions that happened in between meetings the last year and committee I believe was at the beginning in November. So I think it's been a little bit over a month since the last time we've talked + +Tyler Wright: usually we also try to have people that are presently here that want to talk about their discussions. Is anybody here that we can give the most time to anybody? I know Benjamin you are here and I know that Benjamin you put in a pre-proposal that got some feedback and now you've put in a proposal for miscellaneous contributions and creating a new auditor with open source tooling. Do you want to talk about this proposal for a minute or so and then again we can get some more feedback from people in the community and hear from the steering committee. + +Benjamin B: Yeah, please give me one minute so I can prepare everything. + +Tyler Wright: Absolutely while he's doing that again, there have been a couple of other proposals or ideas that have gone in there. We won't talk about the ideas here. Unless anybody wants to talk about them specifically, but if you have any feedback, whether it be members of the steering committee in core team or again members of the community, feel free to drop in feedback related to some of these ideas here. I know that again. There was a community support proposal that went up online as well Adam. Do you want to talk about this while we wait for Benjamin, are you get to go? + +Benjamin B: Yeah, I'm good to go. Can I share my screen? + +Tyler Wright: Absolutely. All So again welcome we're going to be discussing very very briefly The Proposal 406 by Benjamin + +Benjamin B: Also, let me just share my screen. All great, so Me and my brother have been working on this little project where we started on the caution phone hackathon. where we got the idea and started creating some and basic demo and basically showing what the idea would allow. We started by creating this discussion. I believe this is three weeks ago. and this was not discussed last meeting either. + +Benjamin B: Basically, I'm not going to explain everything here because we have made several demos here. But I just want to explain where all information is available. Basically, we start with this predraft discussion. We wanted to explain what we wanted to develop. we scraped this but we turn this into an integration instead we explained how much resources it would take. and we discussed with the community if + +Benjamin B: if the funding we're asking for is firing or not. Then we got great number of people responding with a lot of feedback. + +Benjamin B: we applied it and created a final proposal draft here. Unless there is a major feedback on something that needs to be changed. We also created some market research where right now there's only 11 responses. I know that there is a chance that this will go out in the Akash, what is it called? + +Benjamin B: I don't really know what the emails that are going out from I will include this form link right now. We have 11 responses. And basically for each question. 90.9% is currently voting in favor of the market research questions so this does not include the details, but just whether or not and this would be needed or not. And lastly we have this draft proposal. We have created some. from science information here + +00:30:00 + +Benjamin B: with everything related to proposal. Please feel free to ask any questions. + +Greg Osuri: from + +Greg Osuri: what are the exact deliverables? + +Greg Osuri: Is it and timelines + +Benjamin B: Let me see we have. this for our general ones, but here we have a bit more explaining and if you refer to the previous discussion, you will have more details on each service. We will have both code so that anyone will be able to spin up their own service, but we will also host it ourselves. + +Greg Osuri: What is your moral post-funding? How do you plan to sustain yourself? + +Benjamin B: I discussed this a little With someone from the community a little so right now. We don't have any plans. We just have ideas on expansions. We're not going to go to the community pool again. but basically our idea is that regardless if it will be a big money maker for us or It does not matter for us. We will keep it running for as long as we can and for as long as it makes sense. Then we will. double with ideas of + +Benjamin B: let me see. I have the ideas written down. in a few seconds + +Benjamin B: so yeah, some of the ideas that we might explore or For example Golden Tears. We could have the money back guarantees if the providers were not Of the good service we could have the feast on the kycs. And then we also have some other ideas, but we probably don't want to try this out. These are paper lease advertisements and such. + +Greg Osuri: think it's important for the in general Akash Network as a whole in community to incentivize Auditors so far it's unincentivized and people are doing out of their Goodwill like yourself But this leads to another important aspect that we need to have a broader discussion. I do like the idea of creating a more automated system and open sourcing it. So anyone can run it but I do like the idea of you running it and what we need to work on is a more sustainable way to fund your operations not only your operations, but all about all auditor operations, but From a deliverable standpoint. I support this proposal. + +Greg Osuri: Someone had a question. + +Tyler Wright: I saw I had a PhD every hand up and I saw that dcnorse put a question or put something in the chat, but Pierre said you have your hand up. + +Piyush Choudhary: If so, I have a question regarding how that we are based rating will be established. is it an automated approach or in some other way? Is it a manual approach for the provid? I saw there was some discussions going on regarding putting a clear based ratings for the providers on so this proposal. + +00:35:00 + +Benjamin B: Yeah, I think this depends a little on how deep you want to go because if you were to create a provider and the cheapest lease you have is like a hundred dollars or maybe you're not accepting all leases. It could be hard to Benchmark so in that sense We might have to explore ways to get those providers to allow these benchmarks. But beyond this we will collect all possible information. Without forcing providers to do something. So a lot of information is trackable without creating a single deployment. and for this so-called audits and they provider doesn't have to do anything. Does this explain a little or? + +Piyush Choudhary: yeah, and besides of time presentation and kyc all the deliverables of your presentation. + +Benjamin B: Besides kyc and what was telling? + +Piyush Choudhary: Update that is right now there on the cloud notes. + +Benjamin B: Yeah, so we plan on for example a benchmark the providers via deployments. This includes most resources This Etc. Where you can de different benchmarking images We also have the ones for RPC nodes. We want to verify that they still work and provide up to date lists. because one issue that we've been seeing a lot recently is this was especially Visible when we had the network upgrades and… + +Piyush Choudhary: Hey. + +Benjamin B: they didn't go super Some of the RPC notes, even though some worked some just didn't work at all. They were online. But they didn't help you connect to the Shane. So one thing is that we will also include RPC notes. There are a lot of things mentioned both. Here in the latest discussion and we refer to the previous one as well. And we have a lot of details here as well. + +Piyush Choudhary: Okay and final question, so let's say there are 10 providers in the ecosystem. Let's assume there are 10 providers and you launch this auditor with the all terms. what makes what things you will be tracking the most and what makes a top here. And what makes a provider a lot of you as for your rules that will be defining in this tool so it would be great if you cannot of wordings in this indexed adding a little bit explaination What makes a provider load here as well the rules that will be defining the restore and besides pic of time CPU and stories that is there on the cloud most indexer or deliverables that will be there to your proposal so it could be great to see what are the major goals of this proposal you can + +Piyush Choudhary: Consider adding the words. So yeah, that's our + +Benjamin B: Thanks for all the questions. we want to leave a lot of this to the user itself. So we will try to create a filtering system. So both in Cloud most and Via STL you'll be able to Define these to yourself. But for the general auditing we will have this in two different ways. The general auditing will be more so kind of how multi audits has been working and the + +Benjamin B: Not a culture official auditor, but I'm not sure what it's The one and it's helping to run. Basically for the general auditing we don't really have an asset. + +Benjamin B: Anything set yet. we could definitely discuss What users think here? We want to create us at the criteria that are good enough written here, but we don't have anything set in stone yet. For the other system the user could for example say that My provider needs to have 95% uptime or more. My provider needs to be at least one year old and it needs to have kyc. + +00:40:00 + +Benjamin B: These tears that we're going to include in our auditor. and will be possible to filter both via STL and their cloudmose regardless of how you want to mix them together kind of like a puzzle. Does that answer your question? + +Piyush Choudhary: Okay, I think it answered. So basically you are trying to create a filtering system, So as you said the user will select I want my provider to be one year old. I want to provide her to be or 95% of time or something like that. Is that correct? + +Benjamin B: Yes here is also. Quick demo. I created how it could look like so you could choose. This is just paste of cloud. Most API. but basically + +Tyler Wright: I think this is great conversation. I would just ask that if anybody has any other questions that they would like to have been and his brother asked feel free to drop those in this discussion. I know that we got some great feedback from Greg and his support for again this proposal if anybody else has any questions, feel free to drop it in there. Does anyone else from the steering committee have anything they want to mentioned piyush go ahead real fast. + +Tyler Wright: Yeah, no. No again. I really appreciate the questions piyush it if anybody else I think questions. I see some comments also in the chat if you can add those questions and comments to this proposal. It'll help Ben either add some of these items to the proposal wording or again think about next steps. Once Ben's ready to move forward then again, this will go up for vote. And then if it passes then very similarly to the working group for the cash website. We'll make sure to either track this via sick providers or create a special working group where we can get updates from Ben and team folks from the community can help in a decision making process for some of these fine or tune details. But yeah, those are next steps is I see them. + +Tyler Wright: I know there's a couple other discussions. I know we only have 14 minutes left. Does anyone else have anything that they must talk about right now? That can't go into the discussions post? Will bend much appreciate you taking the time to walk us through. That I'm going to start sharing my screen again, and then we'll continue moving down some of the discussion boards. Because I know we have a couple of other items that we want to get to. + +Tyler Wright: All Ben was getting ready. I know we were talking at the highest level about a proposal that Adam wozney put on for the Akash Community Support proposal. It is something that passed last year, it's again a funding mechanism for vote for folks in the inside of vanguard's program Adam. Is there anything specifically that you want to talk about this proposal before we open up to questions from the steering committee and other members of the community? + +Tyler Wright: Excellent. Does anyone have any questions comments concerns about this Cosh Community Support proposal? + +Tyler Wright: Again, feel free to drop those comments in The Proposal in the next couple of days before they look to put it on chain for a vote. + +00:45:00 + +Tyler Wright: Anil talked about this at the top but someone was asking about private doctor containers, and I know that's very much on the road map. So we'll keep that issue open and continue to track that via again the project board on the engineering side as we're continues to get done there. + +Tyler Wright: Continuing to look down the list. Is there any other discussion that anybody wants to talk about right now? I know we have a little bit time if we want to talk about any of the ideas before we jump into the next part of the agenda, which is an open discussion part. But does anyone want to talk about any of that GitHub discussions go ahead Robert? + +Robert Del Rey: Yes, not committee particular product question for Greg. I noticed that when community members want to propose One of the questions that Rick asked is how are you gonna sustain yourself in the future? So Greg, I like to ask What are other questions? proposers to be ready to answer in future. proposals discussions if that makes sense + +Tyler Wright: Yeah, I'm you Greg. + +Greg Osuri: For me, it's deliverables. Are there going to be open source or not? And what are the expectations after they're delivered? Do you expect to get more funding do you expect to make money or do you expect to work with a network to figure out a system of mechanism, a lot of times when we've seen cases where you build something you're excited and then you want to make money on it. Being open source makes it very complicated to make money. and then you start taking shortcuts and that goes against why we needed the tool in the first place, right? So it's really that simple I don't keep too many belts and vessels. I mean it's really about what are your plans in the future about how to make money, right? + +Greg Osuri: so it kind of sucks as a builder when you go build something and then you can't figure out how to sustain it how to make money on it, especially if you quit your job and do things like that, right so I don't want to set the expectations very clear up front before you start, having your own expectations. Keep it simple. I don't really have too many other questions. + +Tyler Wright: Does anyone else have any other? things that they want to talk about as pertains to any of the open GitHub discussions + +Tyler Wright: cool All right. Now we'll move to the last part of the agenda, which is open discussion. I know we have about nine minutes left again. I know there's a number of events happening and the next couple of weeks whether it be a public Insider office hours, very six and working groups as we wind down the rest of 2023. But is there anything else that anybody wants to discuss with members of the steering committee? And then other members of the community here on this call? + +Tyler Wright: presentation All if not, then again much appreciate everyone's time today. I know that we'll be talking a significant amount. + +Tyler Wright: Perfect dcnorse's dropped something in the chat. So again, if you are want to take a look at it feel free, but again much appreciate everyone's participation today. This is the last steering committee of the year. So again, one of thank everybody for participating this year. We've had 11 of these meetings and it's just been + +Tyler Wright: To continue to evolve these meetings get more folks involved, push some of these items from ideas that GitHub discussions to proposals the community pool and then to actual deliverables. So as we move into 2024, obviously, there's been a lot of learnings from 2023 as we created this open framework when 2024 I think there's a lot of momentum again, we're continuing to learn we're continuing to grow and so 2024 was really going to hit the ground running. So look out for a number of different vehicles that we're looking to get more people involved from the community from down tease to incentives to other forms of people keeping people connected. We're going to try to make it as clear as possible a number of different ways where people can get started whether they want to get started as a community member or whether they want to get started using the product. So again, + +00:50:00 + +Tyler Wright: You want to get Hands-On if you want to help with any of these efforts, I know a number of you hand are already in insiders. But please please make your voice known and continue to express yourself on ways. You want to get involved things that you see that can be improved and we'll just continue to work together to make the cost Network where we all know it can be. If no one has the other questions and again, Happy Holidays to everybody happy New Year, but we'll certainly talk in other meetings before the new year. But again, because this last year and Committee just want to for those watching this much appreciated everyone's effort and hope everyone has a happy and safe new year and we'll talk again and January or 11th will be the next steering committee 2024 and then we'll just continue to build out the Akash Network. + +Tyler Wright: All right, Hope everyone has a great day. Thank you all again. + +Greg Osuri: Thank you so much. + +Jigar Patel: Thanks. + +Robert Del Rey: Thank you. Tyler. Stay safe everybody. + +Cheng Wang: Thanks, everyone. happy + +Benjamin B: Thanks, everyone. Bye. + +Andrew Gnatyuk: things bye guys + +Meeting ended after 00:51:50 👋 + diff --git a/projects-list/README.md b/projects-list/README.md index 99bca470..93934ebc 100644 --- a/projects-list/README.md +++ b/projects-list/README.md @@ -17,16 +17,17 @@ These are all the projects that are currently in some state ranging from "ideati | Project Name | Label | Description | Community Group | State | --- | --- | --- | --- | --- | -| [GPU Support](../wg-gpu/prd.md) | gpu | Everything related to supporting, launching and growing GPUs on Akash | [wg-gpu](../wg-gpu) | beta | +| [GPU Support](../wg-gpu/prd.md) | gpu | Everything related to supporting, launching and growing GPUs on Akash | [wg-gpu](../wg-gpu) | released | | [Stable payments & Settlement](../sig-economics/stable-payments-and-take-rate.md) | | Ability for tenants to pay for deployments using other cryptocurrencies | [sig-economics](../sig-economics/README.md) | implementation | -| [Economics 2.0](../sig-economics/akt20-prop) | econ-2.0 | Redesigning Akash Network's economics model to have fine grained take rates to fund product development and sustainability of the chain | [sig-economics](../sig-economics/README.md) | implementation | +| [Economics 2.0](../sig-economics/akt20-prop) | econ-2.0 | Redesigning Akash Network's economics model to have fine grained take rates to fund product development and sustainability of the chain | [sig-economics](../sig-economics/README.md) | released | +| Akash Website Revamp | | Implement new website with refreshed designs and more maintanable tech stack | [wg-website](../eg-website) | Implementation | | Certification Program | edu-cert-prgm | Define, build and finalize Akash Network Certification Program | [sig-education](../sig-education) | implementation | | Event Planning 2023 | | Define purpose, lineups, and attendees (and weight of OCL presence) for events that Akash Network would attend | [sig-community](../sig-community) | Implementation | -| [Akash Hackathon](https://github.com/orgs/akash-network/discussions/100) | | Define purpose, structure, timelines and outcomes | [sig-community](../sig-community) | Implementation | +| [Akash Hackathon](https://github.com/orgs/akash-network/discussions/100) | | Define purpose, structure, timelines and outcomes | [sig-community](../sig-community) | released | | [Docs site migration](../sig-documentation/documentation-structure.md) | docs-site-migration | Migrating the documentation site from gitbooks to something automatable (Hugo?) | [sig-documentation](../sig-documentation) | implementation | | [On-Chain Analytics](../sig-analytics/prd.md) | | Build data pipeline and analysis tool for onchain analytics | [sig-analytics](../sig-analytics) | implementation | | Provider Attributes | provider-attr | Defining an attribute schema for providers and getting providers to incorporate it | [wg-provider-attributes](../wg-provider-attributes/README.md) | implementation | -| [Authorized Spend Management](../sig-clients/akash-console/prd-authorized-spend.md) | authz | Supporting Authorized Spend (AuthZ) in Akash Console | [sig-clients](../sig-clients/README.md) | implementation | +| [Authorized Spend Management](../sig-clients/akash-console/prd-authorized-spend.md) | authz | Supporting Authorized Spend (AuthZ) in Akash Console | [sig-clients](../sig-clients/README.md) | released | | [Content Moderation](../wg-content-moderation) | content-mod | Tools and process for ensuring that providers have visibility into workloads running on them and controls to ensure they don’t violate their terms of service | [sig-providers](../sig-providers) | implementation | | [Client Libraries](https://github.com/akash-network/community/blob/main/sig-clients/client-libraries/prd.md) | client-libs | Libraries for deploying on Akash programmatically using various programming languages | [sig-clients](../sig-clients/README.md) | implementation | | Provider Services Microservices Refactor | provider-svc-split | Splitting Akash Provider Services into microservices so that we’re able to release and maintain software better | [sig-providers](..//sig-providers) | implementation | @@ -58,6 +59,6 @@ A project may be in one of these states. Note that every project does NOT have t | design | Technical Design is being worked on (typically by SIG(s) ) | implementation | Actual work to bring the thing to life is happening (code being written, event being organized, docs site being updated) | | | beta | The project is in beta test phase (where/ when applicable) - typically for products/ features | | -| release | The product/ feature has been released to everyone (general availability) | | +| released | The product/ feature has been released to everyone (general availability) | | | blocked | The project is blocked or stalled because of some reason (documented) | | | abandoned | The project has been cancelled because no one is willing to shepherd it | | diff --git a/sig-analytics/README.md b/sig-analytics/README.md index 39ffcfef..df53111a 100644 --- a/sig-analytics/README.md +++ b/sig-analytics/README.md @@ -10,9 +10,9 @@ Analytics Special Interest Group is dedicated to defining and building tools tha # Meetings -### Monthly on the second Thursday +### Every Two Months on the second Thursday -#### Feel free to join every month. See meeting table and calendar for specific times. +#### Feel free to join every other month. See meeting table and calendar for specific times. #### [Add the Akash Community Group Calendar](https://calendar.google.com/calendar/u/0?cid=Y18yNWU1ZTM3NDhlNGM0YWI3YTU1ZjQxZmJjNWViZWJjYzBhMDNiNDBmYjAyODc4NWYxNDE1OWJmYWViZWExMmUyQGdyb3VwLmNhbGVuZGFyLmdvb2dsZS5jb20) @@ -27,10 +27,16 @@ Analytics Special Interest Group is dedicated to defining and building tools tha | #5 | Thursday, June 08, 2023 09:00 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-analytics/meetings/005-2023-06-08.md) | [Link](https://github.com/akash-network/community/blob/main/sig-analytics/meetings/005-2023-06-08.md#transcript) | [Link](https://vgq4z3pl2yzp66ubgyz4e6fm6yqh6shzdo22wkk6tucodjy2n6tq.arweave.net/qaHM7evWMv96gTYzwnis9iB_SPkbtaspXp0E4acab6c) | #6 | Thursday, July 13, 2023 09:00 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-analytics/meetings/006-2023-07-12.md) | [Link](https://github.com/akash-network/community/blob/main/sig-analytics/meetings/006-2023-07-12.md#transcript) | [Link](https://gf7f7walagqjm3o6iojm7scckok44sulmjm7k77n2ank3bjsbzyq.arweave.net/MX5f2AsBoJZt3kOSz8hCU5XOSotiWfV_7dAarYUyDnE) | | #7 | Thursday, August 10, 2023 09:00 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-analytics/meetings/007-2023-08-11.md) | [Link](https://github.com/akash-network/community/blob/main/sig-analytics/meetings/007-2023-08-11.md#transcript) |[Link](https://kqbknw24m7hpcjg4hfd2dtg4ozhiqsi4zbjdtjycxw6omyhzvfka.arweave.net/VAKm21xnzvEk3DlHoczcdk6ISRzIUjmnAr285mD5qVQ) -| #8 | Thursday, September 14, 2023 09:00 AM PT (Pacific Time) | | | -| #9 | Thursday, October 12, 2023 09:00 AM PT (Pacific Time) | | | -| #10 | Thursday, November 09, 2023 09:00 AM PT (Pacific Time) | | | -| #11 | Thursday, December 14, 2023 09:00 AM PT (Pacific Time) | | | +| #8 | Thursday, September 14, 2023 09:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-analytics/meetings/008-2023-09-14.md) |[Link](https://github.com/akash-network/community/blob/main/sig-analytics/meetings/008-2023-09-14.md#Transcript) | [Link](https://t5tmhypnhybd3jpbk3amizf6m2pl66msvvbhlqjyqnynouil4ksa.arweave.net/n2bD4e0-Aj2l4VbAxGS-Zp6_eZKtQnXBOINw11EL4qQ) +| #9 | Thursday, October 12, 2023 09:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-analytics/meetings/009-2023-10-12.md) | [Link](https://github.com/akash-network/community/blob/main/sig-analytics/meetings/009-2023-10-12.md#transcript) | [Link](https://v5ixigio4enkf7qhvlmzfptnlx6zkdite2skrznyil2d3xih6ana.arweave.net/r1F0GQ7hGqL-B6rZkr5tXf2VDRMmpKjluEL0Pd0H8Bo) +| #10| Thursday, December 14, 2023 09:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-analytics/meetings/010-2023-12-14.md) |[Link](https://github.com/akash-network/community/blob/main/sig-analytics/meetings/010-2023-12-14.md#transcript) | [Link](https://ek6ahcmxfv2mnwpitrfidefkzfm6razh4zlv7cuowuue5tnrqy4q.arweave.net/IrwDiZctdMbZ6JxKgZCqyVnogyfmV1-KjrUoTs2xhjk) +| #11| Thursday, February 15, 2024 09:00 AM PT (Pacific Time) | | | +| #12| April, 2024 09:00 AM PT (Pacific Time) | | | +| #13| June, 2024 09:00 AM PT (Pacific Time) | | | +| #14| August, 2024 09:00 AM PT (Pacific Time) | | | +| #15| October 2024 09:00 AM PT (Pacific Time) | | | +| #16| December, 2024 09:00 AM PT (Pacific Time) | | | + diff --git a/sig-analytics/meetings/010-2023-12-14.md b/sig-analytics/meetings/010-2023-12-14.md new file mode 100644 index 00000000..f8b94622 --- /dev/null +++ b/sig-analytics/meetings/010-2023-12-14.md @@ -0,0 +1,142 @@ +# Akash Network - Analytics Special Interest Group (SIG) - Meeting #10 + +### **Agenda** + +- Open discussion +- Review of sig-analytics 2023 + +### **Meeting Details** + +- Date: Thursday, December 14th, 2023 +- Time: 09:00 AM PT (Pacific Time) +- [Recording](https://ek6ahcmxfv2mnwpitrfidefkzfm6razh4zlv7cuowuue5tnrqy4q.arweave.net/IrwDiZctdMbZ6JxKgZCqyVnogyfmV1-KjrUoTs2xhjk) +- [Transcript](#transcript) + +## **Participants** + +- Anil Murty +- Jin Lim +- Max +- Rodrigo Rochin +- Tyler Wright + + +## Meeting Notes + +- Tyler talked about all the progress that had been made over the year with sig-analytics. +- Cloudmos Indexer is now open source, and multiple teams are using the API. +- Shimpa has an archival node available as well. If anyone needs access feel free to reach out to him on Discord. +- Jin shared the progress he has made with [Redash](https://github.com/akash-network/awesome-akash/tree/master/Redash) tool. +- Jin talked about the items that he wants to work on over the next few months, including new views and more data. +- Max talked about how the Cloudmos team is refactoring the API for the indexer. +- Max and team will share updates as items get released. + +## Action Items + +- Redash will be added to Cloudmos templates via adding the Redash to the readme in a category. +- Tyler to adjust the cadence of the meeting to every other month. If anyone has any pressing items, please leave a message in discord, or make a new discussion on Github. + +# **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 analytics monthly meeting number 10. The last monthly meeting was in October. I know that people have been very busy over the last couple of months. So we again canceled the monthly meeting that was scheduled in November. This is the last monthly meeting of 2023. Certainly. There's been a lot of progress that has happened over this year. + +Tyler Wright: I know when the year started one of the big initiatives for this again analytics was to have a open source indexer. I know we explored a number of solutions and the cloudmouth team had been added closed Source solution for a little while and again was able to open source that solution halfway through the year. And so now there is an indexer that's available to folks to use. I know that last meeting shimpa mentioned that he had also set up an archival node for people to use and have access to so again, there's been a lot of work that's gone on month over month in this again Analytics. I know that there's some folks. + +Tyler Wright: Jin talked about some of the work that he was going to be doing over that he'd been working on very closely with the cloud most team and it has recently shared that work over a month ago and I shared messaging in Discord. I'm gonna drop in the chat for folks here and I'll add it to the notes for folks that will be listening in later or just looking to notes later. But Jin I know that you've done a fair amount of work and again added red Dash to awesome Acosta. Do you want to talk about from the stuff that you've been doing lately? + +Jin Lim: Yeah, of course. Thanks So since our last meeting I have deployed dash on Akash and an sdl can be found in awesome Lacoste tie. Just put the link in the chat. And here is the dashboard that I prepared. I just think that as To touch on the growth questions found in the discuss priority. So there's a date range filter at the top that all update all relevant charts and then some charts have their own filters as well. So currently when changing filters queries are running real time so they can take a while to update with the current resource allocations I have set I think the value of this comes from having a little bit more granularity than the cloud muscle analytics page. But the questions answered are all very high level so over the next. + +Jin Lim: Month or so I would like to add some cohort analysis and measure retention and engagement over time. And some issues. I have been having sometimes you need to refresh the page a couple of times before the dashboard will actually load. And I did have a quick question for the cloud moss team. So I no longer have access to the sdl within the cloud mods deploy tool. It says it looks like this deployment was created using another deploy tool. And I have updated the sdl since submitting it to awesome Akash and was looking for a way to find the configuration to update it. + +Max: Which is the other are you talking about? + +Jin Lim: The one that I use for this deployment. + +Max: you're saying it disappeared from the app entirely? + +Jin Lim: Yes, no longer visible within the UI. + +Max: Good question. the way we started currently it's in the local storage in your browser. So if you clear your browser cash. it'll just disappear. So maybe you did that. Or if some for some reason also it cannot finish. your disk space is saturated to the point where Chrome purges his own cash to make sure it can continue to work something like this. So yeah, we plan on improving the Persistence of the STL and anymore stable solution on a server the database or something like this and that the browser cash. + +Tyler Wright: Go ahead and deal. + +Anil Murty: Hey, so just to make sure I understand I think the issue is that. even though the read Ashley post checked into awesome It's just not getting pulled into claremos. Correct Jin. + +Jin Lim: I know so on the cloud Moss deploy tool once you're going to your deployments click on the active one and go to the update page it no longer shows the sdl in that section. But yeah. + +00:05:00 + +Anil Murty: voice I see + +Jin Lim: But thanks for clearing that up Max. + +Tyler Wright: Go ahead Rodrigo. + +Rodrigo Rochin: So my issues a little similar but different I was experiencing. for some reason on cloud moves the certificates are not loading again, but now that Max said that maybe due to the cookies and culture setting probably that's why I think + +Max: Yeah, this certificates are stored the same way as the sdls in the browser cache or local storage rather. + +Tyler Wright: awesome Thank you Jin for that update. I gotta make sure that the dashboard content cost - XYZ that you linked here is in the notes so that other people have access to do it all also share it in Discord. So people can see it there but much appreciate all the work that you've done and then what you're thinking about doing next steps for this red. + +Tyler Wright: Cool, max. I know that you've been doing a fair amount of work or the cloud most team has been doing a fair amount of work on improvements to the indexer and has been working very closely with the praetor team on some endpoint stuff. Is there anything that you want to highlight or this analytics special interest group? + +Max: nothing specific in terms of stars that we're adding, but mostly + +Max: what we're working on currently is to refactor the API. And all the routes they're exposed from the API. Which will be documented and version? currently, it's like just an API that we may or our own personal user or for the website use and a lot of people started using the endpoints just because they're exposed and you can use Calling them from your own API stuff. So I know a bunch of people including Rodrigo, Nicole. are using the API endpoints from Carlos API, and if we refactor all of these and release it a lot of people who have some issues or downtime you further up so + +Max: our plan is to First announce it before everybody sit for sure and Also, maybe support for a short period of time like the old endpoints. Just give a period of Grace for people that are using the API correctly. So. Yeah, keep that in mind when we update the API. + +Max: That's it. + +Tyler Wright: Excellent. Thank you. again, I moving into the new year. + +Tyler Wright: Because we have the indexer set up because the number of people are working on a number of things that are we talked about during steering committee, or we could talk about async. I have thought about changing the Cadence of this meeting. I think Anil is also mentioned it previously to maybe once every two months and then if we need to have working group session for anything in particular we can set those up as one Ops. Does anyone have any issue with that as we move into 2024? + +Tyler Wright: That's how I make that adjustment. lastly, I know anil's on the call and has been leading a number of these efforts and driving in these efforts. I just want to make sure I know is there anything and don't feel obliged to say anything. You can just give a thumbs up. There's nothing but is there anything that you want to highlight on the second analytics side? + +Anil Murty: No, I think those cover everything the read - dashboard is awesome. One thing I was wondering was so I guess first answer your question. I think there's nothing much more the only other thing what mentioning maybe is as part of the cloud most rebranding effort to rebrandt those motions. Akash console will be also factoring out the analytics page into its own separate page. So that's probably the most relevant to this discussion. I'm separate from that. I was just wondering when I go into Cloud moves and search for the dash SDS actually don't find it. So, I don't know if it requires that. The dash SD and be put into some category of sdls and then Cloud most completed, but I think that'd be nice to do. Something but otherwise the data visualizations look great. + +00:10:00 + +Anil Murty: Thanks for all the work on this year. + +Max: Is the ISL on the awesome cash report? + +Anil Murty: Yeah. + +Tyler Wright: I've attached it in the chat. + +Max: + +Tyler Wright: I can reattach it max. If I'll put at the bottom just for easy access. And let us know if it needs to be put in a specific folder like a meal said or anything like that. + +Max: yeah, so the way we do it is we use the readme at the root under the categories. So you just need to add it in one of the categories in the readme and it'll be added to. Clubhouse That makes sense. + +Anil Murty: Stuff that makes sense. + +Tyler Wright: cool + +Anil Murty: I figured that might be it will probably add it to data visualization. And then hopefully it'll show up. + +Tyler Wright: Perfect. Thank you. All… + +Max: That's good. + +Tyler Wright: Does anyone else have anything analytics related that they want to talk about this open discussion part of the meeting. Does anyone have anything that they want to cover? + +Tyler Wright: again much appreciate Jin obviously the efforts of the cloud most team led by the Max's overall slaps here again getting us from no indexer to now and open source index are available to the community so much appreciated the participation of everybody that's been here for these monthly meetings for us again analytics again. I will update the Cadence for these meetings moving into 2024, but please feel free to drop anything that you want to discuss inside the city again analytics Discord Channel and then again, we can spin up one off meeting if we need to or just continue conversations there if we want to talk about anything specific to Analytics. Again, I'm gonna give everybody. + +Tyler Wright: A brand of Applause much appreciate all the time and effort that you all put in. I haven't. Hope everyone has a great holiday season and a Happy New Year and we'll see you in 2024. Thank you all. + +Anil Murty: Thanks, Tyler. + +Rodrigo Rochin: Thank you. + +Jin Lim: Thanks, though. + +Max: See you. + +Meeting ended after 00:13:05 👋 + diff --git a/sig-chain/README.md b/sig-chain/README.md index 1f94f41f..d8d9ea5f 100644 --- a/sig-chain/README.md +++ b/sig-chain/README.md @@ -21,9 +21,22 @@ date: 2023-1-09T00:19:20-08:00 | #6 | Tuesday, July 11, 2023 09:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-chain/meetings/006-2023-07-11.md) |[Link](https://github.com/akash-network/community/blob/main/sig-chain/meetings/006-2023-07-11.md#transcript) | [Link](https://sxisediwxnr2rnn2kq4dte3bkw2p7fsbg5h2fuc3tsrgimbgnfkq.arweave.net/ldEiDRa7Y6i1ulQ4OZNhVbT_lkE3T6LQW5yiZDAmaVU) | #7 | Tuesday, August 01, 2023 09:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-chain/meetings/007-2023-08-01.md) |[Link](https://github.com/akash-network/community/blob/main/sig-chain/meetings/007-2023-08-01.md#transcript) |[Link](https://ublt6v3ytezl3kaq6ygiaz2zk52wxhmp7khokzmiy2ufgjheanpa.arweave.net/oFc_V3iZMr2oEPYMgGdZV3VrnY_6juVliMaoUyTkA14) | #8 | Tuesday, September 05, 2023 09:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-chain/meetings/008-2023-09-05.md) |[Link](https://github.com/akash-network/community/blob/main/sig-chain/meetings/008-2023-09-05.md#transcript) |[Link](https://r67rmtmtcv66e7edkvshs42dzkzhk46xpknlhrtrvzwkvdm464ja.arweave.net/j78WTZMVfeJ8g1VkeXNDyrJ1c9d6mrPGca5sqo2c9xI) -| #9 | Tuesday, October 10, 2023 09:00 AM PT (Pacific Time) | | | -| #10 | Tuesday, November 07, 2023 09:00 AM PT (Pacific Time) | | | -| #11| Tuesday, December 05, 2023 09:00 AM PT (Pacific Time) | | | +| #9 | Tuesday, October 10, 2023 09:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-chain/meetings/009-2023-10-10.md) |[Link](https://github.com/akash-network/community/blob/main/sig-chain/meetings/009-2023-10-10.md#transcript) |[Link](https://nyvxvysvdc5oz5zwbmxrvtkyh2n2rrsqkopr2gxgpd7gkptvvsyq.arweave.net/bit64lUYuuz3NgsvGs1YPpuoxlBTnx0a5nj-ZT51rLE) +| #10 | 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) |[Link](https://github.com/akash-network/community/blob/main/sig-chain/meetings/011-2023-12-05.md) |[Link](https://github.com/akash-network/community/blob/main/sig-chain/meetings/011-2023-12-05.md#transcript) |[Link](https://ak4u4umlhafhkfu5jjckivcgokrrwkzzitwtwpoy5axl6soc5paq.arweave.net/ArlOUYs4CnUWnUpEpFRGcqMbKzlE7Ts92Oguv0nC68E) +| #12| Tuesday, January 09, 2024 09:00 AM PT (Pacific Time) | | | +| #13| Tuesday, February 06, 2024 09:00 AM PT (Pacific Time) | | | +| #14| March, 2024 09:00 AM PT (Pacific Time) | | | +| #15| April, 2024 09:00 AM PT (Pacific Time) | | | +| #16| May, 2024 09:00 AM PT (Pacific Time) | | | +| #17| June, 2024 09:00 AM PT (Pacific Time) | | | +| #18| July, 2024 09:00 AM PT (Pacific Time) | | | +| #19| August, 2024 09:00 AM PT (Pacific Time) | | | +| #20| September, 2024 09:00 AM PT (Pacific Time) | | | +| #21| October 2024 09:00 AM PT (Pacific Time) | | | +| #22| November, 2024 09:00 AM PT (Pacific Time) | | | +| #23| December, 2024 09:00 AM PT (Pacific Time) | | | +| #24| January, 2025 09:00 AM PT (Pacific Time) | | | ## Leadership diff --git a/sig-chain/meetings/009-2023-10-10.md b/sig-chain/meetings/009-2023-10-10.md new file mode 100644 index 00000000..6a3d1393 --- /dev/null +++ b/sig-chain/meetings/009-2023-10-10.md @@ -0,0 +1,234 @@ + + + +# Akash Network - Chain Special Interest Group (SIG) - Meeting #9 + +## Agenda + +- Discuss upcoming network upgrades. +- Discussion on Github Discussion 309 +- Open discussion of chain related issues. + +## Meeting Details + +- Date: Tuesday, October 10th, 2023 +- Time: 09:00 AM PT (Pacific Time) +- [Recording](https://nyvxvysvdc5oz5zwbmxrvtkyh2n2rrsqkopr2gxgpd7gkptvvsyq.arweave.net/bit64lUYuuz3NgsvGs1YPpuoxlBTnx0a5nj-ZT51rLE) +- [Transcript](#transcript) + + +## Participants + +- Artur Troian +- Bao Pham +- Boz Menzalji +- George Pro +- Julius Haus +- Scott Carruthers +- Tyler Wright + + +## Notes + +- Artur mentioned that there was another successful upgrade. +- Validator commission was running in dry run mode. This was fixed. +- Authorization issue was found after upgrade related to the upgrade. +- Two upgrade are coming very soon. Artur and the core team want to have upgrades +- The first upgrade will be around bid attributes. The client may want to know what provider office hours. Bid message is perfect place to this information. +- This should be something similar to attributes currently on chain. +- The second upgrade is Packet forwarding. This feature needs to be tested extensively before it goes live. +- Boz asked if upgrades require central exchanges will need to upgrade or just validators? Artur clarified that both network upgrades will require provides +- Artur wants to call core network V1. It is time. The product has grown over the last 2 years. +- Tenants can deploy and pay with USDC on the network. More tokens are coming soon. + +Bao and his team talked about [discussion 309](https://github.com/orgs/akash-network/discussions/309). Artur gave the group feedback. + +- Artur mentioned that the naming of fee abstraction may be wrong. Fee abstraction is something different. +- ICQ is not ready to be used right now. We cannot rely on it right now. +- Cross currency swap is still something that is interesting. Really narrow use case. +- Still interested in Fee abstraction for gas fees. Right now all gas has to be in the AKT. +- Artur wants to close this conversation, and open up a new discussion. It would be great to talk about ICQ and provide some more details. +- Artur wants to talk more about cross currency swaps, especially for the Community Pool. +- Artur wants to know more about ICQ, who is working on it, and more details about code implementation. + + +### Action Items + +- Tyler and Artur is going to create issues for network upgrade. +- Bao and team to close current issue, and make a new issue with some more detail and a new title. + + +# **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 SEG chain monthly meeting number 9. During the blockchain or chain for Shorts, Special Interest Group the group here, mostly comprised that folks from the core team in members of the community talk about everything related to the Blockchain Cosmos SDK network upgrades on And so again, some of these pops tend to be a little bit more technical since our stick to 6, monthly meeting with sick chain, usually is the first week of every month. First Tuesday, the last meeting saw the network upgrade, to mainnet, six being complete, there was a couple of outstanding items that were talked about during the last thing chain monthly meeting. + +Tyler Wright: There's since been that network Fix some issues related to authorized spend cooling as well as the 5% validator commission minimum, which was again, part of mainnet sticks. those items have been tested. And again, the community seems to be Responding well to both those upgrades that have happened over the last month. So, again, shout out to Arthur Scott, I'm a members of the core team and again, thanks for those in the community that helped testing meeting up to Mainnet, Six. And then the network upgrade. That just happened a couple of weeks ago. + +Tyler Wright: So again, there's been a lot of progress over the last month on the network. The network upgrade made at six unlock GPUs as well as a host of other features on the network. And again this most recent network upgrade fixed some validator commission issues as well as Mason changes to all see + +Tyler Wright: I know that Archer who is leading efforts from The core product, has some more updates to give as a supreme to future network upgrades. But again we want to get the floor to artur a little bit to give us some upgrades. And then from there we can open up the questions from folks that are here today. Again there was somebody from the community that wanted to talk about a discussion that they put on Github discussion number 309 that I'll put in the chat around Akt fee of section. If a person is here we can talk about it here with members of the core team. If not again we'll just open up. If anybody has any questions or comments about anything Akash Blockchain related times when Decay etc. Without further ado, I'll pass it over to Artur to get it started with some updates from him in the engineering core. + +Artur Troian: Thanks Hello everyone So Yes that'll just mentioned. We had yet another successful upgrade and we can go so that fixed one issue that was Passed over from the point 24, upgrades are related to validators commission, it was just running right arm mode and even apply. We fix that, as well as. + +Artur Troian: Smoky cup that we discovered poster graduated to the querying of the positive deployment deposit of authorizations. So those deposit authorizations were not upgraded to the new API version and it was causing some issues on some clients. For example, some comments were just unable to query previous authorizations, pre-order. They might have a great six. so all those issues have been successfully cured and we are working right now on these two shortcoming upgrades + +Artur Troian: That I would like to share with the community. Number one is the first upgrade will be related to the extending bead message specification to allow providers put details on what actually they be. For example, deployment has wild card specification for the GPUs the client may want to actually know what provider offers for this particular deployment and the Beat message is the perfect place to pull that in. We're still working on the specification on how exactly it will be late out inside the bit create message, but it should be something similar to the existing attributes that we have on the chain. + +00:05:00 + +Artur Troian: The next one will be bucket forwarding. So we have much done implementation itself and extensive testing falls up. So we want to test this feature as much as we can before going live. See the best. That's kind of dramatic functionality that we would like to be working 100% and that brings us a lot of things. Including one, click Swap for let's say Agg Julius DC, for those who want to pay in USC for the deployments. As for right now, it has to be done through the multi-stage process. For example, switch to osmosis do the swap and then send tokens back over the IBC using pocket forwarding. It just gonna be pretty much single click. + +Artur Troian: that is it I would say for the shortcoming upgrade updates details about when those upgrades gonna happen, we will be sharing soon through Our communication channels, but I would say the next upgrade is coming in about three weeks. + +Artur Troian: That pretty much it from this subject, any questions? + +Artur Troian: Okay, do we want to chat about three or nine discussion or should we push it later? + +Tyler Wright: Go ahead boss. + +Boz Menzalji: The question Arthur for the upgrade Does this require not just validators but I'm centralized exchanges as well or no. + +Artur Troian: A year. So both upgrades I'm afraid and I require that simply because the API changes and all of the nodes will be in the same patches that + +Boz Menzalji: Okay. + +Tyler Wright: Great Archer, One question, I had and the natural Segway, There's a six, support call happening tomorrow. Stuff again, if anybody has any questions on what's happening related to some of the outstanding issues, relate to the core product, feel free to join that conversation Archer. Do we want to make specific issues for these network upgrades similar to where we did for v0.24.0 or because they're smaller we can just have conversations directly with the community and discord. + +Artur Troian: And I think it's gonna go to have issues anyways and actually yeah, thanks for bringing that up. There is a one thing that we are circulating inside is to actually call Not repo for V1. I think it's a good time for that. the network has matured over this two years. And It brings couple improvements to the process as For example, releasing and network upgrades. because in the goal and the V2 and upper versions are pretty much new distinct packages. It drastically simplifies Maintaining previous network upgrades within the code base. We just have to remove them as we have to do right now. + +Artur Troian: And it's gonna remove the confusion that we have is the naming of the network operates itself. so right now, we have this what 0.24.0 0.26.0, which is a little bit over overcomplicated and let's say we to be three before V5 V6 is going to be way more. + +Artur Troian: Easy to read and understand and I think we actually gonna maybe align it with the mainnet night names that we have right now. So yeah. Anyways, we're gonna do the thing and eat quite soon but yeah, let's have those issues as well. + +Tyler Wright: Excellent, thank you. Does anyone have any questions about anything Akash Blockchain related? + +Tyler Wright: We usually also create some time. I know that folks in their casha community are also potential validators or also involved in other communities and the cosmos ecosystem. I was wondering if anybody here is participated in any upgrades on any other chains? There might be anything of note, both positive or negative, that It might be worth sharing with again, Overclock Labs core team related to anything network upgraded related. + +00:10:00 + +Tyler Wright: Again, I know that there was potential for somebody to join the conversation related to Abstraction, which is discussion number 309, I believe Artur's already left the comment related to a discussion, Bao, do you want to speak? I see your hand rates. Go ahead. + +Bao Pham: hello, we are tailors as discussed to Tyler earlier that we are here to discuss our idea of a cast fee of attraction to improve user experience. + +Tyler Wright: Excellent. can you talk a little bit that high level? I know. Artur have some time to look at it over the weekend and it's given some feedback. But again, we just wanted you to be able to quickly at a high level present your idea. I know that you put a great discussion but it'd be great to hear it live for me right now at the highest level about what you're trying to solve and then we can give you some feedback and potential next steps. So the floor is yours. + +Bao Pham: Absolutely. No. I'm going to transfer the microphone too. so our idea is in spite by a discussion on Github about allowing Usdc payment. And in the discussion, you guys has mentioned a feature called. Cross currency payment. + +Bao Pham: and so we want to provide with a solution. For the implementation of that feature. + +Bao Pham: and what we want to do is logic similar to the fee abstraction module. So that + +Bao Pham: we can. Beat and leech in different currency. By leveraging, the osmosis tax by IBC Swap. + +Bao Pham: is any question? + +Tyler Wright: Were you all able to take a look? I know it's Archer responded Today. Artur, do you want to just chime in that high level on? Maybe some questions or comments? You have related to that discussion. + +Artur Troian: Yeah. Yeah, yeah. Hey Thanks for the submission. So first of all, Let's just probably start I can share my screen From the headline. I'm not sure than aktv abstraction is a good name for that. there is a thing called, the abstraction that allows users to pay. Non-native currency for the gas. And that's what we call the fear instruction and that's what it's called. Throughout other chains. in regards to + +Artur Troian: The description. So, it's kind of probably three key thing to do and I don't think + +Artur Troian: let me just scroll down to show you what I mean. I don't think it is gonna work the way that it's been described. So let me just on the high level try to Summarize why? So number one is + +Artur Troian: I don't think the allowing provider to select the currency the provider wants to pay, so we receive Is a good way to do that. + +Artur Troian: It works actually quite opposite. So, the tenant that wants to create deployment actually sets the currency it wants to pay it and I don't think there's a reason to do the swap for that and just frankly saying it's just gonna be over complicating, the process itself. Increasing the beat time deployment time and so forth. That's why we keep the settlement of the payment the way in the currency that is provided by loyment, those by tenant. And the second one is Yes. So actually using the non-native tokens for paying for work laws has already been done. + +00:15:00 + +Artur Troian: It's just only right now. We support usdc through osmosis, but we plan to expand the amount of tokens if there is a demand for them. So, Then, the inq setting the + +Artur Troian: Dynamically during the lease creation, the demand and exchange and exchange rates. I don't think that's gonna be any value for the tenant or for the provider. But it's just gonna increase first of all latency, as I mentioned earlier, as well as Let's say, put the both and + +Artur Troian: Provider, independency of the exchange rate happens on the Let's say osmosis and so in order to eliminate that the Stable payments that we introduce in minus 6 were actually exactly for that reason. and the last one, but probably not least that the ICQ So I'm not sure it's actually ready to be used widely. First of all, is still a draft and it's not been food under Cosmosis, decay team. So I don't think you can rely on this implementation, even on the specification as final one. + +Artur Troian: I would say from what I see in this description on the discussion, I don't think we can move forward with that. But I happy to answer any of your questions, if you + +Bao Pham: Yeah, so the reason we came up with the Document, is that we read from a discussion of you guys. That use The cross currency payment. + +Bao Pham: And so I want to ask if you guys have any plan to Work on that. + +Artur Troian: What is cross currency payment? + +Bao Pham: It's in. Can you screw up a bit? + +Artur Troian: Which one? Okay. + +Artur Troian: Yeah, I probably didn't have the one for 27, right? + +Bao Pham: Yes, in the Phase 3 Bells and Whistle. + +Artur Troian: Yeah, I mean so here's the thing right in regards to the Cross currency payments, Honestly saying I'm not sure there is a at least value for it as for right now, right? + +Artur Troian: first of all, + +Artur Troian: it's gonna be very too overcomplicated to implement it right now. It's gonna be very too many changes including all the things related to the provider as well as for the blockchain itself. That's Number two is what the value of that is. so, I would say it could be potentially Meaningful to have that. + +Artur Troian: Swab for the Community Pool Because you do the take rate, the usdc gets landed in the community pool and maybe it's actually makes sense to do that of ATT through the processmosis or other listeners changes. But doing that per release basis, I don't think it actually makes sense and pretty much it takes down the gear of using stable payments for deployments himself. Doesn't answer your question. + +Bao Pham: Yeah, thanks for the explanation. + +00:20:00 + +Tyler Wright: Perfect. + +Artur Troian: Yeah, sorry for the bad news. It's not that we trying to take it down as a whole is just to try to find what is going to be the best. And For all the participants of the chain. And once again, taking that down to the old details, imagine that having the swaps on every block, maybe or during this draw command and so forth. So it's gonna create a lot of pressure on the network. And as well, as once again, it's just eliminates the need For the stable payments, in terms of, I would highly suggest to rename that + +Artur Troian: Discussion anyways, because it's not the fee abstraction. It doesn't actually discuss the fee as the thing, but It's pretty much like cross currency payments for the workloads. we still interested in the actual fee abstraction that allows Participants to pay for gas fees, Not only in the Akt, especially for use cases. When let's say user deploys, workload and wants to pay in usdc right now payments, the gas has to be stupid and make it, which is a little bit. + +Artur Troian: I would say It doesn't create issues on the clients like Console or Cloud Mods, but it definitely creates issues for the CLI clients. And I think it's going to be the good way to have just using the single currency for both gas and the deployment. But once again, we have to have a separate discussion for that. And do a force assessment of it, but yeah, thank you so much for bringing it up. + +Bao Pham: Yeah, thank you. I think it makes sense to me. So yeah. + +Artur Troian: Yeah, just I would like to summarize that. So, the biggest takeaway of this conversation is so the cross currency Swope is There's still interest for that in terms of, for example, doing by back of the Akt for community funds. Right. But that's Sort of. + +Artur Troian: Need really narrow use case. I would like maybe this discussion to be closed and then drop a new one dedicated for the community swap. And let's think about that. As well as the ICQ, if you could bring in the new discussion things, like, where they seen ICUs is being used. Haven't been tested. What chains are using that? what is gonna be behavior of the client? If I bec goes down or whatever? So, there are lots of engineering challenges with this approach, and we would like, to have to have answers to all those questions before moving on. But I would love to have this discussion related to the + +Artur Troian: Chris currencies swaps, especially for the community pool. + +Bao Pham: Yeah, for the ICQ questions, I think. We can do ICQ to osmosis because a person wasn't contract. For that IQ. And so we just need established a RBC channel to the contract. Then we Basically. + +Artur Troian: Wait, why sort of interruption do we need to use? + +Bao Pham: Then. + +Artur Troian: A cosmos on the osmosis side for interchange queries. + +Bao Pham: Hey, I just made a mistake. At the osmosis chain has a async ICQ module. Running on the chain already. So of yeah. + +00:25:00 + +Artur Troian: I see, yeah, anyways, let's see. I would love to be the AC investigue As a part of Cosmos K. Team. So there is that means they're going to be dedicated maintainers for that. That's number one. Number two I mean I'm sure this question, not for you but actually for nothing the strange law who proposed that And the second question Is we still on IBC before and moving is the higher version of the IBC is going to be probably difficult for us in the next couple months. And my biggest worry on that is how + +Artur Troian: V4 is being maintained for this particular interchange queries. So that's the couple major questions for me. If you could somehow late out and see what because from what I've seen of the IQ implementation, it's not been updated for quite a while, I think. So, my biggest worry is what's the plans for the future plans, for this? Pretty cool thing. + +Tyler Wright: Thank you Artur. does that make sense upon about next steps? So I didn't mean to cut you off. + +Bao Pham: And we do not know detail about the async IQ. Plan for supporting your V for ivcv4. So, I have to look at. The code to answer question. + +Tyler Wright: No, I think that's all right. I think we're looking for an answer today. I think its The next action items. We can close the current discussion discussion. I think 309 was the advice from Artur and then open up a new discussion, where maybe you have some time to look at some of this information related to the ICQ IBC And then again, renaming it Cross currency swap as opposed to the abstraction. + +Bao Pham: Yeah. that works. For me. + +Tyler Wright: Okay, excellent. + +Tyler Wright: About a few or your team methany questions, you can feel free to reach out to me on discord or feel free to throw a message and stick chain. and then when you have a new discussion up, we can just throw that in Sig chain as well and send to me, and I can make sure it gets circulated. We can continue this conversation. + +Bao Pham: Yeah, sure if I have anything to add, then I'll message you on discord. + +Tyler Wright: Excellent. Again, that and the team. Thank you very much for that discussion. Artur, thank you for again, giving you some time, reading it over, and giving some feedback. Does anybody else here have anything they want to talk about or any discussion points related to the cost, blockchain network, upgrades or beyond? + +Tyler Wright: again, look out for hopefully further discussion from Bao and his team over next week or so. And again there will be some issues that will be created for some of the network upgrades that Artur has outlined at the top of this call. And again there's plans to be a number of network upgrades over the next couple of months. So please continue to join this monthly meeting as well as stay involved in sick chain. I know that meant we're gonna get many of the validators involved when they can. But again there's a lot going on with the core product so please look out for a number of changes happening soon. That'll involve again community support But I much appreciate the core team for taking some time and members of the community for listening in and participating. + +Tyler Wright: If anybody has any questions, comments, concerns again, feel free to reach out to me or drop a message in the SIG Chain discord channel. But I hope everybody has a great rest of the day and will continue working online. + +00:30:00 + +Tyler Wright: Thanks again, everybody talk soon. + +Artur Troian: Thanks everyone. + +Meeting ended after 00:30:35 👋 + diff --git a/sig-chain/meetings/010-2023-11-08.md b/sig-chain/meetings/010-2023-11-08.md new file mode 100644 index 00000000..80d67479 --- /dev/null +++ b/sig-chain/meetings/010-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-chain/meetings/011-2023-12-05.md b/sig-chain/meetings/011-2023-12-05.md new file mode 100644 index 00000000..57b13d1d --- /dev/null +++ b/sig-chain/meetings/011-2023-12-05.md @@ -0,0 +1,132 @@ +# Akash Network - Chain Special Interest Group (SIG) - Meeting #11 + +## Agenda + +- Discuss upcoming network upgrades. +- Discussion on Github Discussion 309 +- Open discussion of chain related issues. + +## Meeting Details + +- Date: Tuesday, December 5th, 2023 +- Time: 09:00 AM PT (Pacific Time) +- [Recording](https://ak4u4umlhafhkfu5jjckivcgokrrwkzzitwtwpoy5axl6soc5paq.arweave.net/ArlOUYs4CnUWnUpEpFRGcqMbKzlE7Ts92Oguv0nC68E) +- [Transcript](#transcript) + + +## Participants + +- Artur Troian +- Damir Simpovic +- George Pro +- Julius Haus +- Mariela Tanchez +- Scott Carruthers +- Tyler Wright + + +## Notes + +- Last sig-chain meeting for this year. Artur gave a recap of the year. +- All of the upgrades were successful. Only 1 small hiccup that was not upgraded related but consensus related for an emergency upgrade +- Right now the downtime during the upgrade is less than two minutes. Huge "Thank you" to everyone. +- There are quite a few network upgrades planned for next year. 3 upgrades planned for the first quarter. Please look in the support repo for more details. +- Small upgrades work better with all the features in the Akash Roadmap. +- First upgrade in the works right now is related to governance proposal periods. Right now you have wait 7 days. Artur is looking into expedited proposals. This has been implemented by Osmosis. Any type of proposal can be expedited, if 67 percent of voting power is made available if first 24 hours. +- There will be an upgrade that will include messaging for errors in lease. +- Packet forwarding is on the roadmap. This needs quite extensive testing. This will most likely be upgrade 3 for Q1 2024. All times are subject to change. + +## Testing + +- Scott and Artur are sweeping and auditing all end to end testing for network upgrades. All of the test sdls will be refactored. +- Anyone will be able to test. +- SDL will be moved away from node repo, and into AkashAPI. +- Testing have been steadily improving over the last year. This will continued to be improved. +- Test procedures will be in a separate repo. Will most likely use Docker compose. More to come here. + +## Questions + +- ZJ asked about Liquid staking. Is this on the Roadmap? +- Artur mentioned that this is part of the roadmap. More accurate timeline for implementation will be determined in the future. +- Tyler urged anyone interested in Liquid Staking to start a discussion that highlights the demand this could bring to Akash Network, so priorities can be adjusted if needed. + + + +### Action Items + +- Core team to move SDL out of Akash node repo. +- Auditing and improvements to end to end testing will continue. Work will be shared with community when ready. + + +# **Transcript** + +_This editable transcript was computer generated and might contain errors. People can also change the text after it was created._ + +Tyler Wright: All right, welcome everybody to Sig chain monthly meeting number 11 during these special interest group meetings for the blockchain. We discussed everything from Network upgrades to everything around Cosmos SDK and just again everything related to a cash blockchain. Please let me know if you have any questions and you can drop those in chat and we can cover those after we go through the Out of the last meeting. We were getting ready for binary upgrades that went into maintenance eight. + +Tyler Wright: Since then we've had a successful upgrade to mainnet H. There was an issue that was found and made that eight that was verified fixed tested again, and then we were able to go to me next nine. I believe last Tuesday. So again, thank you all to all the validators and folks that were able to upgrade. There was a provider upgrade. It's a part of the main Aid upgrade but not the part of the main nine upgrade. But again, thank you to all the participated in those last year upgrades that have happened back to back over the last month or so or really within the last month. + +Tyler Wright: Other than that Artur is there anything specific that she wanted to talk about again? I know that Scott's has been working on end testing and you can see this in the GitHub projects. I'll throw that in the chat. So people couldn't look at that as well. But I know there's been also some preliminary discussion around automation for some of the upgrade procedures because I know that again as Archer mentioned we are number of meetings ago. The idea is to have more consistent upgrades because a big upgrade to have five or six features in them are just really hard to test and creates a very mulchuous upgrade process. For Artur, is there anything specific that you want to cover or anything that anybody else on this call wants to cover during this agenda today? + +Artur Troian: Thanks everyone. See you all month. I'm joking. so + +Artur Troian: yeah related The Pain part, I think there's gonna be the last sick change for this year. So I'm probably would like to give some wrap on things that we have. done during this year. So we had quite actually numerous moment of networking braids. as the upgrades itself, they all were successful. We had only one hiccup. It wasn't actually upgraded. It was not even binary place. which I wanna cover letter today as well, but in terms of great itself, I think we have established quite a high ground on the quality of rates and + +Artur Troian: Is pretty much every time we do that we tried to keep it as small as possible as well as a script as possible. So right now the downtime during the upgrade is less than humans. and I'd like to just thank you everyone for being staying results every time and helping us to keep Network alive. moving on so we have scheduled quite a few upgrades next year. And we about that. You're going to cover it in the support trip or quite so on. Hopefully sometime next week that we will describe what might upgrades we are planning to do. It's not all some of them show up. + +Artur Troian: sometimes but quite quickly, but at least for the first quarter, they're gonna be three that's what we Play at this stage, but once again, it can be few more. idea is that we want to keep this Cadence of providing small upgrades as well as + +Artur Troian: still providing necessary and required by Community features. So the very first one. We Having in works right now. Related to the governance. So right now what happens is let's say we need to do Network upgrade and for whatever reason if something has been missed and it needs to be fixed quite quickly. There is no. Best way other than create yet another Network upgrade proposal and just wait for seven days. I think sometimes cost of that is a very too high. Of what we will do is we'll introduce what's called expedited updates So actually expedited governance proposals we found this feature. + +00:05:00 + +Artur Troian: has been actually implemented in integrated biosmosis and it's been now reported to Cosmos SDK for seven hire so what we will do is we will backward you actually give you a portion to our Fork of customers decay. that thing will allow us to have Any type of proposal to be expedited? And if you think 24 hours we gain for now we think is going to be 67% of what in power. More yes them great will be pretty much or any type of proposal parameters change will be executed the same 24 hours. I think this is going to be really + +Artur Troian: cool high quality improvement for entire network so we will be thinking about what deposit amounts Necessary for the expedite but proposals is probably gonna be quite higher than for normal proposal. But once again, we will put all this information in the GitHub. support people and you all will be welcome to put your thoughts so that's probably the biggest one another thing. We are having on our Map right now is improvements to the marketplace. + +Artur Troian: So right now when the lease is being closed by provider, there is no actually clear reason why it can be and there can be a few things like our own escrow count lease is not responsive and so on so forth, so we will be doing that Improvement to include photos. Of the closure into the lease. It's gonna improve visibility for everyone including the money actually talents. and then The pocket forwarding is on our roadmap. We were with salt you're gonna issue this year. However, we still trying to the thing is quite extensive testing. We are in the middle of the process of revising our test procedures which you want to talk today as well. + +Artur Troian: So the pocket forward you'll most probably will be a great number three sometime by the end of q1. But yeah, all those Target dates are subjects to change if anything goes, really gets quicker or things slow down those first now to the testing so historically we had our test files test scenarios, they slightly scattered around the multiple repositors. And we came at the point and it becomes really hard to keep an eye on them and things can be missed. So what Scott and I are doing right now we are. pretty much sweeping entire + +Artur Troian: set of repositors related to the blockchain and the provider. Collecting all of the hdls all the test scenarios and Scott created tremendous documentation struggling what kind of test and education we have in the stage. the target is to include to do test coverage on blockchain and end newly to 100% so we will be Combining all of the other factor in all of the test sdls and moving them into a cash repo they're going to be dedicated directory for that main goal of this move is first of all. Anyone who uses a suppress API can use this sdl as a test making sure that everything works fine. + +00:10:00 + +Artur Troian: The second thing is the sdl parser and specification itself will be part of Akash API. that let's say any client like a card jazz or whatever language is being decided to be used for a car. Can easily take those sdls and validate against them? So we're gonna think about this triangle for that. Yes, I mentioned the HDL will be moved away from not repo and it's gonna be part of a cash API. It technically does the specification. We will be working on the maybe hdrb3. But what's not there It's probably quite conversation. regarding the test framework so I think you've done quite a good job on. + +Artur Troian: testing environment for Network grades The View be gonna keep using this approach with some improvements first of all you're gonna have All of those things to spin up test networks based on the mainnet snapshots. + +Artur Troian: all those test procedures probably located in several triple. So anyone if needed that into one, that's not just try some things. It's gonna be quite easy to do most probably is going to be done through Docker compose simply because it's really easy to manage and I think all of the test Nets ingredients and sandbox will be done using that framework, but anyway more things to come on that part as well. and I think that covers any questions + +Tyler Wright: Thank you her. I know they'll be continued a conversation and discussion whether it be in other cigs and steering committee or again in GitHub discussions around specific topics. So if anybody wants to get involved or wants to learn more about the testing process, please just reach out to me and we can get you involved. + +Tyler Wright: Does anyone have any other? Things related to the cost blockchain that they want to discuss right now or a network upgrades specific. + +Tyler Wright: If not, then has anybody been a validator on any other Cosmos chain and has seen anything interesting or out of the normal recently that they want to bring up here with this group? + +Tyler Wright: Archer do you have an answer there? + +Artur Troian: So that is I believe interchange accounts that needs to have Network upgrade. I believe of somebody from block pain was working on that but I honestly don't know what the stage there are. So anyways, yeah, the internship accounts. We have them on the roadmap. we'll see how important it is and how Thing is gonna be after New Year. So you're gonna try to do it next year. I just don't have the ETI on that subject, unfortunately. let's get back to it once a chain of the new year. + +Tyler Wright: To Julius. Is there anything specific that you thought from a demand perspective that it should be higher or priority or Mariela again? If you do think again, one of the things that their customers always focus on is driving demand. So when decisions are being made about the importance of priority of future editions Network upgrades Etc. Obviously operations is important, but being able to drive demand is something that is always a factor in how things are prioritize. So if you think that there's something to increasing Demand on the network, it would be great to have a discussion or again. we could talk about it in more detail than this next sick change meeting or really at the Sig economics meeting happening tomorrow. + +00:15:00 + +Tyler Wright: Does anyone else have any questions about anything testing related sandbox or just like hash blockchain? + +Tyler Wright: if not as an Archer mentioned this it will be the last sick chain monthly meeting for the year much appreciate the participation month over month for these meetings. Again, we've talked about a number of network upgrades have consistently improved testing from upgrade to upgrade gotten more validators involved. And again continue to have our polls on what's going on with confidence SDK and what's going on in just the cosmos ecosystem so much. Appreciate everyone. It's participating. bearing thoughts concerns questions and Beyond + +Tyler Wright: if there's nothing else then again steering committee will be happening Thursday. A big support will be happening tomorrow. I know that there's some new discussions that have gone up around feature requests, there's some support issues in the support repo again, if anybody has any questions about past Network upgrades or if anybody wants to track future network upgrades, please look in the support repo. That's where all the network upgrade information lives of as well as all Open tickets related to the core product. And we'll have a six support meeting there tomorrow. We'll talk about anything relate to Open tickets and triage any issues that haven't been Trio soon. + +Tyler Wright: that's all for today. Thank you very much for participation reach out to me if you need anything, and we'll continue to power through the rest of the year and we'll see you all 2024. + +Scott Carruthers: Thanks. + +Tyler Wright: Thank you. right + +Artur Troian: Thank you. + +Scott Carruthers: Okay. + +Meeting ended after 00:17:11 👋 + diff --git a/sig-chain/meetings/012-2024-01-09.md b/sig-chain/meetings/012-2024-01-09.md new file mode 100644 index 00000000..546d0272 --- /dev/null +++ b/sig-chain/meetings/012-2024-01-09.md @@ -0,0 +1,88 @@ +# Akash Network - Chain Special Interest Group (SIG) - Meeting #12 + +## Agenda + +- Discussion of network upgrade plans for q1 2024 +- Proposals on chain for vote. +- Open discussion + +## Meeting Details + +- Date: Tuesday, January 09, 2024 +- Time: 09:00 AM PT (Pacific Time) +- [Recording](https://p2eg6ctrzmvcgqmibhpnvtje32gi3rt3nzdyjocfohwt6kiddsma.arweave.net/fohvCnHLKiNBiAne2s0k3oyNxntuR4S4RXHtPykDHJg) +- [Transcript](#transcript) + + +## Participants + +- Artur Troian +- Rodrigo Rochin +- Scott Carruthers +- Tyler Wright +- Zach Ross + + +## Notes + +- First sig-chain of 2024. Happy new year. +- There are some [proposals on chain](https://www.mintscan.io/akash/proposals) for vote. Please vote if you can. +- First network upgrade will be for changing governance proposal structure. Osmosis already has a version of this implemented. No Testnet is needed for this. This will be tested by the core team, and a newtwork upgrade will happen. +- Proposal 2 will be related to Akash marketplace. Right now it is hard to know why a lease has been closed. +- Network Upgrade 3 will be around packet forwarding. Code base is done. Feature just needs to be tested extensively. + +### Action Items + +- Create written plan for Q1 2024 Akash Network Upgrades to be shared with community. + + +# **Transcript** + +_This editable transcript was computer generated and might contain errors. People can also change the text after it was created._ + +Tyler Wright: All right, welcome everybody to the special interest group for their cost blockchain. This is the first meeting of 2024. Happy New Year therapy buddy during the Sig chain monthly meeting the group goes over everything from the cost blockchain Cosmos SDK Network upgrades out of the last meeting. There was some major discussion around what was happening q1 and 2024 which again we're starting right now. I know that Artur will talk a little bit about some plans for the quarter as of right now. Again, we talked about this last month. There's three plans Network upgrades and then art again Archer will talk about those at a high level here shortly. + +Tyler Wright: Also want to call out that there are some proposals that are up on chain, for folks that are validators and this is a meeting where we encourage validators to join if they have any questions comments concerns about the upgrade process or anything else. Again want to remind folks as validators that it's a particular responsibility to vote. There are a couple of live proposals on chain for boat right now and then a number of items that have recently passed since our last meeting including a couple of signaling proposals and a couple of parameter changes proposals. So again, appreciate all those who have voted and if you haven't voted Please vote I try to do. + +Tyler Wright: It's gonna job as possible of sharing active votes in Discord. And then again, I also have a mailing list for validators if anybody that's listening to his call later wants to be added to that validator mailing list. So they get email correspondence keeping them up to date on all boats Network upgrades Etc. Please feel free to reach out to me privately and Discord. I'll make sure you can add to that list. Cool, both out further Ado. I'll hand it over to Artur to just talk a little bit of high level about to take chain and what we got looked for in the quarter and the year. + +Artur Troian: Thanks, Hello, everyone. Happy New Year, and welcome to 2024. All right. So the beginning of the year will be quite busy or Akash network from destructive of chain changes. We haven't had chance yet to put public list of what's Coming we will definitely Over the next chain. I'll try to give verbal overview. And have to answer any questions. so the key one we have when the least I think three Network grades. + +Artur Troian: Number one will be the change of governance module that will allow us to have different working periods for different proposal types. As well as expedited proposals. So we especially excited about expedited proposals reason sometimes Network upgrades may be little bit finicky. Sometimes there are things maybe missed or some box revealed that needs to be fixed quite quickly. So there are two ways to do that number one is we could do something like upgraded certain height. + +Artur Troian: And you tried it last time it didn't work. validators are not quite responsible sometimes and just making maybe unnecessary steps and then waiting for the consultances was right there and took us what an hours. So instead of doing this way, all of the future changes to the blockchain state will be done only through the network upgrades and emergency upgrades you get down through the expedited upgrade proposals. The idea is so it's not new idea. We decide on a process. So we pretty much to get an extended to our needs. And pretty much when the network upgrade is being grateful and chained. They're gonna be an option to Market as So validators gonna vote and if you think 24 hours we get 67% + +Artur Troian: of voting power the great passes and it's gonna be executed right after the break boss. so that's the number one. We have a code-based on and we're gonna start testing it next week. So you will not make any testnets you'll just test these internally and as soon as the testing concluded concludes, we will issue a great proposal number two will be related to Marketplace. So right now it's kind of hard for tenants to see. + +00:05:00 + +Artur Troian: Why lease is being closed? There are many reasons why it can be closed can be overdrawn. It can be responsive. So provider just kills it because house check no passion and so forth. we want to extend the marketplace especially these part that will indicate why it's been closed so they're gonna be clear reason. So whenever provider closely is or this is being caused by the network. Let's say it's overdrawed. The least status will indicate Reason why it has happened. That's number two. and number three is a pocket forwarding. I know we've been talking about that a lot last year. + +Artur Troian: it's really good to have and it wasn't high priority. So we've been pushing back, but we still want to try to squeeze it into the q1 so As soon as we performed first Network operates, we're gonna start testing pocket forwarding. Once again, we have gone by is done. You just needs testing. So the biggest outcome of this feature is That coins. As well as some nice things like liquid staking is from stride and so forth. So that probably summarizes it for the q1. And the chain changes the cosmos SDK version will be remaining on 45.16 for the key one. + +Artur Troian: And later this year. with you upgrade to more recent one, but we don't have The path when and what version it will be so you will reveal all the details about that. Later this year. I think that summarizes any questions + +Artur Troian: Thank you so much salary, but + +Tyler Wright: Thank you Again, certainly by next sick chain meeting. There will be more information. I'll be shared with validators and other members of the community related to these Network upgrades some more written information and then again a path forward and some timing will be made available for all those that are participating in this network upgrades. If anybody has any questions or comments between meetings, feel free to let any of us know on the core team. I know one thing that Artur and + +Tyler Wright: Scott did a great job of trying to optimize was the ease of process for validators that are upgrading during this network upgrade process. So again, it's been going quite smoothly and quite quickly for the last few Network upgrades outside of the one that had to be done more manually. So again, please continue to look at the documentation when it's made available and follow those steps explicitly for a smooth and clean upgrade. I know that again Scott and Artur always working on the tooling to make sure that validators have an easy go of it when it's time to make sure to look out for that documentation. + +Tyler Wright: as we move forward, they'll be continued conversations around specific items related to network upgrades. And I know that some validators have some more questions or just want to connect around specific types and items in the roadmap. So we'll continue to have these on a monthly basis for folks to again ask questions of the core team connect on all things that we're upgrade blockchain. Council Sasuke and Beyond but again much appreciate our trip relating this one. We know it's going to be fairly Short Happy New Year again to everybody and again, what can we'll talk in the validators channel the sick chain Discord Channel between meetings and I make the recording available soon, but look out for updates in terms of network upgrades, which should be available very shortly. + +00:10:00 + +Tyler Wright: Much appreciate everyone's time. I hope everyone has a great rest of their day. Happy Tuesday, everybody. + +Rodrigo Rochin: Thank you. Happy New Year guys. + +Tyler Wright: Yes, Happy New Year. Bye. + +Zach Ross: A new year. Cheers guys + +Rodrigo Rochin: cheers + +Scott Carruthers: Guys are good. + +Meeting ended after 00:10:32 👋 + diff --git a/sig-clients/README.md b/sig-clients/README.md index 921447c9..9af38e0f 100644 --- a/sig-clients/README.md +++ b/sig-clients/README.md @@ -41,12 +41,22 @@ The goal of this SIG is to foster a community around each of these clients that | #6 | Wednesday, June 21, 2023 10:30 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-clients/meetings/006-2023-06-21.md) | [Link](https://github.com/akash-network/community/blob/main/sig-clients/meetings/006-2023-06-21.md#transcript) | [Link](https://7wma24vbcylbmj2q74v24kte6sy7ysjarnbbgozg7p4yh5gnkiaa.arweave.net/_ZgNcqEWFhYnUP8rripk9LH8SSCLQhM7Jvv5g_TNUgA) | #7 | Wednesday, July 19, 2023 10:30 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-clients/meetings/007-2023-07-19.md) |[Link](https://github.com/akash-network/community/blob/main/sig-clients/meetings/007-2023-07-19.md#transcript) |[Link](https://cd6v6hartdyqkeqjzqpcdpxcum2dq6lcytnyrtzvgk7joid44xfq.arweave.net/EP1fHBGY8QUSCcweIb7iozQ4eWLE24jPNTK-lyB85cs) | #8 | Wednesday, August 16, 2023 10:30 AM PT (Pacific Time) |Coming Soon |Coming Soon |[Link](https://56oikxuxws6ewboifrwsgwvq2da4gzrg23sx7u5bldufgusgpc5q.arweave.net/75yFXpe0vEsFyCxtI1qw0MHDZibW5X_ToVjoU1JGeLs) -| #9 | Wednesday, September 20, 2023 10:30 AM PT (Pacific Time) | | | -| #10 | Wednesday, October 18, 2023 10:30 AM PT (Pacific Time) | | | -| #11 | Wednesday, November 15, 2023 10:30 AM PT (Pacific Time) | | | -| #12 | Wednesday, December 20, 2023 10:30 AM PT (Pacific Time) | | | -| #13 | Wednesday, January 17, 2024 10:30 AM PT (Pacific Time) | | | -| #14 | Wednesday, February 21, 2024 10:30 AM PT (Pacific Time) | | | +| #9 | Wednesday, September 20, 2023 10:30 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-clients/meetings/009-2023-09-20.md) | [Link](https://github.com/akash-network/community/blob/main/sig-clients/meetings/009-2023-09-20.md#transcript) |[Link](https://hy3zv6e5mxhxnese25p5cupfitg236o6aeivmow6fxfvpnqmjr3q.arweave.net/Pjea-J1lz3aSRNdf0VHlRM2t-d4BEVY63i3LV7YMTHc) +| #10 | Wednesday, October 18, 2023 10:30 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-clients/meetings/010-2023-10-18.md) | [Link](https://github.com/akash-network/community/blob/main/sig-clients/meetings/010-2023-10-18.md#transcript) |[Link](https://yofgxnfxaqk4jruuwko7pyrfckw27dtg5thp6c6bv2sfvfq66jla.arweave.net/w4prtLcEFcTGlLKd9-IlEq2vjmbszv8Lwa6kWpYe8lY) +| #11 | Monday, December 18th, 2023 08:30 AM PT (Pacific Time) | | | +| #12 | Wednesday, January 17, 2024 10:30 AM PT (Pacific Time) | | | +| #13 | Wednesday, February 21, 2024 10:30 AM PT (Pacific Time) | | | +| #14| March, 2024 10:30 AM PT (Pacific Time) | | | +| #15| April, 2024 10:30 AM PT (Pacific Time) | | | +| #16| May, 2024 10:30 AM PT (Pacific Time) | | | +| #17| June, 2024 10:30 AM PT (Pacific Time) | | | +| #18| July, 2024 10:30 AM PT (Pacific Time) | | | +| #19| August, 2024 10:30 AM PT (Pacific Time) | | | +| #20| September, 2024 10:30 AM PT (Pacific Time) | | | +| #21| October 2024 10:30 AM PT (Pacific Time) | | | +| #22| November, 2024 10:30 AM PT (Pacific Time) | | | +| #23| December, 2024 10:30 AM PT (Pacific Time) | | | +| #24| January, 2025 10:30 AM PT (Pacific Time) | | | ## Leadership diff --git a/sig-clients/meetings/008-2023-08-16.md b/sig-clients/meetings/008-2023-08-16.md new file mode 100644 index 00000000..af210067 --- /dev/null +++ b/sig-clients/meetings/008-2023-08-16.md @@ -0,0 +1,560 @@ +# Akash Network - Clients Special Interest Group (SIG) - Meeting #8 + +## Agenda +- Updates on Cloudmos and Console +- Demo Presentation from Source Network +- Discussions on Clients Libraries + +## Meeting Details +- Date: Thursday, August 16, 2023 +- Time: 9:00 AM PT (Pacific Time) +- [Recording](https://56oikxuxws6ewboifrwsgwvq2da4gzrg23sx7u5bldufgusgpc5q.arweave.net/75yFXpe0vEsFyCxtI1qw0MHDZibW5X_ToVjoU1JGeLs) +- [Transcript](#Transcript) + +## Participants +- Addo Smajic +- Andrew Gnatyuk +- Anil Murty +- Anish Maddipoti +- Boz Menzalji +- Calvin Harris +- Carlos A +- Christopher Berry +- Damir Simpovic +- Denis Lelic +- Emmanuel Arthur +- envy | Neta DAO +- Fred Carle +- Greg Osuri +- Ishan Dhanani +- Joao Luna +- John-Alan Simmons +- Joseph Tary +- Julius Haus +- Keenan Nemetz +- Mark Ntim +- Max +- Maxime Cyr +- Rodrigo Rochin +- Shahzad Lone +- Thomas Montfort +- Tyler Wright +- Tzu-Jung Lee + + +# Meeting Notes + + +### Updates on Cloudmos + +#### Max's Update: +- Max expresses gratitude for support on [ the proposal](https://www.mintscan.io/akash/proposals/216), noting high participation. +- Ongoing work on the CloudMos Interface and Tools, now open source. +- Integration of AkashJS library for SDL parsing and manifest creation. +- Anyone can use the indexer acquired by the community with documentation in the repository. +- Announcement of an upcoming release: the AuthZ manager for managing authorizations. +- Mention of plans to implement authorizations that can pay for deployments fees, inspired by Omniflix platform. +- The plan is to provide free trials for users without tokens. +- Mentioned that they have "no public roadmap," but they work closely with Anil on things to improve and build. + +#### Tyler Wright +- CloudMos and Console teams supporting a sandbox environment for testing network changes. +- Two bugs identified and resolved through testing. +- Community involvement in testing to ensure client functionality on mainnet. + +#### Anil Murty +- Anil addresses a question from Julius and discusses synergies between the two teams(Cloudmos team and Console team). +- Emphasizes that Cloudmos is now open source on Akash Network. +- Highlights the product strategy aimed at leveraging synergies between the two teams and finding common features. +- Discusses the importance of finding common features between both platforms and reusing code where possible. +- Details the plan to identify common features and integrate them into AkashJS. +- Mentions that all the document he is presenting will be available in the Sig-Clients within the Akash Network's community repository. +- Discusses plans to clean up the roadmap and make it accessible, mentioning the Cloudmos deploy folder as a potential location for it. +- Highlights recent developments by the Cloudmos team, specifically UI for viewing and setting attributes for providers. +- Explains that providers connected to the wallet can now see and modify attributes they've set. +- Highlights that clients can view the attributes they're assigned. +- Clarifies that the intention is not to become a provider management platform but to test the [proposed schema](https://github.com/akash-network/cloudmos/blob/main/config/provider-attributes.md) for compatibility with providers before wider implementation. +- Highlights that attributes implemented by the Cloudmos team to help clients query and filter providers based on specific criteria, improved the client experience. +- Highlights that attributes implemented by the Cloudmos team addresses an issue with the SSH shell interface in Cloudmos, which previously experienced frequent timeouts. + +### Updates on Console + +#### Anil Murty +- Anil Murty mentions that some bugs were reported in the Cloudmos channel on Discord during the Testnet phase. Fixes were made, including addressing an issue related to persistent storage. +- Anil Murty introduces a new landing page for Console 2.0 but clarifies that it's an interim solution until the new experience is determined. +- Anil Murty provides information about the Agora Labs team who are starting a project to build upon Console. +- Discusses their aim to create a user-friendly experience for AI developers. +- Mentions the team's plan to work on a prototype for an upcoming hackathon. +### Discussions on Client Libraries +- Joao Luna: Provides an update on the client libraries. The Java library is open source, while the GO library is still closed source and under discussion. +- Greg Osuri: Expresses the need for a GO library for his client project and is open to either building it himself or receiving access to one. +- Joao Luna: Agrees to discuss the GO library further within the working group for clients. +- Greg Osuri: Discusses the funding aspect and suggests putting out a usable version of the library first. He mentions that he will work on it regardless of funding but would need funding for further development. +- Joao Luna: Shares insights into their approach in building the library and their need for a clients library to interact with the Akash network. +### Demo Presentation from Source Network +- Tyler Wright: Introduces the [Source.Network](https://source.network/) team and gives them the opportunity to demo their decentralized solution. +- Addo Smajic briefly explains the nature of their decentralized database solution. +- John-Alan begins the demo of their database solution, [DeferDB](https://github.com/sourcenetwork/defradb). Launches an instance with an in-memory store, explaining the use of schemas and Graphql for interacting with the database. +- Greg asked for a reminder about what a CID is. +- John-Alan explained that CID comes from the IPLD data model, which powers IPFS and Filecoin, and it stands for "content identifier." +- John-Alan mentioned the importance of the Merkel CRDT system for building decentralized databases. +- John-Alan mentioned the need for developers to spin up nodes on Akash to act as replication endpoints for users going through applications. +- Greg expressed enthusiasm for the Source project and its alignment with Akash's vision. +- Discussed the idea of having managed services, like databases, that can be scheduled with containers. +- Greg inquired about the consistency model supported. +- John-Alan explained that it falls under the "strong eventually consistent model," where all clients see the same state as long as they are on the same version. +- Greg Osuri inquired about the number of verifications required for eventual consistency, but the exact number wasn't provided. +- Greg asked about ORM (Object-Relational Mapping) support. +- John-Alan mentioned that GraphQL provides a native ORM-like system. +- John-Alan highlighted Akash's ability to allow users to spin up VMs easily with a private key, reducing the complexity of server management. +- A question was raised about how authentication to the database works. +- John-Alan explained that they have a Global Authorization service within their Cosmos APP Chain. + +### Other matters Discussed +- Thomas Montfort provides a high-level overview of their projec and background as AI/ML engineers. +- Highlights their interest in Akash due to the GPU testnet and the support for GPU resources. +- Expresses the challenges in deploying and fine-tuning models due to resource availability. +- Outlines their immediate plan for the HACKATHON: creating an interface for fine-tuning models and automating deployment. +- Mention of handling model checkpointing and dealing with providers. + +#### Model checkpointing +- Anil Murty: Discusses the topic of checkpoints and shares that they are in talks with another team working on Lower Training, a technique that involves training large AI models on a smaller subset of parameters. They are exploring the possibility of enabling this training on Akash once the mainnet is launched. +- Anil Murty: Highlights that the training aspect of AI models can be exorbitantly expensive, and the Lower Training solution could be a cost-effective alternative. +- Anil mentions that he is working with the team on a proposal that will be published on GitHub discussions in the next few days. + +## Action Items +- Cloudmos team to release new features and additional functionalities. +- Anil Murty to publish a high-level roadmap for Cloudmos and Console on GitHub. +- Anil to share presentation documnent in sig-client repository +- Luna to continue discusions with Greg on Go library development in sig-client discord channel +- Tyler Wright to check if the Source Network team has plans for future sessions. +- John-Alan Simmons to prepare a demo for a larger audience. + +# **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 sync clients monthly meeting number eight. + +Tyler Wright: At these special interest groups for clients, it's an open discussion with folks that are running clients on the Akash network, you can look at the Readme where you can see a number of those clients in there that again, usually end. Some of these meetings, we have a fairly full agenda as mentioned today. I know there's been a lot of added the last dig clients meeting there was some talk about some collaboration going on between cloud most and console. Obviously, over the last month, there's been a lot of progress made there including again proposal that just passed yesterday for community funding for the cloud most acquisition. So again, shout out to all that helped out there. We want to get some updates from a number of folks that are running clients and then following those updates from Team Tech Cloud, Most Console, and others, that might be present. I see Luna's present that does, again clients + +Tyler Wright: there will be a presentation from Source Network. We'll be giving a demo and some of the work that they've been doing and how they'll be leveraging a class network. So, without further ado, I'll hand it over to. We'll start off with, I guess Max and Cloud most, because I know there's been a lot going on, and then from there, we'll go to Anil and we can continue on down the list of updates from clients. So Maxi want to start us off. + +Max: Sure, everyone. First of all, yeah, thanks for the support on the proposal. I think we broke your record. In terms of the participation from the proposal. So yeah, that's awesome. So yeah, we just created the repo for the open source people. + +Max: share it in the chat. yeah. Right now I also created the first pull request With the changes. + +Max: Give me a second. Yes. Either changes of icast. integrated In the Deploy Web previously, we had the custom code, To handle all the SDL parsing, and Creating the manifest and the version. But now it uses the ICASTGS library. + +Max: We have a lot of stuff. Going on to keep working on the CLOUDNOS. Interface and Tools. Right. Now since it's open source, anyone can use the indexer that we built and I'll acquired by the community. There's a bunch of documentation in the repo. That you can follow to run your own indexer. And you can play with it. There's a ton of stuff possible to do. With the indexer in the database. So, if you have any questions on how to run it, And what to do with it. Don't hesitate, I'm always the available on the discord. So yeah, in terms of the changes and stuff, we have a + +Max: not public roadmap but we work closely with Anil on things to improve and Things to build will be releasing. This week, the Adzi manager. That will Managing Your Authorizations in. And a small dashboard where you see all the list authorized addresses that you have. Authorized to spend on your behalf. Which will make it a lot easier for. Enabling free trials or just making someone or pay for someone else's deployments. And we also plan on A very shortly inspired by the Netflix platform. They did this. + +Max: When you meant an NFD and OMNIFEX they also pay for the fees with the authorization. So We'll add this as well, so you can just authorize an address. To pay for the deployments and also for your fee. So, It's this great for giving free trials for new users, they don't have any tokens. They can just get the authorization and try to deploy something for free, basically. Well paid by the user, that will grant the fees and the deployment. And a lot more stuff to come. But yeah, that's pretty much it for now can follow along and start a repo and Watch for pull requests and stuff, we're going to be pretty active on it. + +00:05:00 + +Tyler Wright: Thank you, Max. I see Julius had a question about. Are you all going to be switching to Akash JS in the future and just some plans there and does anyone have any other questions that they want to either throw in the chat, or others? Go ahead and you + +Anil Murty: I can actually answer that when I speak. And I can share a little bit of information on that as well. + +Tyler Wright: All right, so we'll come back to that question again. One of the things that the cloud most team is doing as well. The console team they are supporting sandbox environment for a number of folks on the insiders vanguards community. Are testing the network changes through the cost, GPU AI Incentivized Test Center. There was two bugs that came out of that test net, those bugs again had since been resolved have been tested by the Overclock Labs team and I've been tested by the community using the CLI, We want to make sure that again those bugs are not still having any issues or excuse me. The clients rather are able to do what they need to do when we move on to mainnet. So, again, that's another thing that the cloud most team is working on. Does anyone have any questions for the cloud most team before we move on to an update from Anil on all the efforts from the consulting? + +Tyler Wright: I'll hand over to Anil to give us update on console. + +Anil Murty: Thanks and I'll talk a little bit about cloud mostly console both because, The clubhouse team in me, and Joe have been working pretty closely. Leading up to submitting the proposal and stuff. So what I'll do is I'll just share my screen. + +Anil Murty: so yeah, as Max said, Promptly. As soon as the proposal passed that most people is open source and kash network now. So check it out if you haven't already. + +Anil Murty: The first answer the question that Julius asked, I think so prior to us, sort of writing the proposal and stuff and going through the voting on this and putting it out there, We actually talked through how we could have synergies between the two teams that was as well as console. So essentially So, a little about this as part of the Proposal that we put on discussion as well. And there's a product strategy, dog, regiment read, but this is fairly high level. And I understand there is really high level but we kind of want to do not go super detailed on this one. But we have been working together to figure out what areas where + +Anil Murty: There are things that are common feature between the two clients. So, I called out in the strategy. Doc essentially cloudmose is going to continue focusing on battery, whether they've done really well and then console is going to pivot and focus on trying to go after web to users and make a product. That's really attractive to them specifically initially, at least AI developers who have to. But all that said, there's a lot of features for a deployment clients that apply to both types of users. And it's in our best interest to make sure that the code that is used in both of these products is reusable so that we're not repeating and redoing things in both the platforms going forward. + +Anil Murty: luckily we have a library called Akashias and this is also something that is publicly available and is open source. So if you haven't looked at it akashiases right there, And so, the idea is that we would try to find common features that exist between the two platforms. And if they don't already exist within akashias, we would pour that code into akashiya. So if it's a feature that's implemented in Cloud, most that doesn't exist in console today and Cloudmoms has the better cloud noses implementation. We get into akashias so it's available to both the products as well as any other clients that print that to choose to Similarly, on the console side as well. So just to answer the other questions that came in I think, from Anish or Ishan. + +Anil Murty: this document is right now, just a Google docs that I shared between us in the clubhouse team. I am good to work on getting this into Github in the next couple of days. So it'll be available to all of you. And then along with this, we're also going to publish work on publishing a high level road map of what That was going to be working on and all of this is going to go into the C clients. So again for people, the people that are not familiar with this or joining us for the first time, if you go to Akash network here, one of the repos here is the community people. And then under community, we have various special interest groups and one groups. So one of them is sick clients were group, which is what this call is related to. And inside this, there are the various clients projects that are being worked on that. We typically talk about on this call. So what we're going to do is once + +00:10:00 + +Anil Murty: Clean up the roadmap, we'll put it inside. The cloud, most deploy folder here for anybody to look at and then we'll figure out, somewhere maybe we can put the table that I showed you in the word doc as well. I'll take a look at Cool. That's the general updates. I want to talk about in terms of answering that question. As we're talking about Cloud, most places console, a couple of things that I think Max probably didn't mention it simple, but I would love to talk about in terms of things that cloud, most team ship last week is number one, the shift UI for being able to view and set attributes for providers. So essentially if you're a provider that's connected to the wallet and you go to cloud, most now you can actually see Attributes that you've set for your provider and you can change those values for those keys as well. + +Anil Murty: And then if you're a client, you can actually view all the attributes that you're seeing. I posted a note about this after Max posted on the WG Working group for provider attributes and discord and basically, I just want to clarify that. There's no intention here to become a provider management platform. That is, creator guys are doing a really good job of managing that from a UI perspective. The intention of doing this was few Lee to do two things. Number one, be able to test if the schema that is proposed, earlier in a word document and now in this link that Max is just shared testing, if that schema is going to work with providers. And if it's not gonna have testing if it's gonna have some issues with certain the way things and named or, the way the values are created. Before we roll this out and mass or scale it out to all the providers. + +Anil Murty: That's kind of number one and then the second is This relates very much to the client experience because today, when you're deploying on Akash, regardless of which clients you're using one of the challenges you have, is that there is no way for you to query all the list of providers and say, I only want to see providers being able to say things like only show me providers that are located in a certain region of North America or, providers that offer a certain type of capability. Whether it be a support or something else. So the idea is to have attributes that can help us query as well as filter on providers based on those requests that the clients might have. And so as we scale the number of providers and Akash, let's say we get into the hundreds of providers, somebody should be able to apply these filters and just look at a list of 10 or 20 providers and decide. What's working for them. That's kind of the intention So provide attributes implemented by the cloud. Most team amazing job. Check it out on + +Anil Murty: Our most deploy, if you haven't. And then the second one, which is sort of smaller, but it's something that is bothered me as well as hopefully many others reviews cloud. Most in the past, is If you've used SSH the shell interface on cloud. Most + +Anil Murty: You may have noticed that it often feels like it's timing out so you enter a couple of commands in the container and then come back to it a few minutes later and no longer have access to the shell so it almost Emmanuel fix to that as well. So now it should be such that, you can navigate away from the tab that has a shall Come back to it, initials still should have access to the container and this is really important particularly for people that are doing, AI Fine tuning or inference, where you want to have access to the shell. Copy a bunch of parameters, or download a data set into your container, that's running the model and losing access to it and constantly having to open the share this kind of pain point. So, great job on that as well. Cloud Nose team, + +Anil Murty: On the console side, there was a couple of bugs that were mentioned in the Cloudmos, channel on discord as people went through the Testnet. So I believe you has made the fixes for those. One of the big ones was an issue around persistent storage. One of the things that I do with console is we're trying to not worry about bugs that, are going to be purely on the Vetri side. Because going forward, Moses going to be the tool that will be used for that. But if it's seeing that they're going to impact, even the Web 2 version of this console, we're going to go fix them. So that's why you might see. and things getting prioritized a little bit lower, the console side but it's in a staging environment that we host internally + +00:15:00 + +Anil Murty: and then we also have a new landing page that we were working on prior to this acquisition and, changing the direction. So it looks something like this. So it push this out the production and, this is not like something that is going to be the new landing page for Console 2.0 or something. It's just being interim until we figure out the new experience. So that's kind of the main updates on the cloud nose and console side. I do have another thing I want to talk about in terms of a conversation that we have with another team, but I want to pause here. See if there's any questions on Cloud Mods or console. To check the chat really quickly. + +Anil Murty: So I'll take a couple of minutes Tyler just to talk about it. One more thing since I have the mic right now. So I think they should be folks from Agora Labs on this call as well. ishan's on. I think maybe a nation thomasville I see a Thomas from Montfort's Maybe that's down. Hey, don't so good. + +Thomas Montfort: How's it going? + +Anil Murty: Thanks for helping on short notice. So I just think these guys five minutes before the call and asked if they can join. So they thanks for joining So Tom Ishan in Anish, they're kind of starting to work on a project of their own and hoping to build upon console going forward. we talked a little bit last week, and, they have some ideas around building, something that is very similar to the strategy that was outlined as part of the Cloud Nose acquisition For building something that is a good user experience for AI developers and doesn't have a very very native interface to it. So I just kind of wanted to put that out here and I was telling the Agora Lab team that + +Anil Murty: Earlier this year, we made the decision to go 100% open source and all the things that we do are done in the open as part of these things. So, once you guys figure out, what the user experience is going to be and will work together on that. We should publish respect for it here. and installing that, but in the most immediate term, I think the plan for the Google team is to work on a prototype for the upcoming HACKATHON. So that's kind of the initial milestone. So with that, I'll kind of see if you guys want to share anything more than that ishan or Thomas or anybody. + +Thomas Montfort: Yeah, I can just give a brief high level overview but yeah, we really were AI ML, engineers by trade. And what really struck us with Akash was the GPU testnet and this support toward GPU Forward is insanely huge if you're trying to deploy or fine-tune a model right now it's just insanely Very hard to get to resources so that was really what caught us And so we've just been diving into the community just kind of seeing what is being built. And we notice kind of, with the very web to focused, Emma engineers. They're not going to want to have to get tokens deal with wallets all of that. But are more immediate plan for this. HACKATHON is really building out an interface for fine-tuning models. So you would be able to say + +Thomas Montfort: Here's my data set stored in S3 bucket or somewhere else. Here is a preset model that we have, maybe it's Lama 2 and then we're going to automate the deployment to the network itself. So that's kind of high level our plan and obviously that brings into question or thought like checkpointing the model How do you deal with providers shopping off? So yeah, that's just high level. What we're planning on building out. + +Anil Murty: Thanks for that quick introduction and Appreciate you guys jumping on in short notice again. Yeah, if there's any questions on that. I mean, it's super early. They haven't really figured out what they're going to build, but the good thing is, There's a hackathon coming up. So hopefully we'll see something soon. + +Anil Murty: on the topic of checkpoints. The other thing that might be worth sharing is more of a heads up. Is We've also been talking with another team that is building kind of for a solution for being able to + +Anil Murty: Do something called Lower Training which is low rank adaptation of large language, models or large models In general. The idea with that is you take an existing, really large AI model and rather than retaining it on the full set of parameters that it was very train it on a subset of those parameters with a smaller data set. And the idea is that if you are looking to improve the model by tuning it on a smaller data set, it lets you achieve that without having to use the massive amount of resources that was used previously playing the model to train the base foundation model. So we're talking to this team and we're trying to figure out if there's a way for us to enable them. + +00:20:00 + +Anil Murty: To be able to do this training on Akash when we get to the main So once we launched me in it, we'll look at seeing if we can enable them to train on our caution. It'll be a good example of being able to achieve that use case on Akash as well. + +Anil Murty: Because if you think about it, as part of the recent test net, we demonstrated a couple of things. We demonstrated being able to do inference. There's a bunch of people that build applications for infants and random And then we have had examples of people taking an existing model and, fine, tuning it with a smaller data set, or using something like envy chain to embed together, two different Llms or two different models together and utilize them. So that's kind of in the second camp of not just, running inference. But doing a little bit with the model, the training aspect of it is something that is exorbitantly expensive to do in general, if you wanted to train something and you need course you several millions, if not seven hundred millions of dollars to do. But this idea of using Luna is something that we think could get is + +Anil Murty: A good demonstrable example of training a model without actually spending that much of money. So the plan is that I'm working with that team to write up a proposal and I'll be publishing this on github discussions in the next few days. so that's just another update. I want to share as part of this. I think that's pretty much all the updates I had on my side for now. + +Tyler Wright: Does anyone have any questions about anything il Just talked about + +Tyler Wright: Is again pleasure to meet the new team. If you need anything, please feel free to reach out and SID clients and we can make sure you have everything you need. Cool. I do want to make sure there's enough time for the source network team, I know that we'll still be working on clients libraries. I know some of those efforts are still in discussion. Do you have any updates that you want to share in the work that you've been doing? I want to make sure that I give you some time if you need it. + +Joao Luna: Yeah, regarding progress on the libraries. As far as I know, I think the Java one is open source right now. The goal one is the one that's still close source. We are just using it internally to develop our own product and it's still up for discussion. So, I think that's the effort. That's coming in and it's really just waiting for the mainnet to have a stable release. We are currently just using the release candidates on test and sandbox. + +Greg Osuri: Hey, I'm starting to work on a clients and I need a library. Either I build it or you give me access to it. So it's gonna happen. Either way. so I would prefer you give me access good because I would rather build on your work versus, I'm going to do it, but I do need to go library. I think it's important that we have a go library before a Java library, considering not to maybe we'll use Java or, other stuff we're on Akash. But look go, I wish I could. + +Joao Luna: Yeah. that's something we can definitely discuss further on the working group for the clients, + +Greg Osuri: Yeah, and the funding I think it's a clients, It's a library. I mean, Give me two days. I'll give out a version, I think we should put something out there first And grow right a roadmap. As I want to develop this library and get funding for that, right? Because I think it's too small of an initiative. Not to discount your work, but I'm talking to me. + +Joao Luna: So yeah. + +Greg Osuri: Standpoint of I built the library So I would do it myself if otherwise, I think it's too small often effort to warrant an entire funding proposal on shame but if you put something out there that is usable to certain point and of course you're going to need funding to continue working on it and then we can write a better diggers land, or roadmap and a proposal for that and public, So I'm going to do it regardless of funding, right? You need to be a library to the product then. That sufficient tomorrow 880 toward my involvement without having to actually get paid. so that's just my take + +00:25:00 + +Joao Luna: Of course. Yeah, that's something we can discuss. It was exactly our approach. so you can't,… + +Greg Osuri: Okay. + +Joao Luna: you kind of like a real library but already existing clients we've just found out. We're just two. The troublesome to use. So we kind of designed something that we as developers would like to use as a library and that's kind of what we built and where it was born from the only caveat it was that it was + +Joao Luna: Implemented according to the specification that was built at the start of the discussions on clients libraries. So that's kind of like that the twist that we had with apart from that this is something that we already were building because as you mentioned that you are requiring as well. We needed a clients library to start working on backend services and go there, interact with the cash network. So to make our product possible. + +Greg Osuri: Yep. + +Joao Luna: Yeah, it's fine. It's something that we can definitely further discuss on the working group. + +Greg Osuri: Sounds good. Thank you. + +Tyler Wright: Thank you, Greg's. Anyone have any other comments for Luna before I handed over to Source Network to give a demo. + +Tyler Wright: Before I do that, is there anybody from the Fleet team or sphere on team that wants to give a quick update? + +Tyler Wright: All right, if we'll get updates from those teams between meetings, I'll make sure they put something in the sick clients discord channel. Without further ado, thank you for all those updates from the teams and all the work that's going on. I do want to hand it over to the Source network team. I don't know if Ado Addo, I know that we've been talking in clients, as well as just generally in discord. They are a team that has been working on a decentralized solution that's going to be leveraging. Their cash network and I want to give them the opportunity to demo their solution in front of the group. So I'll hand over to Edo to get us going. + +Addo Smajic: Yeah, it's Addo. And … + +Tyler Wright: Of apologies. + +Addo Smajic: yeah, we have ours, I mean, I'll be quick. It's a decentralized peer-to-peer user-centric native, privacy preserving. No SQL database that we build from scratch to essentially a kind of plug fix that, issue with centralized databases that's plaguing. What three and kind of allow developers to bring true decentralization to their Applic. And I'll hand it off to John or CTO to kick off the demo. + +John-Alan Simmons: Adam, and ler. Thank Appreciate being here. You give us a chance to, show our stuff and hopefully gets really good feedback. So, let me go ahead and get my screen share going. + +John-Alan Simmons: And I think this is the one. + +John-Alan Simmons: Hey my various terminals and windows at the moment. Okay. + +Tyler Wright: Yes. + +John-Alan Simmons: Perfect enough the sides, Okay I can be a little bit open on some smaller screens. But I think we should be good to go. Alright so yeah, welcome we're building this presentation's database that I described. we're gonna go through today is really just kind of like what the mechanics and features and goals of this database is. And you know how it kind of affects the developers. What they really unlocks from an application perspective and kind of walked through some of the stuff that we're working on, obviously in relation to a cash and this ecosystem community and so, with that, we're gonna get started, we're just gonna get, a quick little instance, go into this database running on my local machine. I'll kind of go through a relatively soft and slow progression. And depending on what we get through, we get through real quick. Tyler, approximately. How long would we have for the total demo? + +John-Alan Simmons: Just want to make sure. + +Tyler Wright: We've gotten to the rest of the agenda. So we I think some people might have a hard stop in 29 minutes so we have another 29 minutes,… + +John-Alan Simmons: Perfect. + +Tyler Wright: I want to lay some clients at room for questions as well. + +John-Alan Simmons: That's most certainly. All And feel free to anyone, if there's anything that pops up there at the demo, feel free to pause and ask a question there, to wait for everything till the end. All right, so I'm gonna go ahead and run a instance of defer DB on my local machine. As I said, We're gonna start it up and I'm just gonna tell it to use the in memory store, I usually do this for demo purposes, just in case. I'm making a mistake. we can cook the delete the process and all the data will go away. But we do support our in memory store, Obviously, it's more performant, but, does not persistence. And then of course, we do support file back persistence and we're working towards, connecting that to long term storage providers. Are we see a storage day? Kind of, that whole, because of some things about going. But at the moment, we're just gonna start this in memory store. + +00:30:00 + +John-Alan Simmons: So it's gonna go ahead and just obviously put out some debug information at the moment. We don't care about anything but there's some interesting bits and pieces that will come back to you. In this notably some of the lid, pdp stuff that we have going on. + +John-Alan Simmons: And first and foremost, this is a No sequel, kind of document store database, but it is fully schemaed. So we're gonna go ahead and add a schema, from a schema definition perspective and really whole query language perspective, our entire database is based and built on on and around Graphql. we were deciding pretty early on how we wanted to have developers interact with and build in the system and what kind of query mechanics we're using. And, because of the way we're doing kind of this, no sequel document store process. And, we can really go down the SQL route. We didn't want to go down a route of creating our own custom query language because, that felt like that just was a huge burden on developers to learn. And so, Graphql kind of at the time was a very early thing as far as being integrated natively into databases, obviously they've been around just doing API things for quite some time. But, we were think the third database to actually start kind of like supporting Graphql as a first. + +John-Alan Simmons: This isn't on a database level, which was actually unlock, a really interesting, set of things that you can do with graphql, It solves a bunch of kind of traditional problems with the graphql but we'll get into all that. And so, we do support a bunch of kind of pretty interesting and rich models and relational structures and everything. You can see here this example kind of is a combination of one to ones. And one to many's the database managed a relationships for you. So you don't have to do a lot of the foreign key and primary key, definitions inscriptions to figure out all the making. Sure those lineup, if you just specify the type and the fields, then the database, if you so choose we'll basically manage that whole relationship for you. + +John-Alan Simmons: But in our kind of quick little demo here for the next 30 minutes, we'll use the straightforward one. If there's time we'll kind of transition to a little more complicated one and see some of the differences there. so straightforward. this particular user struct is gonna have four fields name age, verified and points and it's gonna have the respective types of string and Boolean and float. And again, this is just the graphql's way, defining types. So we'll go ahead and get this executed on the database. We'll do definitely be Clients schema ad and then we'll specify Pack F, which is going to the house to read from a file. And we're gonna read from that exact. So unsurprisingly that did exactly what we kind of expected it to do, and + +John-Alan Simmons: This is our playground. I actually comes bundled with our instance of the database and it's really just an easy way to kind of get going, sometimes you might need your own, native Graphql, clients or whoever it is. So if you want to just kind of get going and run it up, and testing and playing around with the database. This basically ships with the database, that's the bet. So you don't have to go get your own l clients. the really beautiful thing about Graphql and I know some of you may not but it is as you just saw a fully strongly typed and fully schemid language and so because of that you actually get a really kind of rich collection of + +John-Alan Simmons: Pipes that are actually generated behind the scenes and that's part of our database. Some of us just kind of native to graphql. which means that we get this kind of really great automatically, generated introspection APIs that go through all the types and all the systems that are defined. You can go through all the kinds of queries and because of that we actually get really fun introspection. I fired quickly just kind of the first second say we were going to create that query from Scratch mutation. Create user. we get the automatically done there. This we have to kind of do as a JSON blob. and stopping to kind of see in real time that + +John-Alan Simmons: action happening. And this is just a benefit of kind of graphql again to use battle ecosystem. Here, we get to introspect on the various fields key, which is the the Doc ID system, and we'll get into what that means in a moments name age. Verified and points. + +00:35:00 + +John-Alan Simmons: So same for as one here. I just want to kind of get you guys a chance to see that. you get that kind of like automatic IntelliSense right off the bat. We'd have to do anything to support that. All right, perfect. So we'll go back and run our original query. Because I know what to expect here. And we get back. Just this data payload, which is the response back from the database And the only thing we're actually asking for at the moment, is this ducky but we'll get into kind of what that means and how that really starts leveraging the powers of both mutable and immutable data and how that can be really really great for crustless verification of data state. + +John-Alan Simmons: So now we'll just go and run a general query. The name here doesn't actually matter. This is just a way to name a query and I like to do it because it means I get my little names on the top pads here, but that's just Handle thing to do. And so we're gonna go ahead and run again just like the general user query which is just the way to interact with the user collection as a whole. And so this user collection is what we define is our type and has our fields and it's the thing. We watched it, too. I'll add all the other bits and pieces here. and you can specify these in any order. Graphql is going to give you only exactly what you asked for. So if I don't ask for a certain fields, it's just not going to give it. + +John-Alan Simmons: And there we go unsurprisingly. Yet again, we're getting back to the exact kind of state that we ended up that we put into the database. You'll see though. One interesting thing that is that we didn't actually specify key parameter this Doc key. And so, again, like I said, behind the scenes, when you insert this type into the database, there's actually a whole series of codegen and scaffolding that's generated and all these, associated types so that we can do filtering type, safe, query and type safe, selection sets, you're able to do a lot of things and the database kind of leverages a lot of that for you. And so going through this, we'd have to go and find the key system, it's just there. + +John-Alan Simmons: Speaking of the ducky this is where the first kind of interesting mechanics and notions of how this database and what the underlying mechanics of this whole system is. And so I mentioned kind of we wanted to marry the concepts of both mutable and immutable data. And if any of you have worked with just the Ipfs API, as a whole and trying to connect build out a system using nothing but that Ipfs API and the Ipld data model, you'll know that it quickly becomes kind of + +John-Alan Simmons: Really exhausting and difficult task because you're always trying to stay up to date with whatever the current CID is of your state. And you have to do kind of a lot of effort to make sure that that stain and sync and potentially maybe you use an Ipns to do that. And you kind of have this static identifier that links to a mutable state Ipns has its own issues of slow query resolution and the records only stay around for 24 hours and it's global Dhd. And so for us the Doc key here it's kind of like our approach to having the familiar developer experience when it comes the databases of a reliable primary key that you can interact with but you still get all the benefits of that rich immutable, I appeal dhana is really just a CID + +John-Alan Simmons: In a UUID and is consistent and static for the entire lifespan of this document. If it gets updated and synchronized over the peer network and forked and branched and we'll get into what all that means. This Doc key will remain consistent and so if you take that key to any peer, you'll be able to resolve the same document and then verify that state and we'll see what that actually looks like. So again unsurizing we're getting back exactly what we're kind of expecting to get back. But I mentioned that we have this branch in your forking model and so if we were to go ahead and send an update to that particular document, using the update user mutation, we're going to specify just make sure that's the exact Keep you want? Yes, E5. + +John-Alan Simmons: So we're gonna send an update to just update the age of this particular user to 123 because apparently the most person in the world, we're gonna send the command again, unsurprisingly, we're getting back. Just the thing that we care about and if we go back to get, it's going to unsparsely, give us back these things. And I'm gonna say unsurprisingly enough because there's something that there's aspects of database development and as developers and consumers of the database. there are things that you just don't want to have to worry about bleeding edge technology, especially when it comes to databases because you want that ance. You want that, guarantee that some things are gonna be just there and working and the way you expect it. and so this database as a whole has kind of two. + +00:40:00 + +John-Alan Simmons: Allergies are too personas and we like to say, looking from the outside in, it should just feel like a database because foundationally is we've built this from Using the ipld data model, using lip P2P using Merkel, crdts using all these verifiable and structures, but at the end of the day, You should just care about that. It's a database and it's gonna fulfill your nudes as a database. if you want to start peeling back the curtains and actually understanding, how it's exposed this information and what that means for developers their applications and their end users. If we go to this commit step, and we'll go and get rid of this for a second. And we run this word. Yep. + +John-Alan Simmons: Yep. Absolutely. Yeah, It's a somewhat long-winded way to kind of work up to that because, all these factors go into what it means to be kind of a decentralized peer database and then how that mechanics and then why that decentralization in that peer become so important. When deploying it into, compute domains like a cash, so, kind of a somewhat long-winded explanation, but I will absolutely make sure that gets cemented. So, we're gonna go ahead and to run this commits API. + +Greg Osuri: So what's a CID remind me again? + +John-Alan Simmons: As so apologies CID comes from the Ipld data model which is the system that they're underlined data model, the powers IPFS and file coin and all that great stuff and it stands for a content identifier. + +Greg Osuri: Yeah, thanks. + +John-Alan Simmons: And so it's a way to, use IDs that represent the data rather than + +John-Alan Simmons: Everett And so using the database, this is how you feel like it should work but actually under the hood, this is actually how data is Data is interact with and data is built upon and this is where our Merkel CRDT system comes into play, which is a foundational requirement if you wanted to build out a, period of decentralized database because you want that ability to have that peer-to-peer because you want that ability, you have peers interact with synchronize in real time In first Merkel's crites, which is kind of this combination of using a Merkel clock from the IPLT data model embedded with a CRDT mechanic and a CRDT stands for free replicated data type. And with these conflicts, we replicated tips, you are able to have these really rich levels of collaboration without complicated or expensive global consensus. + +Greg Osuri: What kind of consistency does it support? + +John-Alan Simmons: So this falls under the strong eventually, consistent model, all clients will see the same state provided that they're on the same version. because each version is tagged and identify and it's structured as a graph or a DAG, then different clients that might see. Different states is only because they're just either further behind or further ahead in that day and… + +Greg Osuri: Are there any options for immediate consistency? + +John-Alan Simmons: And so, you're able to anchor these commits to our protocol and we have a Cosmo cell one. They're appchain that we're working on and so the first commit of any document gets anchored it automatically, and then from there on, you can kind of start. We'll be allowing to shoes. What is the frequency of the interval of those anchoring commits? If you don't need that,… + +Greg Osuri: That. + +John-Alan Simmons: strong global consistency, you can do it at whatever kind of interval that's batch together. If you want that guarantee you can anchor every commit and that's really just the CID that gets anchored on chain at that point. + +Greg Osuri: That how many verifications before eventual, consistency? + +John-Alan Simmons: So happy verifications for eventual consistency. I'm not sure… + +Greg Osuri: Yeah. How many interactions in terms of having … + +John-Alan Simmons: if I understand the question. + +Greg Osuri: Carlos, how to consensus work? How do you? Know. + +John-Alan Simmons: Yes, yeah. So the great thing about, the way Merkel series work, is that we kind of get this notion that we call consistency without consensus. And so, it doesn't require this global Really, any coordination amongst peers, it only requires just, verifying the DAG. When you guys appear receive it as a + +Greg Osuri: And set up a wall of type. because, + +John-Alan Simmons: Exactly. Yeah, baby very much. Kind of represents that wall mechanic. And again, from this being an ipld tag, it kind of follows those same semantics as well as, being able to pull down states, especially in different sets from different peers. And again, it doesn't require this global consistency, unless you want that strong mechanic, And so everything that was really good question. And so what this information actually, represents isn't all that important other than the fact that we actually get to structure and represent this data in a much more rich way and we can't kind of what we get out of that is really quite powerful, first and foremost, we have all these mechanics to query and filter and aggregate. I won't get into that for the sake of time and again, want to get to be cash stuff, we have the ability to run really, really powerful and rich migration. + +00:45:00 + +John-Alan Simmons: Patch systems that are powered by this really great project that we also wrote in Haus called Lens VM, which is a webassembly based directional migration or transformation engine. It doesn't matter what that means of the fact that we get decentralized scheme management and decentralized migrations, which turns out to be a huge pain, database migrations are complicated enough adding in, stronger vegetable consistency, and dags and decentralization. And peer-to-peer turn is no easy feat. So, we're able to build out a whole dedicated, migration system to allow different peers on different versions, to still be able to interact with synchronize and work with one another even in real time. Perfect. Thank… + +Greg Osuri: That's really cool that you're making migrations the first class feature. that's always a secondary feature and… + +John-Alan Simmons: Thank you. Exactly. That's + +Greg Osuri: it sucks, but what kind of oram support you looking at Besidesm + +John-Alan Simmons: What kind of orem? So I mean the great thing about the way Graphql works kind of out of the box is that it almost has this native ORM system in just wrapped up. + +Greg Osuri: Okay. + +Greg Osuri: Got it. Yeah. I'm still in this old SQL world,… + +John-Alan Simmons: Exactly. Yeah. + +Greg Osuri: but let's go. Thank you. All right. + +John-Alan Simmons: And so because of that, we get to actually type, Jen a lot of our clients and so you get this, really rich … + +Greg Osuri: Very slow. + +John-Alan Simmons: here parody with your code and then because of the way, Graphql describes documents. It kind of like you're application state and your application domain is gonna more closely match, your data state and your data domain, or… + +Greg Osuri: Thanks. + +John-Alan Simmons: am kind of client code gen. Mechanic means that you have Really close parody between the two, which is really, really Perfect. In terms of a cache Keenan,… + +Greg Osuri: Cool. + +John-Alan Simmons: do you have the link for the running instance? Or is it not live at the second moment? I keenan's, one of our devs on the + +Keenan Nemetz: I can find a link. Yeah what's more interesting is probably the deployment. + +John-Alan Simmons: All right, perfect. I'll start walking through stuff, which wanna do it? + +Keenan Nemetz: What's that in the chat right there? + +John-Alan Simmons: And I have that right here. + +John-Alan Simmons: And so, the really important thing for this database among all the important things that I've gone through and hadn't have fans to go through, is the deployment models about how and where and what capacity and in what trust and authority those deployment models require or necessitate + +John-Alan Simmons: And so really, that's a long way to say that the goal, this database is to be extremely flexible to kind of suit a lot of different application needs a lot of different user needs, a lot of different developer needs and so that means it deploys in a lot of different environments from, decentralized compute networks. Like a cache, which has been the first decentralized computer network that we've targeted for myriad of reasons. Obviously now, which needs to be described this crowd but, the same time we want to be able to deploy to, traditional environments and AWS and GCP. And so we actually have partnerships with both AWS and GCP to make that happen. This is being worked on to be deployed. + +John-Alan Simmons: The context of a webassembly deployment so you can actually bundle it directly inside your browser and run. alongside your application code, which becomes really important for you for guarantees around User-centricity. But, because of the way that the peer system works, you want to have this mechanic such that you can have as many nodes in as many different domains as possible effectively. And so for developers and for applications, for users, it becomes a really great trust model Knowing that, users can basically freely verify that they're pushing their own, local database state that's being generated in browser via webassembly and that's being pushed to another peer and all peers are just, equal databases in the network that's being pushed to appear that's being run on a compute network where you can publicly verify that it's running the state and it's running the images and it's running, the things the way you expected to because obviously when it comes to again this relationship of trust + +John-Alan Simmons: Even in the decentralized world, there's always going to be that establishment of who are we trusting and what is the authority. And for us it was a simple no-brainer that we foundationally needed to support a platform like a cash to be able to have developers spin up those nodes so that they can act as replication endpoints for users as they go through applications and generate state and generate data. yeah. So this is the cash deployment. I wouldn't say there's really anything off the beaten path. It's fairly straightforwarded but I just wanted to highlight why we've put so much priority with a cash specifically as far as decentralized compute networks. + +00:50:00 + +John-Alan Simmons: there's some other stuff that we kind of want to start working on as well. Kind of this idea of transparently creating micro VMs for users behind the scenes, when they Sign up for an application, the kind of be all and end, All of user-centricity and personal data repositories, is this idea that everyone's gonna manage their own servers? And, of course, you're not gonna expect, Little Granny to go out in some, Linux, Cisco, Sis admin stuff at 2 AM to make sure her box is running correctly and it's updated with the latest security patches, but the idea behind a cash which is basically, if you have some mechanic of pain for it, whoever, however, that is and you have a private key you can effectively just arbitrarily spin up VMs, which it's such a powerful function of what a cash provides and so you can kind of ultimately reach this Holy Grail of user-centric data and personal data repositories by leveraging both the Deaf or DV. + +John-Alan Simmons: Out of cash to build this whole ecosystem of micro VMs that transparently gets spun up for applications and for users as they kind of go through the sign of process without even them knowing that they have their own dedicated server sitting somewhere on the Internet. So that's some of the stuff I want to go through that. It is incredibly abridged and there is many things that I've lost over but I did want to kind of just seed you guys with kind of what other goals and requirements and functions of this database, how it relates to cash. And why we've kind of gone forward with this particular approach in this particular network. + +Greg Osuri: Yeah,… + +Tyler Wright: Excellent. Thank you. John Allen, Greg go ahead. + +Greg Osuri: thank you so much. This is amazing. I love database this for some background. + +John-Alan Simmons: You and… + +Greg Osuri: … + +John-Alan Simmons: me both Greg. + +Greg Osuri: I'm not an expert as much viewer and I love from a user standpoint that dealt with enough in my life too. to scale to a billion requests a day kind of thing. I also helped before for Eagle High,… + +John-Alan Simmons: Exactly, exactly. + +Greg Osuri: I help launch firebase, the first 10,… + +John-Alan Simmons: Really that I was born out… + +Greg Osuri: 15 years or so. + +John-Alan Simmons: Wow that's beautiful. Obviously Firebase inspired super bass and… + +Greg Osuri: So It reminds your demo. + +John-Alan Simmons: super based inspired Lee everything,… + +Greg Osuri: Really Yeah. Yeah. your demo reminds me of the early demo James. + +John-Alan Simmons: what's going on right now. + +Greg Osuri: The CEO fire says it. + +John-Alan Simmons: All… + +Greg Osuri: so, it has Right? + +John-Alan Simmons: bright future lead for us. That very beautiful. I'm glad to hear it. + +Greg Osuri: It has that sort of the feeling and I think what you're doing with a Christ's incredible. I love to. It's part of the road. Now we have this managed services where a user should be able to Schedule a container and… + +John-Alan Simmons: Yes. + +Greg Osuri: a database attached to the container just like… + +John-Alan Simmons: Yes. + +Greg Osuri: how you do on Heracles. That's the vision for cash, But do so on an orchestral way right into certain a very no without companies having to make deals,… + +John-Alan Simmons: Exactly. + +Greg Osuri: but rather protocols working with each other, So that's our vision and… + +John-Alan Simmons: Exactly. + +Greg Osuri: I think this fits right into that vision and database is the first obvious service, For fun application. That's managed And also, with IBC, you have interoperability, so you can have users pay in your own token or, now you have your SDC report, pretty much,… + +John-Alan Simmons: Exactly. Yep. + +Greg Osuri: right, so, it doesn't matter. So it makes it lots simpler in terms of payments. + +John-Alan Simmons: 100% very excited about that. + +Greg Osuri: And how your payments work, but you do whatever you can. If I want to stay, IVC payments, So, a lot of cool parallels. I can see how source can work with. The guy can really excited. I think we're gonna start sharing from this information online. that's okay with you. And thank you so much for the demo. + +John-Alan Simmons: Yes, absolutely. The more, the merrier, Thank you. Yeah, and regard kind of the manager service is + +Greg Osuri: Also. What's sorry what's your background? I mean databases. You don't just wake up and database, right + +John-Alan Simmons: So I just have this old adage that I don't know if I would preach to people once upon a time. And I basically said the Look if you end up that you have to build your own database you're doing something wrong and so that was years and years and years ago. And so now I've just eventually evolved into doing exactly what I said you should never do which is building my own database and scratch. Obviously I couldn't do this without the really great team we have here at source but foundation, I started in crypto and the mining days of 2011 2012 during the full blown Wild West s*** storm, that is crypto, apologies for my French. but foundation, it's like your science and number theory because I got into cryptography and then that just turned into building a alternative or competitive back in 2014 to Ipfs for a bunch of different reasons and then kind of leveraging that whole cryptographic structures and data models that I've learned and just leverage that into a database. And now we brought on this great team to make that happen. + +00:55:00 + +Greg Osuri: The database, right? with the,… + +John-Alan Simmons: Yes, it is fully acid. + +Greg Osuri: with obviously,… + +Greg Osuri: obviously in a comments and… + +John-Alan Simmons: Yeah. Exactly. + +Greg Osuri: Try to adapt to the blockchain… + +John-Alan Simmons: Yes. Yeah. + +Greg Osuri: but it's cool. + +John-Alan Simmons: There's Alan internal mechanics and it's been another couple hours with everyone but I was standing. + +Greg Osuri: let's do, I have more tarot, Presentation allows the demo,… + +John-Alan Simmons: Definitely. + +Greg Osuri: but more power to a bigger audience, I think + +John-Alan Simmons: Yeah, yeah, I just want to add regarding kind of the managed services comment, it makes such a beautiful pairing to have a database like this, that is verifiable and freely cryptographically secure and all this great stuff when it comes to, a deployment in a managed services context in the cache because, it's so great to have all this, decentralized cloud, computing and open marketplace and all those great stuff. But then we build all these applications like anchor to blockchains. And then we attach a postgres server to all of it and the developers just in charge of the postcode server, we go so far that at the last moment,… + +Greg Osuri: Mmm. + +John-Alan Simmons: it's just a bit of a stumble and so knowing that you can kind of combine that whole ecosystem of decentralization blockchain that we work towards with off-chain data solution to actually kind of mimics those. Same mechanics that allow the user centricity and everything is really powerful for us. + +Greg Osuri: Yeah, but try to put a podcast. You end up being a blue cell. That's a disappointment now. + +John-Alan Simmons: Exactly. yes it's just a postgres database that happens to maybe talk to a blockchain but not really + +Greg Osuri: And that until some doing ridiculous poster in the entire state in a single validator. And it was just ridiculous. I mean obviously the homemade progress that approach, nothing personality feedback was it anyway,… + +John-Alan Simmons: Yeah, exactly. + +Greg Osuri: but I'm glad you're taking a very ground up approach and you're addressing some of the score issues fundamentally. I think that's was incredible. I don't really get a minute and but thank you so much. + +John-Alan Simmons: Yeah, that's perfect. No, thank you Gregory. + +Tyler Wright: Yeah. Thank… + +John-Alan Simmons: I really appreciate the comment feedback. + +Tyler Wright: Greg thank John Alan. I know we have a minute left. I'm sure there's going to be continued conversations. I'll work with the Source network team to see if we want to do a longer demo but it was great for them to introduce themselves and give us a high level of what they're doing. A much appreciated. Max had a question that chat, How do you authenticate to the database just want to see… + +John-Alan Simmons: Yes. Yep. + +Tyler Wright: if you can answer that real quick before we get out. + +John-Alan Simmons: Definitely. So the high level Tldr in that is that we have, one of the mechanics of our cosmos. APP Chain is to be this Global Authorization service that connects into the database and that's built on top of + +John-Alan Simmons: a data model called Relationship-based Access Control. It allows hyper granular levels of access control and it's one of the things that we're integrating literally this week so it's very excited to see. But basically means that you can have database or documents in the database encrypted you can have Such that individual peers can have access to individual records inside of a collection. The collections are inherently and automatically multi-tenant for that reason, but you can also specify the policy access and encryption of documents all the way down to individual fields. And that means you can specify that only these people have the access to these fields and those people have access to other fields and that becomes really important. for example a medical context where, your name and birthday might be not public. + +John-Alan Simmons: under the axis of the, administrative staff, but your Social Security numbers and blood types are only access to medical staff. And so that's based off a whole did system. It's built off of a vertical tree based X Control policy engine, that uses Graphtuples. And again if we had another couple hours but yeah it takes a long understand but you can get really rich into what the solo enables. + +Tyler Wright: Much appreciated again. to all the participated today. Thank you to the Source Network team for the demo. Obviously, Thank you to the Cloud. Most Console Team, Luna for all the work that they've been doing. And clients, I will certainly again, have more discussions about source network in a number, get an updates throughout the month of another sick. Clients meeting around this time next month, and obviously there's a number of other SIG and Working Group sessions, that will be happening. Anybody from North Source Network Team wants to have any plans sessions again? Shout out to NDS on this call, who is going to help make these notes and the transcripts and the recording available in the community. I'm sure we'll highlight this at the Steering Committee at the end of the month. But again, if there's anything that you all want to do in terms of meeting with certain groups over the next month, feel free to reach out to me and we can coordinate some of those conversations but much appreciate everybody taking the + +01:00:00 + +Tyler Wright: Time today to have this sick clients monthly meeting was a great meeting. Anybody has any Thoughts comments about anything. This meeting. Feel free to throw those and discord and we'll just continue the conversation there until we meet next month. Again, appreciate everyone have a great day. + +John-Alan Simmons: thanks for the opportunity, Tyler + +Tyler Wright: Please our pleasure. Bye. + +Meeting ended after 01:00:29 👋 + diff --git a/sig-clients/meetings/009-2023-09-20.md b/sig-clients/meetings/009-2023-09-20.md new file mode 100644 index 00000000..487946b8 --- /dev/null +++ b/sig-clients/meetings/009-2023-09-20.md @@ -0,0 +1,129 @@ +# Akash Network - Clients Special Interest Group (SIG) - Meeting #9 + +## Agenda + +- Quick follow up from sig-clients monthly meeting #8. +- Update on specific Akash clients from representatives present at the meeting. + +## Meeting Details + +- Date: Wednesday, September 20, 2023 +- Time: 10:30 AM PT (Pacific Time) +- [Recording](https://hy3zv6e5mxhxnese25p5cupfitg236o6aeivmow6fxfvpnqmjr3q.arweave.net/Pjea-J1lz3aSRNdf0VHlRM2t-d4BEVY63i3LV7YMTHc) +- [Transcript](#transcript) + +## Participants + +- Anil Murty +- Dominic .B +- Emmanuel Arthur +- Joseph Tary +- Julius Haus +- Max +- Maxime Cyr +- Rodrigo Rochin +- Tyler Wright + +## Notes + +- Max and the cloudmos team gave updates on the work that they have been doing + - They have been working on AuthZ Manager. + - Max talked about the work they are doing with USDC. USDC is tricky, but the functionality is billed into the UI of Cloudmos. +- Joseph Tary gave updates on Akash Console. + - Joseph has been working on fixes to AkashJS as a result of the changes to the SDL structure. + - AI templates for different AI sdls have been added to console. + - A new feature is being added where you can configure GPUs from the actual SDL UI in Akash Console. +- Dominic asked about the status of GPUs on the Akash Network. Tyler reiterated that Mainnet 6 upgrade brough GPUs onto the Akash Network. + +### Action Items + +- Cloudmos and Console teams will continue to develop new features. +- Please use respective Discord channels for further questions or in depth conversation. + +# **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 Sid clients monthly meeting number nine. During these clients, special interest group meetings, the group gets together and talks about again. Everything clients related on the Akash network. There was a number of things that have happened. Over the past month. + +Tyler Wright: Since the last meeting, there's been a number of changes that both the Cloud most console team have made. I'm sure that they will representatives from those teams give some updates. There was a maintenance six upgrade. I know a lot of work went into making that upgrade possible by members of the community by clients that are 10 teams that are represented here. Again, the main That's six went up a minute. Fix upgrade went off fairly well. Again the upgrade with successful, There are a couple of things related to validator that are getting fine-tuned and actually are on chain right now for a small validator upgrade. But again, both cloud most and console, we're ready for the maintenance except grade and those are popular deployment tools being used by the Community Post upgrade. So again, shout out to those teams. + +Tyler Wright: Also, we got a great demo from the Source network team. I know that they've been heads down working with integrating into the source networks into the accounts network so we'll get an update from them on discord and I think at the next Stig clients monthly meeting So, without further ado, I do want to just hand it over to the Max's. I know that they've been working on a number of things, Cloud, most related, I just want to start off with some updates in the Cloud website. + +Max: Yeah, It's been a packed month, the past month. We did a bunch of stuff. Starting Officially open sourcing, our code, under the cash network. Organization. I'm sure everyone here has I could post it if it's needed. And also, We refactored. Our SDL handling code to use a cash JS. And the fixed a bunch of stuff inside a Cassius. Which is now fully supporting all the features of the current main net. + +Max: We also added the main support for GPU and USDC. So users cannot deploy GPUs. And also Usdc is a trickier to deploy with because you need to know the exact IBC denim to get bids from providers on the main net. So we'll address this and work to make it easier in the coming months. Because obviously, the usdc, deployments add a lot of value to the attachment work. And we also added the new towels on the dashboard and graphs for the GPUs. And also for the US or yet. Yeah. The US and the Usdc. + +Max: Spending. Which is also Nice to have in terms of Analysis of the network. Seeing the usd amounts of USB amount spent on the network. instead of just the Akt amounts, which is a very volatile and it doesn't Give a good representation of how much is being spent. + +Max: We've also improved, the sandbox support. We run a separate indexer for the send, but not sandbox now. So, Just as we did for the testnet, you can deploy and test stuff on the sandbox. With the full support of all the features and the platform. We also this week. Improve the provided list. It's not released yet. We're releasing it today. So it's going to be a lot clearer on the r providers list, which Pro GPUs are available. also working with a bunch of providers so that attributes properly for the provides schema attributes. + +00:05:00 + +Max: And lastly, we release the first version of the Oddsi manager with the feed grant features also. This is Going to be great for the future. Right now, there's a small bug That will be fixed in the coming year. Network upgrades that will enable ADSI to last longer than the deployment but yeah, so the Aussie management managers ready for supporting free trials, or managing multiple wallets and having a separate wallet for your deployments and stuff without having to transfer. Akts or usdc so yeah. that's about it or what we did in a bunch of bug fixes here and there, + +Max: Improvements based on the feedback. + +Tyler Wright: Excellent. Thank you, Max's. Again. + +Max: yep, for the prototypes and for the SDL parsing and stuff. Yep. + +Tyler Wright: Yes, excellent. does it? + +Max: Code is open source so you can look at it. + +Tyler Wright: I enjoys asking for message types as well, as Akasha has being used. + +Max: I'm not sure for this. I'll have to look at it. You can DM it if you really want to know later on Julius, + +Tyler Wright: I just want to add real quick. I know that there's a ecosystem cloud. Most channel in discord where if anybody has any questions, comments thoughts about any teachers bugs or any comments for the Max's. I know that both of them are very active in that channel and see messages. So does anyone else have any questions comments for the clubhouse team? + +Tyler Wright: Cool, if there's no questions there, then we'll move on to an update from the console team. I know that they've been doing a lot of things related to again. Continue developing on console, as well as a cost JS. Joseph, do you mind giving us a quick update on all the work that you've been doing over the past month? + +Joseph Tary: Yeah, so most of the work's been going into getting a cost JS. Working properly with all the new SDL changes and getting the new message types and everything integrated properly that works. Well complete now so August should fully support everything that's needed. And then all the actual console side, we added a new landing page with some additional template types. So now if you go to the console, there's deployment templates for some ML base workloads, as well as web services. They're kind of pulled out now, so there's no Webster or RPC stuff for Blockin. Web services stuff each separate categories of templates in the beach. And you can deploy with GPUs currently to configure GPUs. You do have to do it through the SDL. + +Joseph Tary: manually through the SDL. There is a UI component that's going to be going in sometime this week, so that you can configure GPUs from the actual SDL UI that just hasn't been put up on production. Yeah. + +Tyler Wright: Perfect. Thank you, Joseph. I know that again, out of the last meeting Anil had mentioned some work that was being done around documentation of similar features for Cloud, most and console. I know that work now been updated in is now again, live in this sick clients repo, I'm gonna put in the chat that people could see and we could just again if anybody has any questions feel free to drop those in discord and we could just talk about those over the month. But I know that was an action item and there was working on and again that action is now available for everybody to look at. Julius putting the Chinese put in. I opened up to update the examples in the costumes. Okay. + +Tyler Wright: Again, I'm throwing That client that I posture is cloud. Most accountable. MD in the chat. + +00:10:00 + +Tyler Wright: Does anyone have any other questions for console or relate to Akash JS before we move on? + +Tyler Wright: Related to clients in general. Again, I know the prey tour. Team is pretty heads down and they often give updates. During the sick providers meeting, I know, Luna has been working on a number of things. So again, he usually attends these meetings, but may not be able to attend today. I just want to see if there's anybody on this call. That's once to talk about anything specific or general relate to clients on the cost network. + +Tyler Wright: then again, if there's no further updates, if there's no further questions and we can certainly cut. This meeting short again. I know that the store's network team has been heads down and we'll give an update probably in discord over the next couple of weeks and then a follow-up at the next monthly meeting. So, look after that, you've heard all the updates being made by the Cloud most team, as well as a console team related to the deployment tools, as well as a cashier. Yes. So if anybody has any questions again, there's respective discord channels, where you can ask for their questions and get a feedback from the teams building those tools. And again, I know that's one of the other action items. We'll talk to Luna about in between meetings. I know Luna. + +Tyler Wright: Asking some questions about provider attributes, which we can have either a dedicated working group session or we can continue to have that conversation discord. And then I know there was conversation out of the last. Take monthly meeting around go client libraries, so we can see what Luna's thought about over the last month there. I know the core team has been thinking about it a little bit but again has been focused on the main net upgrade. So we can talk about that async and say If you need to have a dedicated session or if we can continue those conversations in discord. So I'll check those action items and make sure that we're pushing those items forward over the next month. + +Tyler Wright: Is there any other talking points that anybody wants to discuss while we're all here? If not that, I'll let you all, enjoy the rest of your Wednesday. + +Tyler Wright: again, Thank you. Joseph and others for joining the meeting and again, giving us updates. Thank you to all the questions. Thank you Julius for that. R update much appreciated, everyone's time today again. Please don't be shy. If anyone has any questions comments about any deployment tools or any clients in general, please feel free to ask and we'll continue Christian. Probably forward Dominic. Did you ever hand up + +Dominic .B: Hello guys. And thank you to. I'm happy to speak with you. I have a question, maybe for the next three year. Did we see the mainnet on the GPU? and if we see the Alpha from the Japan. + +Tyler Wright: I'm sorry. maybe as my connection, would you say, did you want to see that alpha of the GPU on the mainnet? + +Dominic .B: Yes, I meant. I mean we are now on the better side. Yes. and I mean, the mainnet from the last part from GPU, + +Tyler Wright: So again may not six It is been released. Yes, as an open the chat. So this is a live feature that is available on the network right now. People are actively deploying GPUs. And again, providing GPUs of all kinds from the Nvidia manufacturer actively right now in the network. So, there was a testing period. And then again, that's a couple of weeks ago, there was an upgrade that occurred, where that made that feature live, you can look at it again. I think Carlos Team mentioned, there are analytics on the cloud most pool that are available, that kind of showcase, what kind of GPUs available on the network, as well as deployments. And then again, pray to also as a tool where you can look at some of the analytics on again GPUs on the network and usage. + +00:15:00 + +Tyler Wright: I hope that answers your question, Dominic. + +Tyler Wright: All Again if there's nothing else. Then if anybody has any questions feel free to reach out to myself or anybody inside the SIG clients. Discord Channel, Dominic, I tell you go on me. Do you want to get something to follow up? + +Dominic .B: Thank you. And I am happy to be here from the beginning. Thank you guys. + +Tyler Wright: Our place again. Thank you all much. Appreciate the participation from the community. Again, it's a community that's been helping building tools testing of the network. So it's very much group effort and all the progress of the class is made over last couple of years. So much, appreciate you all. If anybody has any further questions comments, feel free to reach out and discord and SID clients or in a specific channel like cloudnos, or ecosystem console. Hope everyone has a great rest of their day and we'll continue to talk online. Thank you all. + +Rodrigo Rochin: You guys, + +Joseph Tary: Pictures. + +Meeting ended after 00:16:53 👋 + + diff --git a/sig-clients/meetings/010-2023-10-18.md b/sig-clients/meetings/010-2023-10-18.md new file mode 100644 index 00000000..9e5dbc52 --- /dev/null +++ b/sig-clients/meetings/010-2023-10-18.md @@ -0,0 +1,153 @@ +# Akash Network - Clients Special Interest Group (SIG) - Meeting #10 + +## Agenda + +- Quick follow up from sig-clients monthly meeting #9. +- Update on specific Akash clients from representatives present at the meeting. + +## Meeting Details + +- Date: Wednesday, October 18, 2023 +- Time: 10:30 AM PT (Pacific Time) +- [Recording](https://yofgxnfxaqk4jruuwko7pyrfckw27dtg5thp6c6bv2sfvfq66jla.arweave.net/w4prtLcEFcTGlLKd9-IlEq2vjmbszv8Lwa6kWpYe8lY) +- [Transcript](#transcript) + +## Participants + +- Anil Murty +- Julius Haus +- Max +- Maxime Cyr +- Scott Hewitson +- Tyler Wright + + + +## Notes + +- Max B and the cloudmos team gave updates on the work that they have been doing + - They have been working on AuthZ Manager. This is live and working right now. + - The main issue with AuthZ is that the deployment only last for one deployment. + - Working on user experience for the Cloudmos + - Max has been working to select GPU model. + - Max is adding features + - Max is working on adding SDL builder in the creation wizard. + - Max C started working on Cosmos kit to support for wallets. + - There was a contribution from to support Leap Wallet + - Cloudmos has added a FAQ page. + - Julius asked Do you replace leaps integration then with the release of cosmos kit? Max B. and Max C. + - The plan for the future is to continue to make it very easy to deploy on Akash + - Max B mentioned that they are working on an agent to monitor provider uptime and beyond. +- Anil shared that bug fixing and improvements will be paused for Console. The product is open source, so anyone else can do it. + - The Cloudmos team is part of the core team. All traffic will be directed to Cloudmos. + - Joseph Tary is going to be working on AkashMl.com +- Anil is going to post a message in Discord to let people know. +- All Links that point to Console will point to Cloudmos. There will be a banner on Console that pushes people to Cloudmos. +- Console open source repo will still be there. +- Julius asked Is there already work going on to transform the console to something mentioned in the updated product strategy? Anil mentioned that the thinking was maybe to use Console codebase, but the decision has NOT been made yet. +- Issues for Cloudmos should go into https://github.com/akash-network/cloudmos/issues. +- Anil mentioned that with the Console team being sunset, and some teams not able to join the calls regularly, should the frequency be changed? Tyler will bring this up between meetings, and this can be assesed. + +### Action Items + +- Cloudmos team will continue to work on user experience improvements +- Cloudmos will be pushed as go to deploy tool. Console will remain open source, but new features and bug fixes will not be prioritized by Overclock Labs in the short term. +- Tyler will determine if the cadence of the meeting should change. + + +# **Transcript** + +_This editable transcript was computer generated and might contain errors. People can also change the text after it was created._ + +Tyler Wright: Welcome, everybody to the Special Interest Group for Clash of Clients Monthly meeting Number 10. During these monthly meetings teams that are building on top of Akash building clients come together to talk about updates, respective to their clients. There is a github folder that has a number of folks that have been participating and usually participate during these SIG clients calls. I'm going to put that in the chat so that people can see my cloud. Most console FLEEK open registry. Pray to our sphere on Terraform and others. I know that folks are very busy so much. Appreciate the cloud, most consult team. And again, Julius from the inside is for joining, + +Tyler Wright: but out of the monthly meeting. Number nine, we got some updates on console the work that Joseph and Anil have been doing as well as updates from the Max's and all the works. They've been doing on the cloud most fronts. So, again, as part of the typical agenda, we continue to get updates on a monthly basis from various teams. I know that again, the console team is here today as well as a crowd, most team. So Without further ado, I do want to pass over to the club most team and I'll take the notes in the background on some of the updates that you all have been working on over the last month. + +Max: Hey everyone. So yeah. Sure. I'll provide some updates. + +Max: What was the updates from last month? I'll try to find it, but yeah, we've been Working on improving a bunch of things in the clubhouse. UX, mainly towards the appointment experience. More recently. I've been working on adding more features to the STL Builder. + +Max: the GPUs being able to select GPU model in the SEA on Builder adding support for Usdc payments in the SL Builder. And other features that we're missing the IP Lease and HTTP options. + +Max: of also working on adding the SEO builder in the Creation Wizard of Deployments, it's working right now. So being able to create a pull request later today. + +Max: But else. + +Tyler Wright: Max last week or last month rather you were talking about civil work that you were doing on the Offsee manager as well. I think everything else you've covered already from last month but only thing I know that you were working on last month was off the manager. + +Max: Yeah, this is been released and it's life. So it's working for both the deployment oddity and the fee azi. But I think the main issue with the artsy for deployments is that The authorization only lasts for one deployment. So It's not. that useful right now but it will be a lot more useful once this Bug or feature is implemented. and it's on the timeline, I think for Implementations. + +Max: but yeah, Max has been working on bunch of A very interesting features and project that you can talk about. + +Maxime Cyr: Yeah, So yeah, recently was mainly bug fixes and started looking into integrating cosmoskit to support more wallets. So, right now, we have Kepler and recently we get a contribution and github for the daily wallet. And we all to support, even more with Cosmos Kit. + +Maxime Cyr: and also I think since the last meeting we added the FAQ page, So in the discord we see of, then the same issue coming back. So now we can direct them to the FAQ page with the most common issues. + +Tyler Wright: Excellent. Thank you,… + +Maxime Cyr: Think that's it. + +Tyler Wright: Thank you Maxine. + +Tyler Wright: Julius just asking a tattoo, replace leaps integration. Then with the release of Cosmos Kit. + +00:05:00 + +Maxime Cyr: And maybe we'll need to see the planet there yet. + +Max: It wasn't that many changes the leap to Cosmos, so it shouldn't be big change from leap to customer skit. We'll see. + +Tyler Wright: Is that in the works? Over the next month or what are some things Max's that you are thinking? you're going to be working on over the next month. That might be worth. + +Max: So we will. like I mentioned the earlier, our focus on the next week is really to + +Max: make it much easier for a new users to deploy on a cash. So, Experimenting with you Types of deployment creation, workflows. and also, + +Max: We've been working Creating an agent to deploy on all the providers to help monitoring the uptime. And A bunch of other attributes from providers to. + +Max: monitor their performance at time and stuff. So yeah, I need that and just fixing the issues that are posted in our issues That Anil posted. + +Tyler Wright: Thank you, Max and Anil. Thank you for dropping in, just as a reminder, I think this has been spread on discord and elsewhere. If anybody has any issues related to most again, Cloud most has a specific repo in the Akash Network organization, where you can drop in all those issues I believe. And they'll drop in not only the access to the issues, but then, specifically issue number 34, that Max was just talking about so again, anything cloud most related. Feel free to drop those issues in the cloud, most repo inside the Akash network organization. And again those things will get talked about. If folks are there during the six support or again can be handled async be a github. + +Tyler Wright: Also want to shout out the Max's for all the work they do inside discord. I know there's a specific channel ecosystem dash cloud, most where again, the max it's a very responsive when folks, from the community. Have any specific questions around cloudmouth so much, appreciate the Max's and all their efforts. Does anyone have any questions for the Cloud most team before we move on? + +Tyler Wright: again, Carlos team, thank you very much for the updates. I know you have a lot going on. I don't know if you wanted to give any specific updates on anything console related. I know Joseph usually does that but I know he's been handling some other things this week. So I don't know if there's any specific updates. You were wanted to get today or if you want to handle that Asyn. + +Anil Murty: You actually do have a couple of updates. So I think one of the big updates is that. We are going to be pausing active development and bug fixes on Console obviously is open source. So anybody else it wants to continue working on it from the community is, welcome to do. So to submit PRs in will be happy to review them or have others review them, but we are going to be pausing active development on console. Both bunk fixes as well. New feature development, This is family motivated by two things. Number one. Given that the club most team is now part of the core team. + +Anil Murty: and the want to try to and given what Max said right there they're working on UI changes that in some ways would make potentially the workflow similar to what Console has in terms of, jumping in and potentially having the SDL builder be part of the deploy workflow. Given how similar that is to console and given that they're part of the core team. Now it makes sense to direct all traffic to that one too. As opposed to trying to divide up, the traffic of people that wanted to apply onto two different tools. so that's one reason and then separate from that is as people may have seen with the Akash, ml.com, webpage announcement. + +00:10:00 + +Anil Murty: Joe is going to be spending time working on some prototyping efforts around that and so He's the primary developer on console from the core team. So he's not gonna have time to spend on console and so for those two reasons we're gonna, Pause active development on console, To communicate this, we are going to be posting a message on various discord channels about this change and directing people to use cloudmuse for the deployments and then we're also changing the website, our cash dot network and point pointing all links that point to console today. To point the cloud most + +Anil Murty: Within console itself. They'll be a banner that will tell people that there isn't active development happening from the core team. And that people should. Consider using cloud modes instead of really used. + +Anil Murty: That said, there have been a maybe more than a couple of teams that have Akashat on submissions, that use Console. So, by no means is console, open source report, not going to be there, or it's still going to be there for people that want to develop maintain or host in terms that still going to be there. And people are welcome to submit peers into console. It'll still be there a little bit working. It still works. + +Anil Murty: yeah, so Julius to answer your question, we are currently looking at various options for the stack that we want to have for The Akash ML and AI ML strategy initially as the thinking was, to transform console into that. But we are rethinking that a little bit given night. The Akash Channel service is going to be a service that we want to target primary towards Web to developers. We're trying to figure out if it makes sense to build on top of console or build, something, completely different. So, That's kind of where that is. But, yeah, you're right. Initially, the thinking was, console will be that product, but there's still thinking, if we need a completely different stack, One of the challenges with building, the IML product is, We don't want to be tied to a specific AI model today stable, diffusion is very popular. But, in the next few months, there might be something else. + +Anil Murty: and so, having something that is relatively flexible and can adapt to various models and allow us to not be rigid in terms of the inputs, we accept or the outputs that we put out and also being more developer friendly than just having a UI. So building something that is API driven and driven potentially so, it's kind of thinking over So that's kind of one main updated in. I think the other update, Is. if I think you mentioned the style there's issues on cloud, please submit them to the cloud. Most people given the cloud Moses, open source now. + +Anil Murty: There is an issue section inside that repo. I've been submitting issues there and, encourage anybody else that is running into bugs or has suggestions for improvements to cloud, most to submit them there. And then we've seen a couple of people already Pull requests for changes to cloud modes, so hopefully we'll see a lot more of that way forward. That's all right. + +Tyler Wright: Thank you. Anil for that update? Does anyone have any questions about anything? I know just mentioned. + +Tyler Wright: again, I know some teams are going to be giving some updates on some of the work that they've been doing over the last couple of months async in the Sick Clients, discord channel. If anybody here has any other questions comments or concerns between meetings, feel free to drop them in the sick clients discord, channel or again and ecosystem. Cloud, most channel if you have something specific to cloud, most Is there anything else clients related to anybody wants to discuss right now or while we're here? + +Anil Murty: One thing I was wondering and we don't have to decide right now, but if the participation on the C clients client, is a call isn't super Heavy and it's primarily the Cloud Nose team. And given the proposing console development a little bit. One thing to consider should reduce the frequency of these calls, just to save people time, but it's something that we can probably socialize with other people that are building because, initially we had a bunch of different clients show up to these meetings. So maybe we can put our banner and say, Hey, people aren't able to join these calls regularly. We don't want to waste everybody's time, maybe because they may be other month or something like that. + +00:15:00 + +Tyler Wright: Yeah, I think that's a great call out. And something that we can circulate as you mentioned in discord and look to change the frequency, if we get consensus + +Tyler Wright: again, if there's nothing else and much appreciate everyone's time today. again let's look Stay connected in between meetings and again. we will reassess the frequency of these calls and make sure that we're optimizing the time that we're spending together. But much appreciate everyone's time today. And again, if anybody has any updates, questions concerns, feel free to drop them in the SID Clients discord channel. At any time, we'll talk to you online. Thank you, everybody. + +Anil Murty: Thanks Tyler. Thanks everyone. + +Max: Thank you. + +Julius Haus: Bye. + +Meeting ended after 00:16:43 👋 + diff --git a/sig-community/README.md b/sig-community/README.md index 62c74f99..074e49f2 100644 --- a/sig-community/README.md +++ b/sig-community/README.md @@ -19,6 +19,28 @@ This SIG (Special Interest Group) is designed for Akash community members to pro | #1 | Thursday, January 31, 2023 11:00 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-community/meetings/01-2023-01-31.md) | [Link](https://github.com/akash-network/community/blob/main/sig-community/meetings/01-2023-01-31.md#transcript) | [Link](https://fss4l23i24p6gntryybnqrr5mss4u2bhkutvcdq7avzexqhchida.arweave.net/LKXF62jXH-M2ccYC2EY9ZKXKaCdVJ1EOHwVyS8DiOgY) | #2 | Tuesday, March 14, 2023 11:00 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-community/meetings/002-2023-03-14.md) | [Link](https://github.com/akash-network/community/blob/main/sig-community/meetings/002-2023-03-14.md#Transcript) | Coming soon | #3 | Tuesday, April 11, 2023 11:00 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-community/meetings/003-2023-04-11.md) | [Link](https://github.com/akash-network/community/blob/main/sig-community/meetings/003-2023-04-11.md#Transcript) | Coming soon +| #4 | Tuesday, May 09, 2023 11:00 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-community/meetings/004-2023-05-9.md) | [Link](https://github.com/akash-network/community/blob/main/sig-community/meetings/004-2023-05-9.md#Transcript) | [Link](https://rfjancfiutbtyzyeejxwwqjx7blgeiqqlnjzcw7soszajp7nx7ra.arweave.net/iVIGiKikwzxnBCJva0E3-FZiIhBbU5Fb8nSyBL_tv-I) +| #5 | Tuesday, June 13, 2023 11:00 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-community/meetings/005-2023-06-13.md) | [Link](https://github.com/akash-network/community/blob/main/sig-community/meetings/005-2023-06-13.md#Transcript) | [Link](https://myhqjm7ptqmwz7ul2yss6gjqz25ljc57zamuqdzfpcgweai64j4a.arweave.net/Zg8Es--cGWz-i9YlLxkwzrq0i7_IGUgPJXiNYgEe4ng) +| #6 | Tuesday, July 11, 2023 11:00 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-community/meetings/006-2023-07-11.md) | [Link](https://github.com/akash-network/community/blob/main/sig-community/meetings/006-2023-07-11.md#Transcript) | [Link](https://ldcymjv57vzkxb54husr63qq3saae7qhwos2vcvjoln32ny6cy2q.arweave.net/WMWGJr39cquHvD0lH24Q3IACfgezpaqKqXLbvTceFjU) +| #7 | Tuesday, August 08, 2023 11:00 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-community/meetings/007-2023-08-08.md) | [Link](https://github.com/akash-network/community/blob/main/sig-community/meetings/007-2023-08-08.md#Transcript) | [Link](https://7zxtouwijc7m4syzoixc4ncvcas5hvm46mka44lzxyyr63zi3f6q.arweave.net/_m83UshIvs5LGXIuLjRVECXT1ZzzFA5xeb4xH28o2X0) +| #8| Tuesday, October 10, 2023 11:00 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-community/meetings/008-2023-10-10.md) | [Link](https://github.com/akash-network/community/blob/main/sig-community/meetings/008-2023-10-10.md#Transcript) | [Link](https://kmbia36nv7zwt7js6cprsuwqgor6bs5wsk3io4h7eswdwldv244q.arweave.net/UwKAb82v82n9MvCfGVLQM6Pgy7aStodw_ySsOyx11zk) +| #9| Tuesday, November 11, 2023 11:00 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-community/meetings/009-2023-11-15.md) | [Link](https://github.com/akash-network/community/blob/main/sig-community/meetings/009-2023-11-15.md#Transcript) | [Link](https://elrhjnozov4zcwv4mcpc7n4za4nyuxelufxrk56hniqprbk3bmka.arweave.net/IuJ0tdl1eZFavGCeL7eZBxuKXIuhbxV3x2og-IVbCxQ) +| #10| Tuesday, December 12, 2023 11:00 AM PT (Pacific Time) | Coming Soon | Coming Soon | Coming Soon +| #11| Tuesday, January 09, 2024 11:00 AM PT (Pacific Time) | Coming Soon | Coming Soon| Coming Soon +| #12| Tuesday, February 13, 2024 11:00 AM PT (Pacific Time) | | | +| #13| March, 2024 11:00 AM PT (Pacific Time) | | | +| #14| April, 2024 11:00 AM PT (Pacific Time) | | | +| #15| May, 2024 11:00 AM PT (Pacific Time) | | | +| #16| June, 2024 11:00 AM PT (Pacific Time) | | | +| #17| July, 2024 11:00 AM PT (Pacific Time) | | | +| #18| August, 2024 11:00 AM PT (Pacific Time) | | | +| #19| September, 2024 11:00 AM PT (Pacific Time) | | | +| #20| October 2024 11:00 AM PT (Pacific Time) | | | +| #21| November, 2024 11:00 AM PT (Pacific Time) | | | +| #22| December, 2024 11:00 AM PT (Pacific Time) | | | +| #23| January, 2025 11:00 AM PT (Pacific Time) | | | + + ## Leadership diff --git a/sig-community/meetings/008-2023-10-10.md b/sig-community/meetings/008-2023-10-10.md new file mode 100644 index 00000000..085e18bd --- /dev/null +++ b/sig-community/meetings/008-2023-10-10.md @@ -0,0 +1,190 @@ +# Akash Network - Community Special Interest Group (SIG) - Meeting #8 + +## Agenda +- Planning for upcoming events in 2024. +- High-level overview of Akash Education. +- Review of recent hackathons and their outcomes. +- Discussion about the insider program. +- NodeOps demo + +## Participants +- Adam Wozney +- Andrew Gnatyuk +- Cosmos Hoss +- Damir Simpovic +- George Pro +- Julius Haus +- Naman Kabra +- Tyler Wright + +## Meeting Details +- Date: Tuesday, October 10, 2023 +- Time: 11:00 AM PT (Pacific Time) +- [Recording](https://kmbia36nv7zwt7js6cprsuwqgor6bs5wsk3io4h7eswdwldv244q.arweave.net/UwKAb82v82n9MvCfGVLQM6Pgy7aStodw_ySsOyx11zk) +- [Transcript](#Transcript) + +## Meeting Notes +- Adam discussed the current status of the community, highlighting the completion of the 2023 series of events. +- Mentioned that they are now looking ahead to 2024 and evaluating the community's achievements and future goals. +- Adam mentioned the need to build up AkashEdu and thinking about the next Hackathon. +### 2024 Event Planning +- Adam mentioned that they are working on events for 2024. +- Adam encouraged participants to track and share ideas in the "2023 Events" Discord Channel. +- Adam emphasized the importance of community involvement and making the Akash community more decentralized. +- Adam is planning to host a working group call to discuss the event list, gather community input, and solidify the events list for funding proposals. +- Adam mentioned that this process will happen within the next month. +### Akash Insider Program +- Adam explained the Akash Insider Program, which is community ambassadors praogram of Akash. +- Adam mentioned that he is conducting an audit to assess current members' involvement and looking for ways to increase engagement and support. +- He highlighted the aim of reaching out to inactive members and considering onboarding/offboarding. +- Discussed plans to revamp the Akash Insider Program for the New Year with potential improvements. +### Hackathon Updates +- The first virtual Hackathon with Dorahacks is over, with 24 valid submissions out of 56 (others were spam). +- Adam is discussing ways to decrease spam and potentially hosting another Akash Hackathon in the New Year. +- Adam stated that judges are currently reviewing submissions, and the winners will be announced at the end of the week. +- Adam highlighted that community members are welcome to help organize and put together the new Hackathon. +### AkashEdu +- Adam Wozney discussed the [AkashEdu initiative](https://akashedu.omniflix.tv/), which was launched around five to six months ago with the goal of creating educational content. +- Currently, there is one curriculum available for becoming certified Akash experts, focused on becoming providers on the Akash network. +- The plan is to expand the educational content and curriculum to cover more topics and areas related to Akash. +- Adam is considering how to source content and allocate resources to build up Akash Edu. +- Adam discussed the goal of creating certified Akash experts. He mentioned the need to expand the curriculum and plan for the New Year. +### NodeOps demo +- Naman Kabra introduced [NodeOps](https://akash.nodeops.xyz/), a tool that simplifies Web3 Development infrastructure for new developers. It has been under development for over six months. +- Nodeops aims to streamline the life of node operators and developers, making it easier for developers to work with various app chains within and beyond the Cosmos ecosystem. +- Naman explained that Nodeops leverages AI and focuses on developer tooling and simplifying infrastructure for developers. It offers features like spinning up a node, a developer tooling playground, and automation of various complex tasks involved in setting up infrastructure. +- Adam expressed his appreciation for the demo and asked Naman how long he has been working on NodeOps. +- Naman revealed that the work on NodeOps began in March 2023, with the live launch in mid-July and plans to deploy infrastructure on Akash for new chains. +- Mentioned discussions with Tyler and the Overclock team about template types that would benefit the developer community. +- Tyler thanked Naman for the demo and emphasized the importance of feedback from the community, especially developers and less technical users. +- Tyler encouraged everyone to continue testing and providing input, highlighting the goal of adding tools to support Akash network adoption. +### Action items +- Adam Wozney to create a rough timeline and proposals for 2024 Akash community initiatives. +- Adam to develop a list of events for 2024 and host a working group call to discuss and finalize the events list. +- Adam to conduct an audit of the Akash insider program. +- Adam to discuss the expansion and improvements in AkashEdu in future sig calls. +- Naman to collaborate with Overclock team to determine useful templates. + +# **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, thanks everyone. For joining, today's SIG community call for those that don't know I'm Adam. I had a community for Overclock Labs. I'm basically the Sherpa for these calls but as with all of our SIG calls, always looking further, folks, to jump in and kind of take a leadership role. So, if you're interested, let me know. But in the interim and the foreseeable future, I am happy and obligated to manage these calls. This is the first one we've done in a while. The last one we did was in August in September, there was a handful of events that were going on. So we had to postpone, our regularly, scheduled monthly cost community call until today. But there's a few things that I wanted to cover. And if anyone else has any yet items or questions or anything, just raise your hand. And I'll get you involved in the conversation, but to kind of kick things off. I want to start at a pretty high level. So folks that are just watching this recording or haven't been on this couple before + +Adam Wozney: The whole purpose of this call is to kind of discuss support and manage akash community initiatives. They could be anything from events to educational materials to content to Twitter spaces, to even other SIG calls, special interest group calls. So really, it's all about discussing the Akash community at a high level and understanding what we can do to kind of make it better for everyone that's involved. Today's agenda is pretty straightforward. you talk a little bit about the upcoming year. Want to talk about our hackathons that we participated in. We ran recently, talk about upcoming ideas around 2024 events, getting community members involved in upcoming events for 2024 I want to talk briefly about Akash Edu, which I think some of you are familiar with, I'll kind of give a high level. That is + +Adam Wozney: Talk a bit about the insider program and then we should have plenty of time to hand it over to naman from node ops to do a quick demo. so before I jump into that, any questions or agenda items that people want to discuss or bring up, you can feel free to put in the chat too as well if you're in a loud space, + +Adam Wozney: Cool then Yeah I'll kind of kick things off. So currently I would say where the community stands is 23, series essentially wrapped up at this point. There are no more events that it cautious participating in. We're starting at least on the overclock lab side. Think about 2024 in terms of community, I'm starting to kind of evaluate where we stand as a community today. What have we done over the previous year? What we can do in the future and I think we'll be starting. So in the next community Sig call. My goal is to have kind of a rough timeline or rough outlook or what we can do. what are some proposals, we can put together for 2024 as the Akash community. + +Adam Wozney: So where things stand in terms of that is I'm currently working on our events for 2024 2023. We held as the first year that we ever really worked with the community to put together events where Akash could have not just overclock labs representation, where I work in Tyler and others but bring community members into representative cosh to make it more of essentially, a Dow structure. So, I'm thinking about what that looks like. I'm thinking about + +Adam Wozney: Continuing to build up Akashi Edu that's been a bit on the back burner, but that's because we had a lot of events going on, and I just really didn't have time to kind of shirp of that. But I'm starting to think about how I can push forward to cash you to educate people on all the different aspects of Akash, so people can become certified. I'm also thinking about what our next HACKATHON looks like, which I'll cover here in a second. And then I am doing a bit of an audit of our current Akash insider program. And for folks, listening on this call, people in the call right now. Cash, insiders are essentially a cautious community ambassadors. They're people representing and events creating content providing community support, doing a handful of different things inside the Kaash community. + +Adam Wozney: So, I'm doing a bit of an audit looking through. Who's currently in our program, seeing who still wants to be involved, looking for things that we can do to kind of spur engagement, and support and educate people that are in the program. Then also ramping up onboarding and applications essentially lead generation to get new interested parties to get involved in the community. So that's kind of the high level of where we're at right now and what 2024 looks like still a few months left in planning but I just want to plant seeds of interest for people that want to get involved and what that looks like. Going on to some different community initiatives and projects. So our first ever virtual HACKATHON with door hacks is over, currently the judges are reviewing about 24 submissions of the 56 submissions that came in. why only 24? Because the other 24 were essentially spam. So I'm working with Dora Hacks on figuring out how we can + +00:05:00 + +Adam Wozney: Decrease spam and increase the number of projects that are submitted because I am thinking about another presentation, at least creating a governance proposal on hosting another caution in the New Year TBD. I want that all looks like what the focus of it will be. But anyone inside the community is welcome to help organize and put that together similar to what we did to this previous HACKATHON. what does that mean, essentially creating another working group for a new HACKATHON? So that's kind of where that stands. yeah. Last thing, Is I think we're gonna reveal the winners judges are currently reviewing, but we should be reviewing the winners, hopefully, at the end of this week or early next week, so stay tuned for that. + +Adam Wozney: On the event side. Yeah, as I mentioned I'm starting to think about 2024 events where Akash can have representation from the community and from Overclock. So currently I'm starting to develop a list of events that would make sense for a cash to participate in. The plan is, once I have that list ready, I want to host a working group call similar what we're doing right now. Inviting anyone that's a part of the Akashi community to join where we'll discuss the events list that I created? Talk about what doesn't make sense for us to Hear from the community itself on events where maybe missing? Hopefully, solidify that events list. Put it into a governance, proposal for funding, get approval and then start working on what our presence looks like that at those events from sponsorships, to community representation, + +Adam Wozney: So that should happen. I would say within the next month or so, stay tuned for that. But if you want to track or you have ideas, head over to the discord Channel, 2023 events to get involved. Go ahead, Andrew. + +Adam Wozney: Yep. That's a great idea or Capo Troy so yeah one of the things I want to do I was thinking about similar what I was just talking about and thinking through 2024 is potentially in the next SIG community call doing kind of a recap of 2023 community initiatives which would include that and then kind of plant seeds for what 2024 could potentially look like. So totally with you, makes total sense, Andrew, good feedback. + +Adam Wozney: I'm just gonna write that down. + +Adam Wozney: next up is yeah Akashi news. So for folks that aren't familiar cashews, something that we launched actually a number of months ago already if you want to review exactly what akashi to use, I'll put in a link in the chat but basically that's the wrong link. I don't know why that one was selected. + +Adam Wozney: it is this one copy and go here there, that's the one. So akashi to use, essentially a initiative. we launched maybe five six months ago, all with the goal of creating educational content. So folks could become, certified to cache experts. Currently there's only one curriculum that's loaded, that's entered a pretor. So people can become providers and the cash network. But I think there's a lot of content that we can create the recent akashathon. People will actually created some Kashi. Do you content that? I think we can add to the platform, but my goal is to build that out. So folks can become certified experts. So I'm starting to think about what that looks like going into the New Year, We create we can source content, how we can resource allocate individuals to participate and building up Akashi edu. + +Adam Wozney: So, I'm starting to think more about that, and I think that's something that we'll talk about maybe in the next SIG, call or I'll be able to talk about in some of these insider calls that we have for the insider community. So, starting to think about that a bit more And then the last thing that I mentioned before we hand it over to naman for the node ops demo is the Akash insider audit. So currently as I mentioned we have about 50 or so around the world. Insiders for folks that aren't familiar are the akash essentially cost ambassadors. They do all the things that really help make a cosh. + +Adam Wozney: Is from creating content to Hunts to participating a hackathons to attending events representing They do a lot of different things. It is totally volunteer based. There are no requirements. The only kind of unwritten rule is If people join the program it's kind of expected that, if you joined it, we thought you'd be someone engaged. So, I'm currently going through our current list of insiders, just seeing when people were active inside of discord, seeing when people have been active at, attending our insider calls just kind of doing a general audit of the insider program right now. + +00:10:00 + +Adam Wozney: so my goal is to reach out to people that haven't been to engaged, see if they're still interested understand where they are and then either, help them kind of off-board or just get a better understanding of what they're interested in. Because we do have a lot of applications that have come in for the insetter program. And I want to make sure that people that we bring on board, when they join our discord channel or jump into the regularly scheduled weekly calls we have for the insiders, it's not a ghost town, that's just not a good onboarding process. So I'm doing a general a caution cider kind of audit, not just, seeing who's participating and who isn't. But also thinking about onboarding off-boarding, what are some new programs or initiatives? We can put together to kind of get people involved. What can we do? A better job in terms of support and education. + +Adam Wozney: So I'm hoping to kind of revamp a new and improved in a caution cider program, going into the New Year. I don't see too many giant changes. I think it's at a pretty good stage right now but there's always some room for improvement. So I'm looking at kind of updating the insider program going into the New Year. So with that, those are really the big high level things in the community side that I'm been thinking about. And that I think the community's been working on. Are there any questions comments or any other items that people wanted to discuss before I hand it over to naman from node ops for a demo? + +Adam Wozney: If not, that's totally cool. Or if you do have thoughts, feel free to ping me and we can kind of or just go into the discord channels to community discord channel and let folks know there. + +Adam Wozney: All So with that, I think we can hand over to Naman for a note Ops demo. Go ahead naman. + +Naman Kabra: Hey Thanks, I did have a couple of questions but I think those would be on set after, I quickly walk you through Nodeops is very glad to be here. Guys could to connect with each. One of you just a quick background of when working in the Cosmos space for a while. And node offices essentially something that has been under the hood for, more than six months now. And the reason for that is very clear, we just wanted to have more foundations coming on board and eventually helping each and every foundation to drive more applications and developers towards, building out some crazy apps and use cases, within and beyond the Cosmos ecosystem as Thanks. So I'll just quickly share my screen and walk you through what we've been doing around at Nodeops as well. And I think Tyler has already shared one of the very first + +Adam Wozney: Looks good. + +Naman Kabra: So Nolox essentially is focusing towards simplifying the Web 3 Development infra for new developers Looking to tap into Building on any particular app chain in this case. Right. So what was the actual motivation for us to build this out? there has been lot of chatter around, Developer experience needs to be improved for onboarding more and more applications from the traditional world towards a particular protocol, or particular app change, And Yeah, I recently have seen, a good amount of traction towards building out some really good use cases as well. But when you look at infra ways applications, and in probe is toolings and setting up things, when it comes to note operations, a lot of the things are redundant, and the process is typically, + +Naman Kabra: repeated throughout right and that is where, we started with Node ops as the name, suggest, simplifying, the life for node operators initially, right? So what were the problems for being near developers after talking to multiple developer communities, within and beyond Cosmos couple of things, which we observed was, the struggle when it comes to configuration and troubleshoot. + +00:15:00 + +Naman Kabra: You do to multiple reasons, One of them could be, developer dogs, limited support, in terms of the use cases or limited support in terms of the setup process and getting started, right? So that's where, we're decided to build nodeops, which essentially is one of the very first apps. That is leveraging AI as an infra but more focus towards developer tooling and simplifying, the infra for them to get started, right and a couple of things, which, nodeops eventually provides you is, you can spin up your own, while later node here. So imagine it as a node as a service for anyone to quickly, not just having no code environment, but a low code environment where they get to walk through the entire process as if they're interacting with the document right within what UPS and fried itself and dep. + +Naman Kabra: Nakash in this case, And on top of it. The developer tooling infrastructure is nothing but a simple playground, right? Which we have kept very close to, typical ID which developers generally interact with so that it not only acts as your co-pilot but also gives you very updated backend infrastructure when set for you, right? So you not only have to + +Naman Kabra: you literally don't have to do anything around initial pre-installation of binaries ensuring that you're using the latest upgrades and interacting with the right rpcs nodes setup All of those things. When it comes to interaction with the chain We take care of setting that up and eventually simplifying this complex loop. When it comes to set up to a very Structured process Driven route for developers to onboard them as an active developer, So all in all the objective remains for developers to focus on the business logic and rest of the things been taking care by no dogs as an infra, where exactly this comes into handy as well? Right. So I think right now, because you were talking about Akashi, do you and a lot of hackathons, as well? One of the + +Naman Kabra: Core Challenge for Hackers to participate. the last thing they want is within the 72 hours of Hackathon. they spent two days in just setting up the infra, or two days and just interacting and building out the very base application. All of those things could be easily eliminated when we use something called playground, which I'll also show you, after this slide, which would eventually be for you to just start. + +Naman Kabra: Out the application, using the Boilerplate code snippets everything. In terms of test, nets accounts, faucets node interaction. Everything has been set up in the backend already for you, So that is one of the best use cases for such educational tutorial. Workshops wherein, playground become so one stop solution for developers to get started with building out the application and for hackers to quickly validate, whatever they are building, and focus on the application logic again, right? And on top of it. + +Naman Kabra: we are going to integrate this playground across multiple developer channels. For example, Dora Hacks being one of them we are in talks with multiple different developer community as well. For example GDC Google Developer community across a pack wherein all the workshops which they organize we would be providing a playground for them and be there. Infrastructure partner so that they can literally consume the playground for the workshops which are very specific to a particular protocol or a chain, right? So that's where we would have a lot of ecosystem. Daps been coming out and build right. We've made more of life close to three to four chains right now. For example, mean Cosmos hub, excellent archway, and akash as well. We spend up with template eyes and automated it. So + +Naman Kabra: That we can spin it up for any new chain within seven days, So, I'll quickly show you the current version of Akash as well and walk you through the components of how it looks like throughout, right? So, the signup process is very straightforward because the objective here is to onboard, the newer developers, we are eliminating all the friction in terms of setting up a wallet and stuff, you can literally sign up with Get Up Gmail and get started. You do have an own chain wallet required when you are, having a contribute and own setup, So I'll walk you through that process later but just quickly showing you the components here, So right side is more focus towards just being a Aggregator wherein, what we do is we maintain the most latest, direct access of the links around data sources chain. Registries are PCs for + +00:20:00 + +Naman Kabra: Is Right and Documentation and GitHub for both Mainnet and the latest Testnet. The GitHub section. You see is basically not only tracking the latest commit across the open source repositories of Akash. But there is also an automated vulnerability tracker in the backend. What that would do is let's say if any of the repositories is having we a critical vulnerability, interact by the pipeline, it would automatic + +Naman Kabra: Quickly trigger a sticky note here, for developers to ensure that they know that their app might be exposed to certain vulnerabilities. So, because there are no critical to see, your vulnerabilities been tracked, right now by the pipeline, there are no sticky notifications but once the vulnerability is tracked, rather than waiting, for the official communication from the foundations, about the app been exposed, you would directly get a notification right here. So that, this becomes a one-stop solution for developers to also track, what's happening on the get up front, right? So + +Naman Kabra: that was more from the data aggregation side, the middle interface is simple, Charge GPA type of interface but the one step ahead, which we are taking it is, the try it functionality, So if you have used anything like geeks for geeks, where you have everything been set in the backend, this is actually very similar to that wherein. All you have to do is select the language, it's like everything in terms of binaries. All of those things has been set up in the backend for you, right? So this acts as a simple CLI which is already been set for you to test out certain quotes snippets when it comes to interacting with the node. let's say there are certain use cases or templates which is literally a mandate when it comes to getting started, right? So for example, if someone is interacting with Akash, that's not right now. + +Naman Kabra: And all he wants to do is just have a sent transaction using CLI bin set, rather than asking them to set up the wallet and doing all of those things. We have a one-click deployment here, wherein all you have to do is just update the RPC and you can literally run this code snippet on your own right here, So this templates are right now, just contribute it from our end that is node of steam but very soon we would also have a gamification monetization mechanism wherein any developer can come in contribute the templates and they would be incentivized for those contributions right here so that the data would be automatically trained, we would be very fine. So there would be two sections here. One is very fine and one is So anything that comes from community side of things, Why are this contribute and mechanism would actually be put in under the section and once it's very fine. + +Naman Kabra: Goes throughout actual verifications by Boat Devrel team from the foundation, from our. And from our end, we would put it under verified section and then it would be monetized based on every consumption right now to take it a step further, right? That's where the playground comes in, which is + +Naman Kabra: Basically a one-stop ID for, anyone to actually get started with building out, So what we do is we have a entire docker based back in province. we maintain everything starting from binaries to the correct set of repositors and this is fully configurable, right? So all we have to do is ask developers to just come here, build out use cases or literally utilize the existing one and everything when it comes to binaries. Yes. As the case is actually been, set in the back and for you, right? So, + +Naman Kabra: this eliminates all the configuration side of things for you and you can literally plug in this playground anywhere, So let's say Dora access hosting any HACKATHON, All they have to do is just let us know, what are the core use cases? We take care of the setting up of this infra and giving you a simple widget which you can stick it up on the Dora Hacks website itself. So anyone once click on that playground, they would just be given a sign in button and it would take you directly to the playground or if you are literally hosting some, workshops in Akashi, You can literally have one of the, pop up as sort of widget as playground and anyone can literally play around with the tut. + +00:25:00 + +Naman Kabra: Else as well, So this is what we have created so far. in terms of traction as well, we live with archway version of it mid of July that is July 15th. Within two months, we had close to 6,000 conversations, been done, and + +Naman Kabra: Around 120 plus developers coming in and interacting with the playground close to 200 plus containers where built out that is nothing but 200 plus, repositories been out by leveraging playground and templates were consumed as well. And on an average, each developer spend close to six minutes for utilizing templates and playground, which is comparatively longer than what we anticipate them. We want this to be, as quick as possible for developers and for them to literally have the solution for whatever they're looking in less than five minutes. Right. So that's the journey so far. And, we live with just the very first version a couple of things which should be optimizing. Here would be in the template section for and I think this is something which we are in talks with Tyler balls and the Foundation team as well in terms of what type of templates. + +Naman Kabra: Would be super helpful for developer community and courses, like Akashi DU and initiatives like hackathons, and also leveraging playground at its best for any kind of node operators related, system here, right? So Yeah, this is the progress right now. I'll be happy to take any questions if you have. + +Adam Wozney: That was awesome naman. Thank you so much. Only real quick question Holly. Been working on that. + +Naman Kabra: So we've been working on this, since March, right? So first couple of months just went on ideating and simplifying. The UX first setting up the right architecture, we live with Archway in July mid, And after that, we've just been spending it up for multiple chains. Like a car acceler Akash main Cosmos hub as well Tera classic as well. There has been a lot of interest from the Terra Classic Foundation, by the way, for more of their testnet side of things. So we did span of the new top version for them as well because the documentation was a mess after the Tera Collapse Inter Classic Foundation. So, yeah, that's been the journey so far for us. + +Adam Wozney: Very cool. thank you for the demo. Any questions for naman before we wrap up today's call? + +Adam Wozney: Tyler, go for it. + +Tyler Wright: And necessarily a question. But again naman, thank you for the demo. I just want to add if anybody here because I know number of folks here are on the insiders Vanguards can continue to play around with it. I know I put it in discord but if anybody here wants to continue play around with it and give feedback. We're continuing again, That's a great support from folks, like you all on this call that help out with many people that are developers or less technical folks We're just trying to add tools like what no options built. So just again looking for feedback. I just continue getting more adaption on the cash network. So thank you very much. and I guess, + +Naman Kabra: Thank you. And this is just the very first version, guys. So, of course, the responses would also be compatibly slows because we have not scaled up the infra since it's been under the testing phase. But the plan is for every new chain, whatever infrastructure we would be setting up for them. We would be deploying it on Akash so that's gonna be the plan and we've been discussing with the foundation around the Process for setting those things up as super excited for it and would love to, hear your feedback, your views and, of course, anything that you see in particular, which we can improve upon as well. + +Adam Wozney: Thank you so much Any other final questions for myself naman. + +00:30:00 + +Naman Kabra: Thank you, everyone. + +Meeting ended after 00:30:59 👋 + + + + + + + + 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-design/README.md b/sig-design/README.md index 86dae30d..12e68835 100644 --- a/sig-design/README.md +++ b/sig-design/README.md @@ -17,18 +17,30 @@ date: 2023-1-09T00:19:20-08:00 | --- | --- | --- | --- | --- | | #1 | Thursday, February 2, 2023 08:00 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-design/meetings/001-2023-02-02.md) | [Link](https://github.com/akash-network/community/blob/main/sig-design/meetings/001-2023-02-02.md#transcript) | [Link](https://uj3nmvkwwqwjkd3jzkkhbjf3w7rewuvfqrmcdapficmmik4gudzq.arweave.net/onbWVVa0LJUPacqUcKS7t-JLUqWEWCGB5UCYxCuGoPM) | #2 | Wednesday, February 22, 2023 08:00 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-design/meetings/002-2023-02-21.md) | [Link](https://github.com/akash-network/community/blob/main/sig-design/meetings/002-2023-02-21.md#transcript) | [Link](https://e6wptkexnljmfnq6swe4qbbu54assn65grzlurzvpizzlreiro5q.arweave.net/J6z5qJdq0sK2HpWJyAQ07wEpN900crpHNXozlcSIi7s) -| #3 | Wednesday, March 8, 2023 09:00 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-design/meetings/003-2023-03-08.md) | [Link](https://github.com/akash-network/community/blob/main/sig-design/meetings/003-2023-03-08.md#transcript) | [Link](https://apru4o53g355qdxpxifh2ejjvopsqlmf5c7zlmnygpqq33vekvya.arweave.net/A-NOO7s2-9gO77oKfREpq58oLYXov5WxuDPhDe6kVXA) -| #4 | Wednesday, April 12, 2023 09:00 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-design/meetings/004-2023-04-12.md) | [Link](https://github.com/akash-network/community/blob/main/sig-design/meetings/004-2023-04-12.md#transcript) | [Link](https://6xo72sp45srm3peei2i57kitrya34ftrqffk3irtxgfyxxjhmxbq.arweave.net/9d39Sfzsos28hEaR36kTjgG-FnGBSq2iM7mLi90nZcM) -| #5 | Wednesday, May 10, 2023 09:00 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-design/meetings/005-2023-05-10.md) | [Link](https://github.com/akash-network/community/blob/main/sig-design/meetings/005-2023-05-10.md#transcript) | Coming Soon +| #3 | Wednesday, March 8, 2023 08:00 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-design/meetings/003-2023-03-08.md) | [Link](https://github.com/akash-network/community/blob/main/sig-design/meetings/003-2023-03-08.md#transcript) | [Link](https://apru4o53g355qdxpxifh2ejjvopsqlmf5c7zlmnygpqq33vekvya.arweave.net/A-NOO7s2-9gO77oKfREpq58oLYXov5WxuDPhDe6kVXA) +| #4 | Wednesday, April 12, 2023 08:00 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-design/meetings/004-2023-04-12.md) | [Link](https://github.com/akash-network/community/blob/main/sig-design/meetings/004-2023-04-12.md#transcript) | [Link](https://6xo72sp45srm3peei2i57kitrya34ftrqffk3irtxgfyxxjhmxbq.arweave.net/9d39Sfzsos28hEaR36kTjgG-FnGBSq2iM7mLi90nZcM) +| #5 | Wednesday, May 10, 2023 08:00 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-design/meetings/005-2023-05-10.md) | [Link](https://github.com/akash-network/community/blob/main/sig-design/meetings/005-2023-05-10.md#transcript) | Coming Soon | #6 | Wednesday, June 14, 2023 08:00 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-design/meetings/006-2023-06-14.md) | [Link](https://github.com/akash-network/community/blob/main/sig-design/meetings/006-2023-06-14.md#transcript) | [Link](https://inlakgk4lzlfmrveddowlqvf3olzpxeklmrjdksle6defao4ehea.arweave.net/Q1YFGVxeVlZGpBjdZcKl25eX3IpbIpGqSyeGQoHcIcg) | #7 | Wednesday, July 12, 2023 08:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-design/meetings/007-2023-07-12.md) |[Link](https://github.com/akash-network/community/blob/main/sig-design/meetings/007-2023-07-12.md#transcript) | [Link](https://4v5gjbxldak3kwlx7jbkp2gcgp4ovvbf6q67ue2oyp22w2guavua.arweave.net/5XpkhusYFbVZd_pCp-jCM_jq1CX0PfoTTsP1q2jUBWg) -| #8 | Wednesday, August 09, 2023 08:00 AM PT (Pacific Time) |Coming Soon |Coming Soon |[Link](https://7hbbbiaiqssx7redpnzevdfif3smtvixbsd6uahwjtqugqcndxia.arweave.net/-cIQoAiEpX_Eg3tySoyoLuTJ1RcMh-oA9kzhQ0BNHdA) -| #9 | Wednesday, September 13, 2023 08:00 AM PT (Pacific Time) | | | -| #10 | Wednesday, October 11, 2023 08:00 AM PT (Pacific Time) | | | -| #11 | Wednesday, November 08, 2023 08:00 AM PT (Pacific Time) | | | -| #12| Wednesday, December 13, 2023 08:00 AM PT (Pacific Time) | | | +| #8 | Wednesday, August 09, 2023 08:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-design/meetings/008-2023-08-09.md) | [Link](https://github.com/akash-network/community/blob/main/sig-design/meetings/008-2023-08-09.md#transcript)|[Link](https://7hbbbiaiqssx7redpnzevdfif3smtvixbsd6uahwjtqugqcndxia.arweave.net/-cIQoAiEpX_Eg3tySoyoLuTJ1RcMh-oA9kzhQ0BNHdA) +| #9 | Wednesday, September 13, 2023 08:00 AM PT (Pacific Time) | Coming Soon | Coming Soon | Coming Soon +| #10 | Wednesday, October 11, 2023 08:00 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-design/meetings/010-2023-10-11.md) | [Link](https://github.com/akash-network/community/blob/main/sig-design/meetings/010-2023-10-11.md#transcript)| [Link](https://lpgpnhvzo3h4wr6vc7qy5rggghi2qztpqj6krjuzlevcmcypf63q.arweave.net/W8z2nrl2z8tH1RfhjsTGMdGoZm-CfKimmVkqJgsPL7c) +| #11 | Wednesday, November 08, 2023 08:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-design/meetings/011-2023-11-08.md) |[Link](https://github.com/akash-network/community/blob/main/sig-design/meetings/011-2023-11-08.md#transcript)| [Link](https://mctlnmdevhysanes52tbok6kbc3mgbsgnn6qemc35xhanfc2x67q.arweave.net/YKa2sGSp8SA0ku6mFyvKCLbDBkZrfQIwW-3OBpRav78) +| #12| Wednesday, December 13, 2023 08:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-design/meetings/012-2023-12-13.md) |[Link](https://github.com/akash-network/community/blob/main/sig-design/meetings/012-2023-12-13.md#transcript) | [Link](https://une76rieq3cvbtrnjv3gxaw6kbxaay3tnzqsangya2lfe6ionpva.arweave.net/o0n_RQSGxVDOLU12a4LeUG4AY3NuYSA02AaWUnkOa-o) | #13| Wednesday, January 10, 2024 08:00 AM PT (Pacific Time) | | | | #14| Wednesday, February 14, 2024 08:00 AM PT (Pacific Time) | | | +| #15| March, 2024 08:00 AM PT (Pacific Time) | | | +| #16| April, 2024 08:00 AM PT (Pacific Time) | | | +| #17| May, 2024 08:00 AM PT (Pacific Time) | | | +| #18| June, 2024 08:00 AM PT (Pacific Time) | | | +| #19| July, 2024 08:00 AM PT (Pacific Time) | | | +| #20| August, 2024 08:00 AM PT (Pacific Time) | | | +| #21| September, 2024 08:00 AM PT (Pacific Time) | | | +| #22| October 2024 08:00 AM PT (Pacific Time) | | | +| #23| November, 2024 08:00 AM PT (Pacific Time) | | | +| #24| December, 2024 08:00 AM PT (Pacific Time) | | | +| #25| January, 2025 08:00 AM PT (Pacific Time) | | | + ## Leadership diff --git a/sig-design/meetings/008-2023-08-09.md b/sig-design/meetings/008-2023-08-09.md new file mode 100644 index 00000000..03c6629c --- /dev/null +++ b/sig-design/meetings/008-2023-08-09.md @@ -0,0 +1,219 @@ +# Akash Network - Design Special Interest Group (SIG) - Meeting #8 +## Agenda +- Website design elements improvements. +- Design style and elements. +- GPU landing page design. + +## Meeting details +- Date: August 09, 2023 +- Time: 08:00 AM PT (Pacific Time) +- [Recording](https://7hbbbiaiqssx7redpnzevdfif3smtvixbsd6uahwjtqugqcndxia.arweave.net/-cIQoAiEpX_Eg3tySoyoLuTJ1RcMh-oA9kzhQ0BNHdA) +- [Transcript](#transcript) + +## Participants +- Denis Lelic +- Emmanuel Arthur +- George Pro +- Tyler Wright +- Zach Horn + +## Meeting Notes +### Discussion on website design elements improvements +- Graphics on the [website](https://akash.network/) were identified as needing a facelift. +- Denis specified some specific graphic requiring significant improvement. +- Denis suggested the possibility of dividing groups into graphics or avoiding logos and using names for clarity. +- Denis mentioned the hero images on GitHub and referred to a list provided by Tyler. +- Denis expressed his intent to work on the hero images and hoped for community assistance but was willing to handle it on his own. +- Denis mentioned plans to update all illustrations for the GPU with a specific style. +### Discussions on design style and its elements. +- Denis explained the design's elements, such as handwritten illustrations for a human touch and geometric elements for the technical aspect. +- Zach Horn expressed approval of the design, highlighting its appeal to everyone. +- Denis Lelic clarified that the design is a website markup and stressed the importance of a unique, on-brand style. +- Denis mentioned the value of these elements in providing a unique illustration experience for Akash. +- Denis referred to their previous use of this style during the GPU campaign. +- Zach Horn praised the design for being both unique and familiar, as well as clean and lightweight. +- Denis confirmed that the design maintains the desired lightness and simplicity while giving Akash a distinct identity. +- Tyler Suggested that Denis identify "low hanging fruit" design tasks that can be tagged as "design and bounty" in the community issues to make it easier for the community to contribute. +### HACKATHON graphic and related promotional content +- Denis Lelic mentioned adding the HACKATHON graphic to the action items. +- Zach Horn noted the upcoming launch on Monday and the need for a tweet summarizing the tracks with good engagement. +- Zach discussed an email blast scheduled for Friday and suggested repurposing the original social media graphic. +- Zach Emphasized the importance of incorporating the tracks into the tweet and reusing existing content. +- Tyler reminded everyone that there's still time for individuals to register for the HACKATHON, which begins next week. +### GPU landing page design +- Arthur inquired about the readiness of the GPU landing page design for development. +- Denis explained that the GPU landing page design was pending final feedback and would be hosted in the Overclock Github repository, not as part of Akash Network. +- Tyler clarified that the GPU landing page was an Overclock Labs effort with a bounty for development and would be a collaborative project between the community and the Core Team. +- Denis assured that he would provide more information on the project, and Arthur could start working on it soon. +### Other Matters Discuss +- Denis brought up Adam's point regarding the Massari video and suggested Robert, who has experience with video editing, could assist. +- Denis suggested the possibility of handling the video internally due to its content and requirements. +- Tyler mentioned a migration plan for the Akash documentation 2.0. +- Tyler shared the plan for allowing the community to review new docs 2.0 in a live state over the next couple of weeks. +- Tyler explained the intention to take the new documentation live after Mainnet. +#### Akash Participation in EthSafari +- Tyler asked if there were any specific resources or assets required from SIG Design to support Akash's representation at EthSafari. +- George stated that he was still in the preparation process and would determine their needs and share them with Denis as time went on. +- Tyler emphasized the importance of communication with SIG Design to obtain the necessary brand assets and materials for the event. +- George discussed the possibility of sponsorship and the organizers providing design materials as part of the package. +- Denis offered his availability and willingness to provide any required assets for the booth or video presentation at EthSafari. +## Action Items +- Denis to provide additional information about the GPU landing page design. +- Zack to Repurpose the original social media graphic for an email blast. +- George to share Ethsafari design requirements with Denis. + +# **Transcript** + +_This editable transcript was computer generated and might contain errors. People can also change the text after it was created._ + +Tyler Wright: Glad you're the boss. + +Denis Lelic: Hey everybody, and welcome to today's SIG Design Meeting. there are a couple of things would like to discuss, and I'll just get started with + +Denis Lelic: The first one. Yesterday, I had a look me and Tyler were just talking about. What exactly could we discuss? So I had a look Of the pending stuff and try to find. Where could we improve? Anything design related. So, I went through the website and they're like these graphics. That. Could use a facelift. Something like we did for the presentation for audio boss. Greg and so on So, there's one. This one, definitely you need some work. + +Denis Lelic: and I'm not really sure how to fix this system since there's so much information going on, but there's a possibility of dividing these groups into graphics or just avoiding logos and just providing names and stuff like that. So that will be one thing. The other thing would be. + +Denis Lelic: these hero images. On Github. I know there's a list. Tyler, you've sent me. I've saved it. Just hadn't had time to put the work in. I was hoping someone will be here from the community side to. So I get push that to them, but doesn't matter, I'll take care of it. And I wanted to talk about. Also the thing Adam brought up, Which is the massari video. I'm not really sure if he shared this thing with the community. but I think Robert might help since he has some + +Denis Lelic: I just forgot the Experience with video editing and stuff. He already did for a cash. Yeah, but as I said, if there are no takers, I'll take care of it. And Maybe it's even easier for us to take this thing internally and just because of the content and everything that goes, Into a video. + +Denis Lelic: The the illustrations we did with it for the GPU. I was actually planning to update. All the illustrations with. That kind of style. + +Zach Horn: That sounds great. I really like that design and I think everybody did. So yeah that's great. Wear these going? + +Denis Lelic: This is just a markup for the website. So, I think I talked to Tyler a couple of days ago, and + +Denis Lelic: At least for my perspective. It's great to have some unique on brand style for And the argument here would be like we have this. + +Denis Lelic: A handwritten illustrations which are kind of like bringing that human touch and then we have this geometric elements that bring in the tax side of it. And + +Denis Lelic: I guess they provide some unique. + +Denis Lelic: Illustration experience for a cash. And I think where we were missing that I know we kind of inherit that style but I'm glad we + +Denis Lelic: took that approach during the GPU campaign and kind of experiment to see what could be done with it, how to elevate that style. And we'll just give it a try and see how it works on the website and on the other materials, + +Zach Horn: Yeah, I really like it because It is unique. there are other design styles that I see out there that are similar. But there's nothing that's exactly the same. So it is like it in a way, but it's also kind of familiar and legible and all that and it's clean and lightweight too, which that's + +00:05:00 + +Denis Lelic: Yeah, I know, Greg requested having this lightness and Simplicity around these illustrations. So I think we kind of kept that. + +Denis Lelic: But we made it a bit. Our own meaning Akash, owns them. + +Denis Lelic: So that's about it. So we covered Github Hero, images, ugly charts on the website. + +Denis Lelic: Massari video and these illustrations, that will be everything. + +Denis Lelic: I came up with what I could remember off. Of course there's the website stuff we're going to talk about that tomorrow in detail. there's also, + +Denis Lelic: Website related and that is a docs documentation. And I still own some feedback on that thing and it's kind of like overlapping the design and the website meetings and the Akash meeting. So yeah, I heard something but I don't see a hand. + +Tyler Wright: So Eris may, I won't let you finish. + +Denis Lelic: Yeah, go ahead. + +Tyler Wright: In terms of the doc think there's going to be a migration, we're working through the migration of Hugo over. So that again folks from the insider and buying guys community can start going through the new docs 2.0 and a live state. So I'll be sharing that with folks over next a couple weeks and then folks can give their inputs again before we take The idea is to take it live sometime After Mainnet. So when there's a little bit of a low so that we have time to update any blogs, any other collateral that might have links to old documentation, they'll have links to the new documentation page. So I'll give that a good sorted, some time after main, Upgrade + +Tyler Wright: Yeah, as mentioned, there will be a working group session tomorrow around the website where there'll be some folks talking about website changes. I know that there have been some bounties out there. Again, if anybody wants to look at the bounties around the website, please look in the website repo under the issues. Think to that point, I know that Adam has talked about Wozni and sick community and a head of community overclock. But in state community has talked about some bounties + +Tyler Wright: Video assets and some other items. I think Denis talked about that at the start of the call, but I think it might be a great dentist that there's any low hanging fruit of items that you want to get designed. You don't have the bandwidth to do. I think we should start putting those items in the community issues and we can start tagging them as think, design and bounty. And I know that There's a set aside for this kind of stuff, So I think we should start using it so we can start pointing people at direction in sync design without you having to say it in the meetings, here are some things that folks can design if they want to and see if it get me biters that way. + +Denis Lelic: Yeah, I agree. There's a mar. he made himself a bit available. the DID graphics for a caution. I think he still does those. Akashian videos. So I was planning to talk to him regarding these graphics. It's an easy task. So, It's not going to take much time resources and so on. + +Denis Lelic: anything else? + +Tyler Wright: I see George and Art and Arthur on the call. + +Tyler Wright: I hope I'm not speaking too soon, but I believe that George put in and a proposal to Akash insiders, to go to eat Safari and I believed that proposal has been approved. And so in preparation for that event, are there any resources that you all need from big design or anything that you need from SIG design, George in terms of assets, when going to East Safari to represent a cash, + +00:10:00 + +Tyler Wright: George, you might be on mute. + +George Pro: Yeah, yeah, thank you we are going to developer. I was still in the preparation process, so As time goes on, I'll be able to kind of get the whole idea about the things. then I will share it with Denis. + +Tyler Wright: Okay, and we want to make sure that you have a merchant stuff right prior to the event. So you have stuff to wear and hand out while you're there. Okay. + +Tyler Wright: That's the only thing I had,… + +George Pro: All right, Thank you very much. + +Tyler Wright: Yes, no, yeah. please let folks know and… + +George Pro: Thank you. + +Tyler Wright: sick design what you need so we can Make sure you have the right brand assets. And again anything that you need to represent a cost that eats the car. + +Denis Lelic: Yeah, good call y So, as Tyler mentioned, I'm here available, just let me know what kind of assets you need Even if we're planning a booth or a video presentation. Just let me know. + +George Pro: Yeah. Yeah. we are planning of a boot or something. I spoke with Adam. So you're going to kind of have a boot where we are going to presentation over there, but I don't know whether the Organizers are going to do the design for the boot or you have to bring our own design because I don't said it's going to be some kind of sponsorship. So I think a designs and those ones are part of the blue, the amount we are going to pay you're going to give out their boot what we have to do, to send the design to the organizers and then they are going to do the banners and everything themselves. That fair idea how about the whole thing. + +Tyler Wright: Excellent. Yeah. + +Denis Lelic: Sounds good. + +Tyler Wright: So When you get that any assets any documentation from each safari, just throw that in sync design. So that, if sizing needs to be adjusted for any assets, we can make sure that we're optimizing for that. that'll take Denis or another member of the community just a few seconds to make sure everything is size properly and high quality. + +George Pro: Sure, sure. + +Denis Lelic: Thanks, thanks. Tyler George. If you guys have anything to add to these five points or I guess four points, please do so. + +Denis Lelic: This was pretty much everything from them from my side. I'm sure we'll talk offline and async so, If you have anything, just let me know and I'll add it to this. These are kind of like, actually my Action items for the next week. After we finish some of the website stuff that's been going on. + +Denis Lelic: Yeah, that's it for my site. + +Tyler Wright: Thank you, Denis. I have nothing else to add again. + +Denis Lelic: Our. + +Tyler Wright: We'll have to working group around the cash website. Tomorrow, there's some lively discussions in Github discussions, and then there's a proposal, Up for vote happening right now. Additionally, I believe there's a SIG analytics happening tomorrow. So just a couple of things on the calendar over the next couple of days. + +Denis Lelic: One more thing, I forgot Zach you've mentioned the HACKATHON graphic. I might add that to the action item as well. + +Zach Horn: That would be great if you have the bandwidth. I guess we're launching on Monday. I'm thinking at this point that it'd be good to do at least one tweet that goes over the tracks the engagement on all the tweets has been pretty good so far. So if we can do one tweet that has the tracks on it maybe in a graphic and then we have an email blast going on on Friday, as well. Can probably just repurpose the original social graphic. But if you have any thoughts on that, those are the two big touch points at this point,… + +00:15:00 + +Tyler Wright: Yourself. + +Zach Horn: one more tweet and then the email blast and then maybe we'll do something on Monday when it launches. + +Denis Lelic: And the content can be reused from the existing graphic. + +Zach Horn: I would say So yeah I don't think we need to reinvent the wheel on this one. Just I think the big thing is just having the tracks on there. + +Denis Lelic: Got it. + +Tyler Wright: Zach Gray call out about Just another reminder that folks still have time to Register for the HACKATHON and participate over the I think month starting next week. + +Zach Horn: Yeah. + +Denis Lelic: I think George is already a part of it. I know he was. There. And since the beginning, + +Denis Lelic: And Arthur. If you have time and bandwidth, you're welcome to join. + +Denis Lelic: so, we might Wrap up early today. + +Emmanuel Arthur: Hey, hey Denis actually is the GPU landing page design. Ready for development. + +Denis Lelic: yeah, I'm actually waiting for final feedback. There was some additional information from the core team. Which led us to design a Completely new page and it's not going to be part of the existing network. Which means also it's going to be part of another repo. And it's going to be in the Overclock Github repo. If I'm not mistake Tyler, you probably have more information on that side. + +Tyler Wright: No, that is correct. So this is actually not an akash network. This is an overclock labs effort, that'll have a bounty behind it, Arthur to develop again and demand page for Overclock Labs. So we're just again, leveraging, some of the community at Overclock Labs of Core Team to build a page of live in the overclock repo, for a new site where the demand page will be held and hosted. + +Emmanuel Arthur: Arthur Alexander Information. + +Denis Lelic: As soon as I have more information,… + +Tyler Wright: Okay. + +Denis Lelic: It's probably going to happen today. I'll ping Chang and the rest of the guys if they have any additional changes issues. And so on, if not I'll provide you the drawings and you can start working on it. + +Denis Lelic: Yeah, but good call Arthur. It's actually not part of Akash as Tyler mentioned. But yeah, we still have to do it anyway. + +Denis Lelic: So, Thanks everyone for joining today, don't forget the meeting for a cash website, which is happening tomorrow. And I'll see you there. + +Tyler Wright: Thank you, Denis. + +Meeting ended after 00:19:07 👋 diff --git a/sig-design/meetings/010-2023-10-11.md b/sig-design/meetings/010-2023-10-11.md new file mode 100644 index 00000000..649414ef --- /dev/null +++ b/sig-design/meetings/010-2023-10-11.md @@ -0,0 +1,175 @@ + +# Akash Network - Design Special Interest Group (SIG) - Meeting #10 + + +## Agenda + +- Previous initiatives brought up by community members +- High-level overview of initiatives and past accomplishments +- Inviting community members to revive initiatives and draft proposals +- Updates on the Akash website +- Discussion on design assets and mascot +- Support for content creation and long-term content ideas +- Open discussion and sharing of ideas +- Presentation of a prototype for a mature Akash Console +- Feedback and suggestions on the prototype + + +## Meeting details + +- Date: October 12, 2023 +- Time: 08:00 AM PT (Pacific Time) +- [Recording](https://lpgpnhvzo3h4wr6vc7qy5rggghi2qztpqj6krjuzlevcmcypf63q.arweave.net/W8z2nrl2z8tH1RfhjsTGMdGoZm-CfKimmVkqJgsPL7c) +- [Transcript](#transcript) + + +## Participants + +- Denis Lelic +- Tyler Wright +- Zach Horn + + +## Notes + +- Tyler talked about wg-akash-website and gave a recap of all of the work that Piyush and his team have been working on. +- Denis and Zach talked about some videos that are being made for how to deploy on Akash Console and Cloudmos. +- Denis and Zach have been working on videos for Automatic1111 and other AI models deployed on Akash Console and Cloudmos. +- Youtube videos will be embedded on the website. +- Overclock going to make a decision about how to display Console and Cloudmos for the Getting Started page. + +## Action Items + +- Zach will upload videos to Youtube. +- Zach will provide copy. +- Denis to work on Github images. + + +# **Transcript** + +_This editable transcript was computer generated and might contain errors. People can also change the text after it was created._ + +Tyler Wright: All… + +Zach Horn: All right. + +Tyler Wright: Welcome to Stick design monthly meeting number 10. During these design, special interest group meetings. The group talks about everything related to + +Tyler Wright: visual communications and just general communications on the akash network. This is a place where anybody that wants to contribute to developing content, potentially blogs, animations, graphic design. Again, anything design related or communications related, this is the group that's open to the public meets monthly. On Wednesdays there's a calendar invite that everybody can sign up for as well. As again the discord events are available to all inside discord and you can feel free to Add yourself as one to be notified about the SIG design. + +Tyler Wright: One of the working groups of the SIG design is monitoring. It's a working group for their cash website. There was a proposal that was accepted. I believe a little bit under a month ago for website, revamp to have an open source website. That's accomplishes all the things that folks in the sick, design, one from early, touch points for all those that are trying to interact with the cost network, I know a number of folks, whether it be through social media efforts of Zach, or just general awareness land on the Akash network websites. And again, being able to point people in the right direction, if they want to be contributor, or if they're a user, want to understand. What next steps. A website, revamp it will improve the communication and improve the design and ux, as well as again, allow for more open source contributions. + +Tyler Wright: Folks, like Denis and Zach have been leading efforts with Piyush and his team that have accepted the work to do The working group for the website to meet every Against the next meeting is Thursday. At 6:30 am Pacific time. So if anybody wants to support with anything relates to website again there's videos going on the website of fair amount of design or happening in Figma and elsewhere. Again Zach has been hands-on with Developing Copy on all the various pages. If anybody wants to contribute, you can feel good to the website, specifically feel free to join that working group session. But again, there's a number of other things happening in stick design. + +Tyler Wright: most recently, there's been a number of events that the Akash network has participated in that have called upon SIG design to deliver graphics for T-shirts graphics for + +Tyler Wright: Stickers graphics for banners that have gone in the back of displays at some of these events. shout out to Denis and other members of the team that have been leading those efforts. So again, there's been a fair amount of work that's been coming out of SIG design. There is a shop for folks that want to wear and show off their cost network, love the apparel and other products, believe the link for that is shop data cost.network. And again, it's being added to the footer, the website. So if you want to contribute to developing new swag or if you just want to get your own swag again, I think that's swag is being sold at cost, just for folks, to be able to have it, where it show it off and increase awareness. + +Tyler Wright: With that, I'll hand it over to Dennis, to see if there's anything else he wants to cover outside of a quick recap of again, all the things that SIG design has been covering and overseas as a SIG. + +Denis Lelic: Here, thanks, you pretty much cover, everything except the videos. We got a couple of video tutorials in the making me and Zach were working on automatic 1111 where screen recorded his deployment of the Sdxl, if I'm not mistaken and we got that. + +Denis Lelic: Almost ready. It's 90%. Ready? We used aivate voiceover for the tutorial because Democus doesn't speak English. I believe. + +Denis Lelic: Another one in the making is this one was done for console and we have another one in the making for cloudmose. + +00:05:00 + +Denis Lelic: I think that's it. Zach, you do have any input for the videos because you were part of it. + +Zach Horn: Yeah. the one video we were working on is pretty close to done. I think the only thing it needs at this point is maybe a little bit more like filler copy just to fill in some of the gaps but otherwise I think it's just about there so that's on me to get you that copy Denis and then I guess we can throw that into 11 labs and finish it up just on that note we want to produce more of an intro outside of what you already have? Where are you thinking? We'll just do a simple interest and simple outro just clean up the audio and that ship it. + +Denis Lelic: Yeah, for the first one, I would keep it simple. And later on,… + +Zach Horn: Yeah. + +Denis Lelic: when we add new stuff, we can play around with it and it's for sure, gonna get better and so on. So I would three three the treat these as an MVP video. + +Zach Horn: Yeah, makes sense. And these are gonna live on the website, And that section, we were looking at on the deploy page. + +Denis Lelic: I would actually have them on YouTube Akash network channel. And we can just link there. + +Zach Horn: Got it. Are they gonna be embedded? Or is it just gonna be like a link? + +Denis Lelic: We can about embed them or provide the link, not really sure what works better. Yes. I Okay. + +Tyler Wright: I vote in bed, if we can't. + +Zach Horn: I thought that as well. Yeah. + +Tyler Wright: I do think that they should live on YouTube and that should be where the source lives, but for the sake of website, I think we should look to have some more videos that are again hosted on YouTube that are embedded on the site. + +Denis Lelic: Okay. Yeah,… + +Zach Horn: Sounds good. + +Denis Lelic: I know. Arthur made a PR for this. product page where we present power modes and console, and I can just add Actually one sec. + +Denis Lelic: Previously, we had the capacity and the space to embed and now we're having two of those products on one page and are not really sure where to put I'll just show my screen so you know what I'm talking about? + +Denis Lelic: So previously we had Two pages, one for cloud models, and we had much more space to Whatever we wanted. And now we have one page where we present both of these products. And I'm not really sure if we can embed in this area here. + +Tyler Wright: Got you? Maybe this is something that we could talk about as an Overclock Labs, internal team and… + +Denis Lelic: Yeah. + +Tyler Wright: then we can make a decision there. + +Tyler Wright: Yeah, I'll just leave it at that for now. + +Denis Lelic: Okay, So when we make the decision I'm just gonna let Arthur know about it and I mean, it's embedded so it's quite probably easy to implement. + +Denis Lelic: Okay Yeah. Did we cover everything for this page and the videos or do you want to add something else? + +Zach Horn: I think that's it for these. + +Denis Lelic: Okay, so, Zach, whenever you're ready, just let me know and I'll add The additional voice over you mentioned and Then we can publish it. I'm not really sure who's taking care of the YouTube channel. + +Zach Horn: That's me, so it's not just give me the file and… + +Denis Lelic: okay. + +Zach Horn: I'll get it uploaded. + +Denis Lelic: Okay Yeah, that's it. Regarding the videos. there are a couple of minor things happening, + +Denis Lelic: Github images, I know you've requested this couple of times, and every time I start working on it, something else pops in. But I got them almost ready. So hopefully, today tomorrow you'll get them. + +Denis Lelic: So we can update the Github pages. + +Tyler Wright: No rush. And yeah, if tomorrow is fine, tomorrow's time. + +Denis Lelic: Okay, cool. + +00:10:00 + +Denis Lelic: That's about it. I think for this week, father, Tyler, you are I can fight The right word cohesive is that You mentioned pretty much everything. So, + +Denis Lelic: Just haven't quit quick. + +Tyler Wright: I'll take it. + +Denis Lelic: Look if we missed anything going through notes, but I think we could cover pretty much everything. So cool. + +Tyler Wright: Cool. + +Denis Lelic: We can wrap it up for today. A bit shorter meeting? No community participation. So yeah, we'll talk in the next one. and tomorrow, of course during the working group for the Akash website, Brandon Others. Join fish. George Arthur and so on. + +Tyler Wright: Perfect. Yeah, I think Robert's traveling. I think so. A lot of people are just moving around. So it's a little bit hectic this week, but I'm trying to get more people from the general community that want to contribute. So, All right. We'll figure it over time but much appreciate you both. I'll follow up with notes, the transcripts of the recording shortly. But again, if anybody wants to join the working group around the website, feel free to join tomorrow or feel free to reach out between meetings on specific things that you would like to add to stick design. Whether it be again, drawings, animations, videos, etc, There are bounties available to those, that want to support creating content that further creates awareness around the Akash network and… + +Denis Lelic: + +Tyler Wright: makes it easier for people to use it. So, Yeah, reach out to Zach myself or Denis if you have any more questions about potential bounties but again everyone have a great rest of the day and we'll certainly talk between meetings online. Thank you both. + +Denis Lelic: Thank you time. It's like, bye-bye. + +Tyler Wright: Thank you both. + +Zach Horn: Thanks guys. Thank you. + +Meeting ended after 00:12:11 👋 + + + + + diff --git a/sig-design/meetings/011-2023-11-08.md b/sig-design/meetings/011-2023-11-08.md new file mode 100644 index 00000000..0d870697 --- /dev/null +++ b/sig-design/meetings/011-2023-11-08.md @@ -0,0 +1,424 @@ +# Akash Network - Design Special Interest Group (SIG) - Meeting #11 +## Agenda +- Video Tutorials for Onboarding +- Swag and Merchandise +- Marketing Assets +## Meeting details +- Date: Nov 08, 2023 +- Time: 08:00 AM PT (Pacific Time) +- [Recording](https://mctlnmdevhysanes52tbok6kbc3mgbsgnn6qemc35xhanfc2x67q.arweave.net/YKa2sGSp8SA0ku6mFyvKCLbDBkZrfQIwW-3OBpRav78) +- [Transcript](#transcript) +## Participants +- Benjamin B +- Denis Lelic +- Emmanuel Arthur +- George Pro +- Max +- Robert Del Rey +- Taiwo Omoyeni +- Tyler Wright +- Zach Horn +- Zeke E +## Meetings Notes +#### Denis Lelic +- Emphasized the importance of ensuring video content stays relevant. +- Personal project to create tutorials, including basics like setting up a wallet for Kepler, Leap, purchasing AKT, and an intro for Cloudmos deployment. +- Plans to integrate video content into the website (going live in 3-4 weeks) by adding it to docs or linking to YouTube. +- Open to hosting content on personal YouTube channel if not aligned with Akash Networks. +- Highlighted the need for video tutorials to onboard new users, covering deployment tools and the entire journey. +- Mentioned the longstanding discussion about Akash swag. +- Urged the team to take action on the swag pipeline. +- Encouraged the community to share ideas for Akash-themed t-shirts, sweaters, etc. +- Proposed dropping design ideas in Discord or discussing them in the current meeting. +- Piyush and his team actively working on the Akash website. +- Planned additions to the website include pages on network activity and pricing. +### Discussions on Video Tutorials +#### Zach Horn: +- Emphasized the importance of the video series idea, especially with Cloudmos as the primary deploy tool. +- Raised questions about the positioning of the series, suggesting options like a basic series or a more comprehensive guide. +- Explored the idea of a series consisting of five to ten short videos or a longer guide of 20 to 30 minutes. +- Initiated the discussion on structuring the content for optimal user experience. +#### Denis Lelic: +- Advocated for short videos, each lasting a couple of minutes, covering basic tasks like setting up a wallet, obtaining AKT, and connecting it to Cloudmos. +- Discussed the successful use of AI voiceovers in previous tutorials. +- Mentioned collaboration with Zach in creating tutorials and willingness to do so again, focusing on Cloudmos. +- Proposed using 11 labs to capture voices for specific team members. +#### Max: +- Supported the video series idea and suggested integrating short-form videos into the "Get Started" section. +- Highlighted previous work on Cardinal's "Get Started" section and the potential for collaboration. +- Acknowledged the recent release of new GPT functions for transcribing and commenting on videos. +### Swag Planning +- Tyler Shared the goal of sending care packages to Insiders and Vanguards win advance of events they plan to attend in 2024. +- Encouraged more ideas for swag designs and emphasized the need for timely distribution. +- Zack suggested creating a basic care package specifically for Insiders, including various swag items like shirts, keychains, and water bottles. +- Zack proposed making it a standard practice to send this care package to all current Insiders and Vanguards. +- Benjamin liked the idea and expressed interest in embroidered sweatshirts and sweatpants with the Akash logo. +- Advocated for basic items like logo-branded merchandise. +- Zeke highlighted the free marketing aspect of sending care packages, as recipients would likely wear the swag and generate visibility for Akash. +- Participants agree to share their swag ideas in the Discord channel. +### New Akash Swag Discussion( embroidered sweatshirts, sweatpants). +- Benjamn raised the idea of creating prototypes for Akash merch using his grandmother's sewing machine with an embroidery feature. +- Benjamin acknowledged being not the best at designing but willing to contribute by creating physical prototypes. +- Noted the possibility of creating merch at home for events. +- Deis encouraged Benjamin's idea of creating prototypes and supported the concept of utilizing the sewing machine for Akash swag. +- Tyler expressed enthusiasm for Benjamin's idea but raised concerns about optimizing Benjamin's time, suggesting a focus on SDL documentation. +- Tyler encouraged the sharing of references or ideas on Discord for the community to discuss. +- Discussed the creation of a board for public-facing marketing initiatives during the steering committee. +- Shared a link to the [marketing repo](https://github.com/akash-network/Marketing) and encouraged community members to use it for creating content, with assets available for use. +### Discussion on Printing and Merchandise: +- Tyler mentioned the use of a company called [Printful](https://www.printful.com/) for on-demand printing. +- Explained that Printful allows customization of various products without the need for managing inventory. +- Tyler emphasized that the store is intended as a marketing resource, with products sold at cost, and any extra funds contribute to the ecosystem. +- Zach inquired about setting up the shop to have multiple suppliers, potentially for limited runs on premium products. +- Tyler confirmed that multiple suppliers could be added to Shopify, and the main consideration is the fulfillment process. +- Group discussed the possibility of exploring a third-party fulfillment center for managing inventory and fulfilling orders manually. +### Improving Delivery Time: +- Benjamin raised a concern about the extended delivery time for merch, especially outside North America. +- Benjamin suggested exploring print-on-demand companies in Europe to improve delivery times for insiders and vanguards in that region. +- Tyler welcomed the idea and encouraged Benjamin to research European-based print-on-demand companies and provide feedback. +### Other matthers discussed +- Denis encouraged participants to drop ideas in the Discord channel for cool pieces to include in a care package. +- Invite community members to join website development meetings +- Provide feedback and insights on the Akash website +## Action Items +- Zach and Denis to collaborate offline on planning the content and structure of the video series. +- Group to explore using 11 labs to capture voices for AI voiceovers, potentially featuring team members' voices. +- Denis to share swag ideas in Discord for community input and discussion. +- Group to explore the possibility of creating a basic care package for Insiders with a range of swag items. +- Zach Horn and Tyler Wright to touch base offline to discuss the current provider for the Akash store. +- Benjamin to explore creating embroidery prototypes for Akash merch +- Benjamin to research print-on-demand companies in Europe and share findings via DMs +- Group call for design ideas for Akash swag to facilitate discussion and gather suggestions. +- Group to seek community input for content topics + +## Transcript + +_This editable transcript was computer generated and might contain errors. People can also change the text after it was created._ + +Denis Lelic: Hey everybody, and welcome to today's Sig design meeting. I see we have some new participants for welcome and thanks to everyone who joined today on the regulars of course and the new ones. + +Denis Lelic: a couple of things an items Maybe we check from our previous calls. Maybe just making sure they stay in the video content is something that's always on my list and I was just thinking +I'm gonna probably just have it as my personal project to set up a bunch of tutorials. for + +Denis Lelic: Basics just like setting up a wallet for Kepler leap where and how to purchase akt and maybe adding a short intro for cloud nodes the video for creating a first deployment. +So there's a whole journey of video tutorial tutorials. And that's something that's been on my list forever. And now when we have website + +Denis Lelic: going live probably in three to four weeks. I just like to add some of the video content either to dogs or link them to YouTube. I can even host them on my own YouTube channel if it's not aligned with a cash Networks. + +Denis Lelic: Content I don't know. So I just want to get it out there. I think we're kind of missing some of that stuff to onboard new users and basically just the deployment tools and yeah, like I said basically the whole journey + +Denis Lelic: It's also something that's been on our list forever. We've been talking about it, basically. From the beginning of these meetings and that would be swag stuff a car swag. I know Tyler is always. happy to talk about it and I think + +Denis Lelic: We have to do something about it. It's been in our pipeline for long long time and I would just like to see some of the new t-shirts. Sweaters, whatever you guys think would work. +So if there are any takers out there who want to design some t-shirts or whatever you guys think would help represent the cash and + +Denis Lelic: Akash Community feel free to drop your ideas in the Discord or you can of course discuss it now here as well. And last but not least. I'm just gonna mention the Akash website briefly. +We have a separate meeting happening tomorrow. And yeah Peterson his team are. working on the website + +Denis Lelic: We're provided some feedback on the UI stuff. And they're making sure to implement that and to implement some of the stuff Cloud models guys IC Max on this call. So thank you for +providing some help to pierce. And yeah, they're gonna prove they're gonna put up. + +Denis Lelic: Some pages around network activity pricing and they're going to pull that data from cloud nose, which is great. Yeah, anything else you guys want to discuss feel free to speak? + +Denis Lelic: I just covered briefly couple of items. I had on my list. So of course you can add yours. And these meetings are always up for discussion. Whatever the second guys think. We should need. +Please let me know I'm happy to discuss new ideas new things. So. + +Denis Lelic: Yeah Zach. + +Zach Horn: Let's touch base on your first point for a little bit because I think the video series idea is obviously something that we've needed forever. And now, +I know Max's on this call now that we're moving forward with Cloud most of the primary deploy tool. I think it'd be a great idea to do some videos that showcase the deployment workflow was specifically with Cloud modes. +how did you see that the series being positioned? Is it basic series, get A series with I don't know call it. Five to ten videos or so that go through all the different processes at separate videos or a full get started guy. +That's 20 or 30 minutes long what you think? + +00:05:00 + +Denis Lelic: I was thinking more like a short videos. just a couple of minutes long for signing up your wallet where to get akt how to get it and connecting your wallet in +Cloud mode and maybe creating your first deployment on just basically selecting one of the templates and that would be it for the first couple of videos basic stuff short. + +Denis Lelic: So yeah, I'm Max I see you have to leave and your hands up so. + +Max: Yeah, just a quick comment about the videos. I think it's an amazing idea and on Cardinals. I'm sure you saw it get started section that I did a couple of months ago. +My first idea intentions to where this could go was to actually include some short form videos to get started. So I think it would be amazing to plug these videos in this section. +So that new users can just follow along with the videos as well as the text to support. + +Denis Lelic: Yeah I mean me and Zach already created some of the tutorials and I think we could just do it again and + +Denis Lelic: just do it around cloudmose and yeah, we use the AI voiceover and it worked perfectly, so Yeah Zeke. + +Denis Lelic: Yeah agree. + +Denis Lelic: Sorry Max. I didn't get that the new GPT functions. + +Max: They released yesterday or the day before for transcribing and commenting on videos and stuff. But that's what you're raising. + +Denis Lelic: yeah, we actually use 11 labs. And it's really easy to use great product and you can also train your own voice. So If anyone's interested maybe later on we can. grab, +I don't know Max's voice for cloud nose or a Greg's Voice maybe Adam's voice. He has a radio voice. + +Zach Horn: it's surprising how well the 11 laps Voice works. it's really fluent. It gets the Cadence down almost perfectly. + +Denis Lelic: Yeah. It used to be awkward. But now I think it's for stuff like this for tutorials, it's great. + +Zach Horn: Yeah, definitely. + +Denis Lelic: Okay, Zach me and you can of course. Talk About it. If you have any ideas, let know. I scribbled some of the ideas I can share them with Of course. + +Denis Lelic: But yeah, I'll also share them in the Discord. and if anyone of course has any ideas drop them there, I'll make sure we discussed and tried and stuff like that. So. + +Zach Horn: Yeah, that sounds good. let's set face offline and we can get going on that. I'd be curious if Here on this call or elsewhere in the community has +things that they definitely want to see as part of the light get started process. I mean we can talk about them on this call or people can drop them in the chat or on Discord, +but definitely feel free to do that anybody. but otherwise, yeah, let's just touch base online and we can get going on some of the ones we know we want. + +Denis Lelic: cool Okay, the next item would be. swag Tyler you have any ideas + +00:10:00 + +Tyler Wright: No, I'd like the idea that Ben put in the chat about embroidery. I just would like if more people could throw ideas in the Sig design jet one thing that I want to +do a much better job of in 2024 is if individuals like insiders or other folks are going to specific events. Instead of getting them Swag six days before that event. +I just want to be as an example Max is going to be going to three events in 2024. I would like to send them a care package in January. So he has a bunch of product that he could take with +them and he's not waiting to the last minute. So that's something that I want to do a better job up and I want to rely on the Insiders. Even if it's not in Akash. + +Tyler Wright: Thanksgiving event, you're like any member here in this call is like hey, I have a free weekend. into the local then maybe wants to go to an event in his part of the world. +I would like for the Insiders to have product that they are proud of and excited to wear in a timely fashion. So that's again, we're not like pressing at the last minute people just have +the product and they're just rocking with pride. So, I don't know if I need more ideas. I know that the store link is now in the footer I believe and it's also If there's anything +I'm dropping the chat for folks if there's anything that you see in the store. + +Zach Horn: One thing that we could think about especially for the Insiders to your point on making sure that everyone's at how fitted is having a basic care package. +That's Insider specific that has a range of Swag stuff. So it's like you get a couple shirts you get whatever we want to do key chains water bottles, all that stuff, +but just like a predefined like pack that we can send out to current insiders. But also if anyone's the Insiders, they just automatically get this package, so they're +immediately outfitted and then we can top people up they need specific swag or we do limited run stuff or whatever. Yeah, Benjamin. + +Benjamin B: I like this idea. I also want to say for Tyler the thing he mentioned about the shop. I would like to see how to say the sweatpants as well. + +Tyler Wright: Got it. Yeah, you want embroidered sweatshirts and sweatpants with they're just hash mark on them ideally, right? + +Benjamin B: I think both of those ideas could be great. + +Tyler Wright: Okay. we're not talking about something like + +Tyler Wright: gpus are the new oil on our butt right? We're just talking about just basic stuff. That's just + +Zach Horn: Or Tyler don't rule that out. + +Benjamin B: Yeah, yeah, I agree with something the basic stuff like the logo or something else. + +Denis Lelic: people + +Zach Horn: Yeah. + +Tyler Wright: Absolutely. Go ahead Zeke. + +Zeke E: Yeah, I think another thing if you were to send insiders care package, I mean it's free marketing at the end of the day, because if I get a cost or I'm gonna wear all over the place and I'll have people ask me about it. So + +Tyler Wright: Absolutely. Absolutely. + +Zach Horn: Yeah, definitely agree. + +Denis Lelic: That could be a welcome package some of the companies use when they get new employees. + +Zach Horn: Totally. Yeah, I think that'd be a really nice thing. it's an extra perk for the Insiders, because I've had them as this whole process that he runs +people through and when they join but you finally get accepted and it's like you're an Insider now and you get this care package that all this cos swag that I think that'd be great. Yeah, Benjamin. + +Benjamin B: Yeah, this is a new topic. I just wanted to say that I wrote the message in the secret Design Channel on Discord. I'm not the best at designing things. +So I believe that someone else should be in place for that. But I would be able to create at least prototypes for how they would look in real life or maybe even +create merch if there is an event I could create some at home. with my Grandma's old sewing machine with an embroidery feature and bring them with me. + +Denis Lelic: Yeah, why not? + +Tyler Wright: I like the premise of that idea. I don't know if I want Benjamin who could be spending his time optimizing sdl documentation, but now he's with his +grandma and saw her with his grandma's sewing machine in China like making a cash logo, we can optimize that for you. But I love the idea of if you have any references +then you have to be a car. So if you see an article of clothing from another company, I really like this. I wish I had a version of that throw that in Discord and then +we can start to take these ideas and Denis can very quickly take the logo or the Mark or any of the marks and we can just Mark something up talk about it async and sync design and go from there. Go ahead then. + +00:15:00 + +Benjamin B: Yeah, I agree letting our company do everything with the printing but I just wanted to say that for prototypes and to see how something would look in real life. +I could create some prototypes. It wouldn't take that much time because the sewing machine has this feature it's a computer program that does it. And my family has wanted to try get it up and running again. So it would not be an issue for us. + +Tyler Wright: amazing on that topic while we're here and this will be filled out more but I think you all heard in steering committee. there's a board being created that's going to have a number of + +Tyler Wright: Public facing initiatives that are marketing Focus. So whether it be community and marketing folks. So whether it be like the edu program some of the swag stuff +as we start to develop some of these ideas we can throw them on the board and distract them during the steering committee on top of that. I just put a link to the marketing +repo inside the Akash Network organization. Basically how we want to use that is able to drop in issues if anybody wants to put an issue in there. And again, it'll automatically +be put on the marketing community board but more specifically if you see any assets, you can already see in that folder where Denis has already dropped in the logos the word +March the power by a cost where marks we can drop in more marketing assets. So then Benjamin to your point instead of having to design from scratch a + +Tyler Wright: Good you dropping in the embroidery program. You can literally just take the logo file and a PNG or in some other file format to just hopefully take it into your +system and then use it. So again, I just want to make that available to anybody if anybody's doing I know Robert in the past has used some of these assets for a lot of his videos. +But if anybody wants to create anything, whether it be merge videos other forms of content, feel free to use that marketing folder that marketing repo rather to find your assets. +And again, if there's anything that's missing we can make sure to get those assets added to that marketing repo in the Akash Network organization. + +Zach Horn: Hey Ty we can touch base on this offline, but who's our current? Provider for the store who does our merch? + +Tyler Wright: Are yeah, we talked. This is actually something we use a company called printful. They do on demand printing. + +Zach Horn: + +Tyler Wright: So basically we don't have to get a hundred units or… + +Zach Horn: right + +Tyler Wright: something. They have an entire store. I can drop it in here for folks. But any of the blanks in here we can customize and if anybody has any idea I really like this heavy sweatpant. +Then we can just talk about that again async and chat and then we can design a mock up and what the company does is somebody orders it they just print to order and they'll send that product out so we don't have to manage any inventory. + +Tyler Wright: And then one thing I'll just say for clarification sake and I guess that clarification shape because it should be blatantly obvious. The store is designed to be I think a Zeke said it perfectly a marketing resource, right? +We want people like the Insiders and vanguards to receive product that they want to buy any product on their own. They're feel free. If anybody from the community wants to buy any product. Feel free. We are Akash nor overclock is +looking to make a sent off of this is everything is at Cost all the extra dollars don't back into The ecosystem for whether it be for insiders or whatever. So again, all the product is sold as close to that cost as possible not +trying to be a retail business. Just want to make everyone aware that. + +Zach Horn: Is there a way to set up the shop such that we can have multiple suppliers. I know Drop Shipping is probably where we want to stay for now just to your point like ease of inventory management, +but let's say we wanted to do a limited run of something on a more premium. Supplier can we have both of those routes to the same store? Do we run into backend issues with that? + +00:20:00 + +Tyler Wright: No, no we can so basically the store is still up to Shopify. + +Zach Horn: but + +Tyler Wright: We can add any product that to your point Zach if we order 50 of a notebook we can have those 50 notebooks available and sell them to the store. The only issue comes in to we need to have to +have a third party fulfillment center that's going to fulfill the orders via Shopify or… + +Zach Horn: right + +Tyler Wright: somebody whether it be from the community or from the overclock Labs team is going to have to manage that inventory and then fulfill the orders manually that's only pick up. But again, it's still very doable. + +Zach Horn: Yeah might be worth pursuing what a 3pl Arrangement would look like I mean, maybe it's prohibitively expensive. Maybe it's not but might be worth it chatting that offline. + +Tyler Wright: Would love to hear just let me know. + +Tyler Wright: Go ahead. + +Benjamin B: I just wanted to say here that one thing we could improve upon as well is trying to have multiple different print of demand companies working so in the past when I +received some merch during Christmas from Adam and so on it took almost a month to get it. I don't think it was Christmas anymore. So if it would be possible to have instead of +only in North America, which I assume it was shipped from + +Tyler Wright: I think that's a great call out. If you see any printful or printify competitors, companies that do demand printing that a European base. I feel like maybe in the +past I've seen one. But if you see any please let me know. There was a company I found at some point and maybe it's printify or someone similar that basically has a number of +suppliers all over the world and depending on where you ship from or where you want to get the order shipped to rather. They will use a different manufacturer the problem with +that is the products could be vastly different, so a printer in North America might have black shirts, but they might be all sold out of black shirts in the European region. And so + +Tyler Wright: then you run into issues like that. But again Benjamin if you have the bandwidth and can help find maybe a demand printer in Europe. I would love to learn more +about it and see if they can support us because I know we have a number of insiders and vanguards in that region. + +Benjamin B: Yeah, I will research this and get back to you via DMs. + +Tyler Wright: Amazing. Yeah. + +Denis Lelic: Yeah, one thing I would like to encourage. robbers Arthur George benjamin-- Zeke + +Denis Lelic: if you have time just drop a couple of ideas and in the Discord channel, for example, what would be some cool pieces you would be happy about if you get it in a care package for example, or a welcome package. I'm just gonna like + +Denis Lelic: scratch a couple of them from the list t-shirt and a sweater. That's something like which is always around so maybe something beyond that. I'll leave it up to you. So if anyone is interested, please drop it in the Discord. + +Benjamin B: Robert did sir, Tyler. Did you see what Robert's? wrote in the shop + +Tyler Wright: Yes. I'm actually looking at awkward Styles right now Look at their pricing plan. I'm also trying to better understand where they're shipping from. But yes, I am looking at it right now. Thank you. + +Denis Lelic: Yeah, I saw Robert also posting some gifts. yeah, why not? It's always a nice way to respond some sometimes on Twitter or Discord or slack just with a gift. So if you have anything cool anything funny? I'm always up for it. + +00:25:00 + +Denis Lelic: Okay, I'm happy that we have A longer discussion around swag it's usually one of the last items in our meetings. So it would be great as an action item to have just a short list of + +Denis Lelic: Items, which would be in the care package? + +Denis Lelic: Anything else you want to add to this topic? Otherwise, we could use some of the time to cover other stuff as well. + +Denis Lelic: Okay, cool. Maybe one last thing around. + +Denis Lelic: Swag Arthur and Have you received any of the swag stuff? And how did that when did you waited for a long time? I know you had some T-shirts, but I think you've created those on your own, right? + +Denis Lelic: I think George you created some of the t-shirts for one event. + +Denis Lelic: Okay, cool. Yeah, maybe that's one of the options as well like just providing brand assets for the + +Denis Lelic: for the printers and then we could maybe cover some of the costs that are. + +Denis Lelic: created for printing purposes Yeah time. + +Tyler Wright: Real quick. This is for the Insiders when you go join The Insider program, I believe Adam does this but Does he asking for your shirt size or your clothing size? I feel like he did at one point. +I just want to do Zeke. I feel like you are a newer Insider. Did you give your sizes for product? + +Zeke E: I don't remember if I did or not, but I haven't received anything if I did. + +Tyler Wright: Okay, we'll change that. Go ahead Ben. + +Benjamin B: I don't think kills this the first meeting, but then if you mentioned that you're interested in March some I believe it's reached out. two times outside of + +Tyler Wright: Yeah, I'll talk to Adam about that because they again to Zach's point in many others points. I think it would be great to get the Insiders at least like a starter package +of stuff that they feel comfortable like taking to events wearing around the neighborhood Etc. + +Denis Lelic: Yeah, I agree. Tyler you could hook up Zeke and Benjamin with some swag. + +Tyler Wright: For sure. We're gonna get them something soon. Yeah. + +Denis Lelic: cool + +Denis Lelic: Okay. + +Denis Lelic: I know website is always an important topic to discuss but We have one meeting happening tomorrow, which is dedicated only for that but if anyone. Wants to share anything +ask anything and he can't wait until tomorrow. Feel free to speak. + +Denis Lelic: Thanks Yeah, so I think we pretty much covered. All of the items I wanted personally. I wanted to talk about the videos and swag. + +Denis Lelic: So just looking through the old nodes. we had + +Denis Lelic: I see we had Talking about Swag and saying he will provide some of the ideas. Unfortunately, he's not here. but doesn't matter I think we can just start it off but a +simple item list for the package and I'll make sure we have that thing designed and I know Tyler will be around to help us produce that thing and would be great to have an ice package in new Insiders. + +00:30:00 + +Denis Lelic: Okay, cool, Zach you and I can talk about videos offline, of course, but if anyone else is interested in that topic, you can ping me on Discord and I know Robert you're always. +Interested in producing that kind of content. So just let me know. + +Denis Lelic: And we can talk in a separate call. Otherwise if that's everything for today we can wrap it up. + +Denis Lelic: Yeah type. + +Tyler Wright: Real quick. I know that Zach does a great job of sharing all the high level announcements related to Akash Network amongst many other things that he's doing +specifically type of funnel and across a number of different things presentation marketing. If has I know Zeke you get involved with the community if anybody here has any +topics that they maybe think would be good for content in terms of specific things that users are dealing with that could be a video a short form blog maybe something that can throw in. + +Tyler Wright: Email newsletter just keep that top of mind. I'm not saying there's a specific action item to anybody needs to do but certainly more support from the community +on some of these initiatives that again Zach can just really focus on editing and then optimizing his content would be great. So Again, I know the Zach does. s*** ton. +It's part of my English but Some Community Support on some of these things just like creating again short form videos on specific topics that might be beneficial to the community or might feature a feature being used would always be helpful. + +Zach Horn: Yeah, thanks That's the technical term right for my amount of workload. + +Tyler Wright: Exactly. That is the super technical place. + +Zach Horn: Yeah, I completely agree. I mean just for context for everyone on the call. We're working on a lot of stuff on the back end to essentially service top of funnel for cash. +So that's deployment things. It's a very technical deployments with AI mostly at the moment but to Tai's Point like if anybody here in the community has things they want to cover or they think should be pieces of content, +feel free to ping me on any channel or just throw it into one of the public Discord channels to discuss and definitely I will keep an eye on that because it's definitely an important part of our content strategy +at my attention goes a lot of different ways. So if there's anything that anyone feels like should be content. Just let me know. + +Denis Lelic: sounds good. + +Zach Horn: Or exactly that's right. + +Denis Lelic: Yeah as Robert would call you. + +Zach Horn: Yes, that's right. + +Denis Lelic: Okay, So thanks everyone for participating today. We'll talk in Discord and if your guy guys are available tomorrow, +you're welcome to join the meeting for working group Akash website and we'll have a Deeper better discussion and everything regarding the website. We just briefly touched it today. So you're welcome to join. + +Tyler Wright: Yes, please do join. + +Denis Lelic: you next month. + +Tyler Wright: Yeah, Please do join those website calls because we're getting down to the wire. I know that a number of people have been joining consistently, +but I just want more people from the community to see all the work that has been done by Peterson's team. But also by Zach working on content Denis working on design Robert, giving ideas. +So it's been really a community effort and as we get closer to picking this thing live, I just want to get more eyes on it, so feel free to join tell your friends trying to make it a +good time so that everybody from around the world can go but yeah, please feel free to join if you can. Thank you, Robert. + +00:35:00 + +Denis Lelic: Thank you type. bye guys + +Tyler Wright: All Have a great day. All right. + +Zach Horn: Thanks guys. + +Denis Lelic: Thank you. + +Meeting ended after 00:36:27 👋 diff --git a/sig-design/meetings/012-2023-12-13.md b/sig-design/meetings/012-2023-12-13.md new file mode 100644 index 00000000..ac518b93 --- /dev/null +++ b/sig-design/meetings/012-2023-12-13.md @@ -0,0 +1,480 @@ +# Akash Network - Design Special Interest Group (SIG) - Meeting #12 + +## Agenda +- Swag/Merchandise Concepts. +- Design style and elements. +- Landing page design. + +## Meeting details +- Date: Wednesday, December 13, 2023 +- Time: 08:00 AM PT (Pacific Time) +- [Recording](https://une76rieq3cvbtrnjv3gxaw6kbxaay3tnzqsangya2lfe6ionpva.arweave.net/o0n_RQSGxVDOLU12a4LeUG4AY3NuYSA02AaWUnkOa-o) +- [Transcript](#transcript) + +## Participants +- Denis Lelic +- George Pro +- Tyler Wright +- Zach Horn + +# Meeting Notes +### Introduction +- Tyler acknowledges Denis and the contributions of Robert and others to Merchandise Design Concepts in Discord. +- Hands over to Denis to commence the final Sig Design meeting of 2023. +- Denis recaps the year, highlighting the substantial focus on website redesign and expressing optimism for diversifying design efforts in the coming year. +- Emphasis on shifting attention to more video content, particularly short tutorials, with community members showing interest in contributing to video documentation. +- Denis envisions the creation of video content as a valuable way to communicate with the community, especially for those who prefer learning through videos. +- Encourages community members to get involved in transferring documentation into videos. + +### Swag Concepts +- Denis mentions the desire to explore new avenues and mentions creating Swag Concepts. +- Expresses gratitude to Robert for sharing ideas on Discord and encourages team and community members to share their favorites. +- Denis expresses gratitude for the ideas shared on Discord. +- Plans to gather feedback on the presented concepts from the community and team members at Overclock. +- Aims to move selected concepts to the Shopify store promptly for wider representation. +- Denis clarifies his perspective on presenting diverse designs, including funky and official styles. +- Expresses a preference for moving away from strictly corporate designs and introducing character and twists while maintaining Akash's brand identity. +- Denis invites interest and feedback from the community and team members on the diverse swag concepts. +- Denis introduces the idea of a monogram of letters, expressing a personal preference for this design. +- Denis concludes the presentation, seeking opinions and favorites from the community for these end-of-year swag concepts. +- Denis expresses the desire to offer a variety of options for different occasions, from clean corporate styles to more creative and flexible designs. +- Zach proposes the idea of having a staple set of corporate-style merchandise always available, with occasional rotations of more creative and limited-edition designs to keep the merch store interesting. +- Denis agrees with the idea of providing a variety of options for different occasions and mentions the potential for team members to wear different swag for a confident and diverse look. + +### Group Feedback on Swag Concepts +- Zach expresses enthusiasm for the diverse designs, appreciating the variety and the flexibility of the brand representation. +- Zach particularly likes the design with the speed element and inquires about the one with the little four-point star. +- Denis identifies the star design and confirms it's towards the beginning. +- Robert also appreciates the designs, expressing interest in the retro ones. +- Zach asks about the timeline for releasing the merchandise, suggesting it's a good time to drop them in the next couple of weeks. +- Denis agrees, mentioning the plan to share all the concepts with the community for feedback before releasing them on Shopify. +- Denis emphasizes the intention to provide a variety of options for the community to choose from. +- Zach supports the idea of experimenting with designs and seeing what resonates, especially considering the current prevalence of corporate designs. +- Denis highlights his research on how established brands experiment with graphics while retaining brand recognition. +- The discussion touches on the retro trend and its potential appeal in conveying a sense of longevity for the brand. + +### Robert's Feedback +- Robert expresses love for the retro vibe in the designs and notes the trendiness of retro aesthetics a few months ago. +- He sees the retro style as fitting for Akash, associating it with the project's longstanding success and trustworthiness as an OG project. +- Robert ponders on the possible connection between the retro trend, synthwave music, and the appeal of being crypto-native. +- He appreciates the freshness of the designs and concludes by expressing his approval. +- Denis mentions his research among other web3 projects, highlighting the decision to go beyond simple logo placement and striving for more diverse and appealing swag. +- Denis expresses anticipation for community feedback to shape the final selection of designs. + +### Discussions on Logistics and Quality +- Zach raises the question of pursuing embroidered merch, noting the interest from the community, even if it involves increased costs and logistics. +- Tyler provides insights, mentioning the search for a new merch store with a focus on a partner that supports print on demand. He notes that the current partner being considered is printful. +- Tyler confirms that the potential new merch store, Printful, does offer embroidered options. +- Tyler suggests adding custom embroidered patches and incorporating embroidered elements like the Akash logo and wordmark to enhance the quality of the merchandise. +- Zach acknowledges the plan and expresses agreement. + +### Discussion on Video Content Plans +- Denis mentions the previous discussion on video content but suggests waiting due to the ongoing Cloud rebranding process and upcoming UI refinements. +- Denis expresses readiness to create deployment videos, product demos, and similar content after the initial wave of rebranding. +- Focus on merch is prioritized as it seems like a more immediate opportunity, especially with the end-of-year timing. +- Zach acknowledges the timing for merch, especially with the holidays approaching. +- Denis teases Zach with a special price for the speed design, to which Zach responds positively. +- Zach shares ongoing discussions with Thompson about creating the first set of videos. +- Uncertainty about whether to wait for more finalized docs or proceed with different tutorial-style videos unrelated to the docs. +- Emphasis on the need for more video content to balance the text-heavy nature of the current documentation. +- Zach notes that Tom might be the first solid contributor for video content. +- Denis inquires about the type of videos Tom plans to produce, particularly regarding voiceovers. +- Zach mentions discussions about using 11 Labs for voiceovers to establish a consistent brand voice and make collaboration with multiple contributors more seamless. + +### Discussion on AI Voiceovers and Localization +- Zach highlights the advantages of using 11 Labs for voiceovers, including the ability to establish a consistent brand voice, collaborate with multiple contributors, and potentially localize content into different languages. +- Denis agrees with using 11 Labs for voiceovers, and both express satisfaction with the current quality of AI voiceovers. +- The conversation delves into the transformative capabilities of AI in voiceover, making it a much-improved experience compared to the past. +- Zach mentions the amusing feature of uploading an audio sample to mimic a specific voice, like having tutorials in someone else's voice. +- Denis playfully suggests the possibility of using famous voices like Morgan Freeman or David Attenborough for tutorials. +- Denis looks forward to focusing on content in the next year, especially with wrapping up the website and working on landing pages. +- The discussion implies a shift from comprehensive website review to targeted improvements, allowing the group to allocate resources more effectively. + +### Future Focus on Landing Pages +- Denis expresses excitement about having resources to tackle many different tasks in the coming year. +- Zach agrees, mentioning that landing pages have been on the marketing back burner for a while and sees them as a focus for the next year. +- Denis agrees to shift the attention of the working group towards landing pages as soon as the current tasks are completed. +- Denis mentions having some ideas and drafts for landing pages but is willing to wait and discuss the direction to take in the upcoming meetings. +- Zach anticipates using future meetings to finalize the current website. + +### Feedback and Incorporation of Designs +- Tyler recommends a specific format for sharing design feedback, suggesting that each design be numbered for easier reference. +- Tyler expresses the desire to discuss incorporating designs into the website and mentions the addition of embroidered items to the store. +- Links related to printful embroidery are shared in the chat. +- Tyler requests design files from Robert to discuss mock-ups and potential additions to the store. +- Robert acknowledges the feedback and mentions having the design files in Canva. +- Tyler encourages Robert to share the design files or mock-ups for discussion and suggests organizing them with numbers or letters for clarity. +- Robert agrees to share the files and confirms his understanding. + +### Licensing Concerns +- Denis raises concerns about the use of vector graphics and potential copyright issues. +- Robert clarifies that he uses Canva Pro and pays for a subscription to access assets marked with the pro sign. +- Denis suggests verifying the license to ensure it allows for reselling the assets on Shopify. +- Robert acknowledges the concern and commits to finding out the details about the licensing. + +##### Discussion Wrap-up and Future Plans +- Zach mentions that there's nothing super pressing on his plate, mostly focusing on website-related tasks. +- Zach looks forward to 2024 and mentions the anticipation of having merch in the store for social media exposure. +- Denis plans to take some time off next week but will be available during the Christmas holidays and New Year. +- The team expresses availability and commitment to asynchronous communication during the holiday period. +- The meeting is wrapped up, and Tyler expresses appreciation. + +## Action Items +- Denis and Robert to review the Canva design files shared by Robert to ensure licensing allows for reselling the assets on Shopify. +- Zach and Thompson to discuss the approach to creating video content for website and docs, considering voiceovers and brand consistency. +- Robert to share design files and mock-ups for his merchandise. +- Denis to share merchandise design with community for feedback. +- Tyler to coordinate with Denis to add embroidered items (hoodie and t-shirt) to the Shopify store. + +# **Transcript** + +_This editable transcript was computer generated and might contain errors. People can also change the text after it was created._ + +Tyler Wright: All right, welcome everybody to the design special interest group monthly meeting number 12. During the Sig design monthly meeting the group goes over anything that's related to Visual Communications. Whether it be video graphic design swag. I've been promotion marketing materials anything Visual and sometimes even high-end marketing assets that have a little bit of copy and that's why we have the copy both Zach that always joins these calls as well. But anything that's really focused around visual communication of Akash. + +Tyler Wright: On the Akash brand is discussed during these monthly meetings. The Sig design Discord is also very active where people throw in ideas for various items that are swag related or event related or again, if anybody's doing an in-person event and their local area and it needs design assets the folks at a park at the part of this sig Design Group come together to help deliver the assets that it might need whether it be against swag or event materials. So again, there's usually a great deal of participation from folks with these calls being led by Denis. + +Tyler Wright: one of the other action items that came out of Sig design this past year was the working group for the Akash website, which had obviously many design elements on the front end and it on user experience design elements of how things kind of look and feel that working group produced a proposal that went on chain from a team called human HQ that took on the task of revamping the cash website since then that working group has been meeting on a weekly basis to design and migrate many of the assets from the old website to a redesigned much improved experience for an open. Source Akash Network website. + +Tyler Wright: That working group is in its final stages of reworking the website. And again, we'll be meeting tomorrow. But again, there's been a lot of work that's been going on around the website. You can see in the project board, which I'll share in the chat here right now. You can track progress with the revamped website and any other design assets that are in the pipeline. So again, if you are interested in any of those things, I'm going to share the community and marketing project board that gets discussed during the steering committee meetings. + +Tyler Wright: I know that Denis has some items that he wants to discuss and since the last meeting. I know that Robert and others have put some Design Concepts in Discord so much appreciate the efforts there, but I'll hand it over to Dennis to kick off the last sick design meeting of 2023. + +Denis Lelic: Thanks Tyler for covering pretty much the whole year quickly. last meeting happening this year. It's been a fun journey. I think what as you mentioned websites took the most of design resources this year, but moving into the next year. + +Denis Lelic: I have a good feeling now. We can focus on other stuff personally. I want to see more video content like shorts tutorials stuff like that. So we have new community members willing to help On the Dark Side meaning + +Denis Lelic: transferring some of the talks into videos and just Community communicating that touchpoint and in a different manner since people like to learn in a different way. Hopefully we're going to have some videos soon to cover that part, too. Yeah last meeting we talked about a bunch of stuff. + +Denis Lelic: on There's all always videos, but before we close this year. I just wanted to create some of Swag Concepts and share them with team members and community members to see if they have any favorites. I see Robert also dropped some of his ideas in Discord. So, thank you. + +00:05:00 + +Denis Lelic: yeah, we'll just grab these ideas and Concepts and share them and see what the community has to say team members from overclock have to say and we'll move some of them to the Shopify store as soon as possible. So everyone can. represent properly So yeah a couple of Concepts today. I wanted to show you guys one sec. + +Denis Lelic: Yeah, just to give some clarification. for my perspective. I wanted to present a variety of designs. Some are more funky some are more official but of course community members and team members and whoever have different tastes so + +Denis Lelic: my opinion was just like to move a little bit away from the corporate design and Do something a little bit more with a character with a Twist still? preserving Akash as a brand but communicating different characters, so + +Denis Lelic: Maybe we just have a look so. we got this illustration kind of like forming a bursting cloud with letters super cloud around so it's kind of like popping out and I think it would look good across a huge print across the back and + +Denis Lelic: that's something personally I would wear. so we got another one a little bit of a nod to Cosmos. So we have this kind of floating elements like a Galaxy and Akash, of course, all of these Graphics can be applied to different touch points t-shirts hoodies. + +Denis Lelic: Bags hats whatever. Then we have an illustrated Akash sign. Breaking out a little bit from the corporate side. And just providing a little bit of Illustrated details. Then we have something complete completely different and it's kind of related to Cloud. So we have these letters kind of bubbling. And yeah, this one is quite different from the rest of the stuff. We usually see but I feel then we have a cash erythro version of Akash something we can often see in VHS tapes and something like that. So + +Denis Lelic: Anyone interested or some? retro related stuff they can opt in for this one. + +Denis Lelic: Then we got some akt I had this idea for a while. I don't know maybe a year to do a monogram of letters again something I would wear. + +Denis Lelic: I hope I didn't do too much of the designs I would wear. but I guess it's the easiest way for designers to do something like do what you want to wear. But of course I concerned many tastes. So yeah, I get in different color. Maybe on a hat red hat. Then we have some. + +Denis Lelic: I don't know what to call it, but it's kind of like a mix of retro and Cosmos. then we have this. Akash sign but transformed in some sort of cloud a design. We already had in white, but I felt like we can just play around with it and add a little bit of Dimension to it. So the cloud feels a bit more real. And then again concept like the previous one the Bubby one where? + +00:10:00 + +Denis Lelic: We have a bigger sign which says Akash Network supercloud. Then we have this one. + +Denis Lelic: akt here on the shirt in a bigger size and a little bit of messaging around and all of these designs can be like We cannot adapt them To a certain touchpoint and we can also quickly change whatever it's written on it. Then we have a bursting Cloud distorting this typography. Which is forming this kind of like a warping effect. + +Denis Lelic: another one Triple A + +Denis Lelic: and we have the cloud in white version. And a little bit of formal corporate stuff Akash Network superclub the side could be applied to t-shirt or whatever. + +Denis Lelic: And then we have this one. 3D sign with some clouds floating around + +Denis Lelic: and again this was kind of like I was trying to clients for some of the lightness and the speed and the super cloud and try to just see how it looks I have feeling like I still have to work on it a little bit to capture that. + +Denis Lelic: the story of speed but yeah, I think for now it conveys the idea that needs a little bit more work. Yeah, so that's it for + +Denis Lelic: dropping some swag for the end of the year. What do you guys think? any favorites + +Zach Horn: You really? I love it's all over the place. But in a good way, I think mean. it's good to flex the brand a little bit and throw stuff out there. I like the one you're on now. I like the one I think is last the one with the speed element. Yeah. A lot. What was the one with the little four-point star in the corner? + +Denis Lelic: or point star + +Zach Horn: Yeah, it's a little tiny is towards the beginning. Yeah. + +Robert Del Rey: What the third or fourth the slide? + +Robert Del Rey: Before not that right? + +Zach Horn: I like that one a lot. They're all kind of retro in I mean. But I don't think that's a bad thing. it's interesting. I feel like a lot of this is up ties alley, too. What do you think that? + +Zach Horn: But no thoughts. + +Zach Horn: What are you thinking to drop these before the end of the year in the next couple weeks? + +Denis Lelic: yeah, I think it's the best time to drop some merch we can just shared all the concepts with the community to see… + +Zach Horn: Yeah. + +Denis Lelic: what are they thoughts but personally I would just try and… + +Zach Horn: Yeah. + +Denis Lelic: drop them in the Shopify and see what people would actually By prefer or whatever. I know we don't rely too much on people getting merch but I really tried + +Denis Lelic: to do a bunch of them that are still kind of like there's a variety of them so people can actually choose from but Yeah,… + +Zach Horn: Yeah. + +Denis Lelic: I would just try to see what happens. + +Zach Horn: totally I like that too. it's just throw stuff out there and see what resonates because I do agree. We have lots of very corporate designs. Currently. We kind of always have so It could be nice to throw some things at the wall and … + +Denis Lelic: Yeah, I mean I did a little bit of research… + +Zach Horn: what sticks. + +Denis Lelic: because I wanted to stay on the brand for example, Nike and all these different brands. They always experiment with Graphics, but they still use some of the brand aspects. + +00:15:00 + +Zach Horn: + +Denis Lelic: So not the users but potential buyers and buyers + +Denis Lelic: are still recognizing that that's the brand and regarding the Retro thing. + +Zach Horn: totally + +Denis Lelic: I don't know. I think maybe it was trending for a while. And I just tried to capture some of that. + +Denis Lelic: and for example,… + +Zach Horn: Yeah, definitely. + +Denis Lelic: it brings another aspect to the brand which is like hey, we've been around for a while + +Zach Horn: Yeah, yeah. + +Denis Lelic: we're from the Super cloud from the 80s. + +Denis Lelic: + +Zach Horn: It's funny. You just said the 80s and I was about to say 20 years ago. Which how often do you do that? Not 20 years ago 43 years ago or… + +Denis Lelic: Yeah. man Yeah,… + +Zach Horn: almost 44 years ago. That's crazy. + +Denis Lelic: when I say 80 is always think 20 years ago. done mention that again. + +Zach Horn: Yeah. + +Zach Horn: Really? + +Denis Lelic: Yeah, Robert, think sorry I saw Robert hands went up. + +Zach Horn: No, no. + +Denis Lelic: You wanted to say something. + +Robert Del Rey: Yes real quickly that I love the Retro bike that all these designs are given and what I wanted to say was in accordance to what we're just saying, it's not that retro was trendy but I do feel like it was brandy a few months ago same goes with synthwave music. I mean here into that listening to that a lot recently, but also I believe this is a Sign for a cash a success. Run for a while, right? It's an OG project. People can trust in the project more because of that. + +Robert Del Rey: so much man, but what I really wanted to say was + +Robert Del Rey: also, I don't know if there is a relation between synth wave retro nostalgic and being like crypto native or + +Robert Del Rey: Initially when you see how blocks used to look like a few years ago how web page used to look a few years ago. And when you come across a modern page that has that all feeling but it's modern you like that and at the same time you're kind of nostalgic on how things were in the old days. I don't know if that made sense at all. But I did like the Retro style at all. I do think that it suits a cash perfectly for what we are as a project in and where we stand and that Taking it it's super freshman. Those designs are Super Fresh. I'm gonna leave it there. + +Denis Lelic: Yeah. I was doing a little bit of research among other projects like web 3 projects. They're pretty much like, + +Denis Lelic: Taking the easy way, which means hey portal logo on it bigger. and get of course it's easier to produce but I just felt like we should do more and do better and we'll see what community and actually people have to say what do they prefer? and we'll take it from them and try to + +Denis Lelic: do some cool swag stuff. + +Zach Horn: Totally one thought is you should Loop out of Bosnia on this. I know he has strong feelings about merch in general. I'm sure he would love these but definitely make sure to run these by him. I'm sure he'd love to be a part of us. I like the idea maybe for the merch store of having a staple set it kind of like we do now very corporate clean style March that's always available and then over time rotating some of these more creative ideas and that kind of flex the brand a little bit. So you can always go in and buy the logo tease and the Very clean corporate stuff. But then also I don't know if they would literally be limited edition or we just have a kind of rotating stable of some of these ideas that we refresh every once in a while. + +00:20:00 + +Zach Horn: But I do like that mix as well where it gives people a reason to go in and check the merch store, but you always have the clean corporate stuff available, if you want something in that direction. + +Denis Lelic: Yeah, I agree. Yeah, we can always offer I prefer to have a variety of options. + +Denis Lelic: so, when you dress up there different occasions, maybe sometimes you need just a logo and Some award Mark next to it and for other occasions we can just go like crazy. and in case I'm of some sort of confidence or… + +Zach Horn: totally + +Denis Lelic: something, we can have team members wearing different swag we can do some flexing. + +Zach Horn: definitely Here's a question on the logistics of the merch at I may not be available. + +Denis Lelic: but + +Zach Horn: But if you are I'd be curious. I know we're looking for a new merch store and the bottleneck is always been that we were Drop Shipping right now. So we don't have a ton of control over what gets shipped but I've heard a bunch of people ask for embroidered merch I know it's a big step up in terms of cost and Logistics and all that. But is that something we want to pursue as well? I've seen that on social a bunch people asking for even just a simple embroidered Akash logo tea just something a little like, bump up in quality. + +Tyler Wright: Yeah, I think that's something we can certainly do. What we're looking for is not even like it is Dropship, but the other component that we're trying to find is Print on demand. So something where you don't have to keep a bunch of units that you have an inventory and then ship out. It's just like as people order you have a partner that's making those one by one. I believe the partner that we're currently using is printful and… + +Zach Horn: Mm-hmm + +Tyler Wright: I'm looking at their inventory right now. I believe they have embroidered options. that we could have custom embroidered patches and we can add embroidered elements. So that's something that we should happen to action item to make sure we add to the store from a quality perspective. Obviously, we only have the quality of blanks that the company has but they have different scales. and again, the link is printful.com for the inventory and I'll share that in the chat for folks but don't answer as I believe we have the ability to add embroidery. So we should do that with the Akash logo, maybe the word Mark and add that to the store as soon as possible. + +Zach Horn: So sounds good. + +Denis Lelic: yeah, the other thing was we discussed in our previous meeting was. a video content, but that's something I just wanted to wait on a little bit because of the Cloud models going through this process of rebranding and stuff and they're gonna do some UI refinements So whatever we would produce now would seem outdated in two three months. So I would personally rather prefer. We wait at least for the first wave rebranding process and yeah, I'm up for doing some deployment videos. + +Denis Lelic: Product demos and stuff like that. So yeah, that's why I kind of focus on the merch for now because it's just seems like a lower hanging fruit at the moment. and it's the perfect time for some merch so, end of the year. + +Zach Horn: Yeah, definitely right in time for the holidays. I am I don't… + +Denis Lelic: Yeah. + +Zach Horn: how much I can put on the right. + +Denis Lelic: Sorry. Sorry Zach. + +Zach Horn: Yeah, go ahead. Sure. + +Denis Lelic: I got a special price for you. + +Zach Horn: What you got? + +Denis Lelic: Pick one pick one. I got a special price for you. I'm kidding. + +Zach Horn: yeah. + +Denis Lelic: Yeah, go on you wanted to say something about the videos. + +Zach Horn: Yeah, if I get one of these I want the speed one. I like that one. + +Denis Lelic: Okay. + +Zach Horn: Yeah, I don't know how much I could put on the record right now because we're still discussing it Tom Thompson over. a proposal to do is first set of videos that I was literally this morning, so I haven't had a chance to review but What we've been discussing and we can save this for the website meeting, tomorrow is basically exactly what you're saying, which is if the docs are being redone right now. he's ready to get going but it's like do we wait until the dogs are a little more finalized for him to go through and create this dog's content, but he's ready to start making videos. So either depending on what comes out of working the website working group tomorrow. He may start on the docs content or we could do a different set of tutorial Style videos or just walk throughs that are necessarily related to the docs. + +00:25:00 + +Zach Horn: So'm with I'm totally aligned that we need more video content and shorts and all that. We're very text heavy right now, and we need consonant across the board. I think Tom's going to be our first really solid contributor for this. So I'll keep you guys posted with what that Bounty looks like as it comes together, but I'm completely with you that we need more video. + +Denis Lelic: Yeah. agree did he mention what kind of videos he would produce probably Just recording his screen and doing the voiceover or would he prefer some AI voice over or something? + +Zach Horn: + +Zach Horn: Yeah, that's what we were chatting about the other day. So what I pitched to him was that for the doc's content we would want to use 11 laps. So we have a brand voice. That way it gives us a couple things one it lets us establish a brand voice. So it's consistent of anybody comes to the site. They have this voice and tone that they come to expect the second is it lets us work with multiple contributors at the same time. So we get multiple people producing videos and they can just go into 11 Labs use the same voice and then it all sounds the same as opposed to having lots of different individuals. if somebody's going through the website, they're reading the content. That's like they're just a few Hearts from Thai. he may agree with that. I can't tell but he + +Zach Horn: the other thing it gets us is the ability to localize into different languages, which you kind of always needed, but it's just been like Ultra bandwidth constraint. What we could do if we use 11 Labs is do a first set of videos and then pretty easily trans them. We may have to go through and adjust the timing which could be tricky because we'd have to use, AI to translate it and then translate it back to know what we're saying What time That's on my mind currently. So I think we get Tom started on this first set of videos using 11 labs for the docs. And then we have all these options going forward. We can Loop in other contributors. We can do some localization all that. + +Denis Lelic: Yeah, I agree. I would do the same thing Just using 11 laps and doing a voiceover with that thing. It just feels like a better idea to pursue. + +Zach Horn: Yeah, totally and it's getting so good right now for a while it wasn't all the way there. But I mean even as recently the AI voiceover, especially 11 Labs is really really good. It sounds so natural. + +Denis Lelic: Yeah just remembering those audio books. It used to be a horrible thing. And now it's something you actually listen to. + +Zach Horn: totally + +Denis Lelic: And we're just getting started. + +Zach Horn: Yeah, definitely. it's kind of a funny thing that's been on the table for a while with 11 Labs. You can upload an audio sample, this Denis but for everyone else you can upload an audio sample and it will let you do AI voiceovers in somebody's voice. So literally we could upload Greg's voice and have all the tutorials be Greg, which is crazy. + +Denis Lelic: Yeah, yeah, that's true or Morgan Freeman. + +Zach Horn: Yeah. That's true. Yes, David, Attenborough. + +Denis Lelic: Yeah. exactly + +Denis Lelic: Yeah, but I guess that's one thing we can focus on in the next year. So content. We're wrapping up the website. I'm sure there's going to be a lot of website related stuff as well, but not + +Denis Lelic: In the manner, which is dead going through the whole thing and making sure. The content is there the design assets are there. But yeah, we're probably just gonna work on some of the landing pages and stuff like that. So hopefully we're gonna find more resources to do. + +00:30:00 + +Denis Lelic: many different things so looking forward to it. + +Zach Horn: Yeah. Same the landing pages has been on the marketing back burner for a long time. We do need a bunch of landing pages for all kinds of things. So that's something I'd like to focus on next year as well. + +Denis Lelic: Yeah, I mean as soon as we're finished we can focus and shift the attention in the working group. Towards landing pages. I'm all in. + +Zach Horn: totally could be a good thing for psion as team to work on as well because there's so many landing pages that we can do for all kinds of stuff. + +Denis Lelic: Yeah, yeah. I had some ideas and some drafts, but I'm gonna rather wait to see which direction we're going to take. So we can discuss that probably next year. I'm sure we're going to use all of these meetings just to finalize the website we have at the moment, Hey Ty. Yeah. + +Tyler Wright: Hey, I know and we've just talked about it. I know that Robert had shared some designs. Also Robert did those s design files one thing that I'm going to recommend and I'll talk to Dennis about this but he comes from the Consulting world if we're going to put anything in chat for people to respond to if we want feedback especially for anything design related if we could put in a format like this where each design is numbered so that people know what their referencing because I think people can get confused on how to get feedback if they're just trying to reference different pictures that are all in a group and it's a bit difficult to doing Discord, but I was wondering if you have design files for some of those because I want to talk about it how we can incorporate them into the + +Tyler Wright: Website then again. I threw some links in the chat one is a printful embroidery link so we can do some embroidery. So I will get with Denis to make sure we add some embroidered at least a hoodie and a t-shirt. I know that Greg has talked about in the Gildan quality stuff. So we'll look at a guilted shirt up there and some other things and those Zach's just put the chat hoodie would be perfect. So we'll do that. For sure and a couple of different colors, but I would also like to see Robert you can share some of the design files so we can see it down like mocking them up and also adding them to the store. And then at the top of the year I know we talked about a little bit inside our office hours as well as the community. I think Robert was doing a great job of thinking about + +Tyler Wright: a Insider onboarding kit which we were talking about in a previous Sig design meeting we could talk about what that kind of looks like in the future what those items may be. I'm not someone might get so I'm about just looking for the design files to start and then Robert just a suggestion to optimize the process by just creating a simple slide deck or some deliverable that has a number for or even if you drop it in as images here just number each or letter each image so that people can respond specifically to something. + +Robert Del Rey: Thanks, though. That's a great feedback man a spot on. + +Robert Del Rey: And about the design files I have them in kamba. Is it okay if I share the link with you or you want me to do something like Denis have on display installation + +Tyler Wright: I saw the canva link if you could take each of the designs files not So an images you shared you have a mock-up in there, but if you could share the design file. and you got the heaven Gates one. If there's a design file that's Incorporated with that. to share at the PNG something. + +Robert Del Rey: Okay, guys. + +Robert Del Rey: Sure. + +Tyler Wright: I think okay, beautiful. + +Robert Del Rey: We'll do and set it over. + +Denis Lelic: Yeah, one thing I wanted to mention. Robert or sorry you use some of + +Denis Lelic: superhero vector graphics have you used any? + +00:35:00 + +Denis Lelic: on our image Banks or Something we would have to make sure we don't. mess up with the copyrights and just in case we have to buy some of these Vector assets in case they go to production. + +Robert Del Rey: Sure, all of them I get in from kamba Pro. I pay for a subscription and use those assets. They are marked with the pro sign so I believe that should be enough. + +Denis Lelic: Yeah, I'm gonna have a look just to see. + +Denis Lelic: If the license is allowing us to resell it because it's going to be on Shopify. So just to make sure those assets are available for reselling. Just something to be aware of so. + +Robert Del Rey: Okay. That's the licensing you're referring to got it. Okay, I believe there should be a way that I can find that out and… + +Denis Lelic: Yeah. + +Robert Del Rey: maybe you can find out let me know also, yeah so that there is what one license to use the stuff in your designs, But there is another licensed in case you want to sell them. So that is the one that you are more concerned about right then. + +Denis Lelic: Yeah, exactly. + +Robert Del Rey: It's Got it. Okay. I will find out the let know, no worries. + +Denis Lelic: Thank you. anything else you guys wanted to discuss? It's the last meeting. so take advantage of the Sig design while you can. Holidays are coming. + +Zach Horn: Yeah, that's right. + +Denis Lelic: If anyone needs anything. is the time. + +Zach Horn: I don't think there's anything super pressing on my plate. It's mostly just website stuff. I think at this point because that's once we get the website ironed out the docs, we can get some of the website ors or the content contributors as I started. there that's mostly it on my side. Once we start having this merch in the store. We can get some eyes on it through social as well. Which could be good? But that's it for me. + +Zach Horn: Looking forward to next year, I guess 2024. + +Denis Lelic: Yeah, I'll be taking some time off next week, but I'll probably be available throughout. Christmas holidays New Years so if anything pops up I'll be happy to help. + +Zach Horn: Yeah I'll be async but I'll be checking messages. So I'll be around. + +Denis Lelic: cool Okay. + +Denis Lelic: we can talk on Discord and Slack whatever, but we can wrap it up for today if you guys think we covered. All the stuff we had in plan we discuss. + +Tyler Wright: awesome + +Denis Lelic: I'm going to drop these merge swag designs and sick design. maybe insiders as well and + +Denis Lelic: Yeah, looking forward to see some feed some of the feedback from community members. + +Denis Lelic: You next year. + +Tyler Wright: I could. + +Denis Lelic: Thank you everyone for joining Robert George Zach Thai Happy New Year. + +Tyler Wright: Happy New Year. Looking forward to more contributions in the New Year exciting stuff. + +Denis Lelic: cool + +Robert Del Rey: Up in a year Denis. + +Zach Horn: Same here. Thanks guys. + +Robert Del Rey: Thank you, man. + +Denis Lelic: Thank Have a good day, bye-bye. + +Zach Horn: Take care guys. + +Meeting ended after 00:39:28 👋 + diff --git a/sig-documentation/README.md b/sig-documentation/README.md index 0236bec8..41cc504d 100644 --- a/sig-documentation/README.md +++ b/sig-documentation/README.md @@ -24,12 +24,23 @@ The goal of this SIG is to foster a community around the creation and maintenanc | #6 | Tuesday, June 27, 2023 07:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-documentation/meetings/006-2023-06-27.md) |[Link](https://github.com/akash-network/community/blob/main/sig-documentation/meetings/006-2023-06-27.md#transcript) | [Link](https://jqtbpq377livrj4hbk4pw4vv2djrt3gmqxgs5zjwl7djg3lq4f5a.arweave.net/TCYXw3_60Vinhwq4-3K10NMZ7MyFzS7lNl_Gk21w4Xo) | #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) | | | -| #10 | Tuesday, October 24, 2024 07:00 AM PT (Pacific Time) | | | -| #11 | Tuesday, November 28, 2024 07:00 AM PT (Pacific Time) | | | -| #12 | Tuesday, December 26, 2023 07:00 AM PT (Pacific Time) | | | +| #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) | [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) |[Link](https://github.com/akash-network/community/blob/main/sig-documentation/meetings/011-2023-11-28.md) |[Link](https://github.com/akash-network/community/blob/main/sig-documentation/meetings/011-2023-11-28.md#transcript) |[Link](https://na7gjhjowrrxc37tzk76rixczxf4st6b3rjpfjrzktiln7yxuckq.arweave.net/aD5knS60Y3Fv88q_6KLizcvJT8HcUvKmOVTQtv8XoJU) +| #12 | Tuesday, December 19, 2023 07:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-documentation/meetings/012-2023-12-19.md) |[Link](https://github.com/akash-network/community/blob/main/sig-documentation/meetings/012-2023-12-19.md#transcript)|[Link](https://w3evlgbcqz4g4b4kicipe3gxrblirj4f2czs3eutaibrqrp7xtva.arweave.net/tslVmCKGeG4HikCQ8mzXiFaIp4XQsy2SkwIDGEX_vOo) | #13 | Tuesday, January 23, 2024 07:00 AM PT (Pacific Time) | | | | #14 | Tuesday, February 27, 2024 07:00 AM PT (Pacific Time) | | | +| #15| March, 2024 07:00 AM PT (Pacific Time) | | | +| #16| April, 2024 07:00 AM PT (Pacific Time) | | | +| #17| May, 2024 07:00 AM PT (Pacific Time) | | | +| #18| June, 2024 07:00 AM PT (Pacific Time) | | | +| #19| July, 2024 07:00 AM PT (Pacific Time) | | | +| #20| August, 2024 07:00 AM PT (Pacific Time) | | | +| #21| September, 2024 07:00 AM PT (Pacific Time) | | | +| #22| October 2024 07:00 AM PT (Pacific Time) | | | +| #23| November, 2024 07:00 AM PT (Pacific Time) | | | +| #24| December, 2024 07:00 AM PT (Pacific Time) | | | +| #25| January, 2025 07:00 AM PT (Pacific Time) | | | ### Working Group Sessions for Docs 2.0 diff --git a/sig-documentation/meetings/009-2023-09-26.md b/sig-documentation/meetings/009-2023-09-26.md new file mode 100644 index 00000000..c43c042c --- /dev/null +++ b/sig-documentation/meetings/009-2023-09-26.md @@ -0,0 +1,159 @@ +# Akash Network - Docs Special Interest Group - Meeting #8 + +## Agenda + +- Discuss [Docs 2.0 migration process](https://github.com/akash-network/support/issues/86) discussion. +- Suggestions for additional docs to be added. +- Updates on documentation. +- Update on Console Documentation (if available). + +## Meeting Details + +- Date: Tuesday, September 26th, 2023 +- Time: 7:00 AM PT (Pacific Time) +- [Recording](https://dknymsd25d4wo4gbxp6435niarkm3ugz7f6onipsi7r7aoghn72q.arweave.net/GpuGSHro-Wdwwbv9zfWoBFTN0Nn5fOah8kfj8DjHb_U) +- [Transcript](#transcript) + +## Participants + +- Andrew Mello +- George Pro +- Joao Luna +- Scott Carruthers +- Tyler Wright + + + +## Notes + +- Scott and Tyler talked about some changes to the provider documentation. To this point, there was separate documentation for setting up a CPU provider versus setting up a GPU provider. Many of the steps are the same, so Scott consolidated the documentation to make it easier to find during a users journey through the Akash Docs. These changes will be live soon. +- Scott mentioned that the Akash Sandbox is more stable, and documentation has been updated. +- Sandbox is for exploration and experimentation, and the core team wanted to make sure there was approriate supply, so the user experience is ideal for users. +- Andrew Mello mentioned that there needs to be some video guides that could add value to the docs site. He mentioned that he was interested in creating this content, and he would create a sample of what he was thinking to share with the rest of the docs special interest group. +- Tyler thanked Luna and the Quasarch team for the work that they did with the the [new docs](https://github.com/akash-network/new-docs). +- Tyler invited Luna to the next working group session for the akash website to talk about the docs and any other items. +- Tyler reiterated that the sig-docs is always looking for individuals who would like to write Akash documentation and earn AKT. Please feel free to reach out in the [sig-documentation discord channel](https://discord.com/channels/747885925232672829/1111760723463385159/1113084013419171840), if interested. + + +### Action Items + +- Andrew Mello to create a content plan for adding video references to the Akash Docs. + + + +# **Transcript** + +_This editable transcript was computer generated and might contain errors. People can also change the text after it was created._ + +Tyler Wright: Just all right, welcome everybody. To special interest group for documentation on their class network. This special interest group talks about improving documentation, a new documentation changes to documentation on the Akash network. Over the past couple of months, a group has been formed to make a working group for Docs 2.0, which is included in migration of the documentation. From Get Book, over to Hugo, Luna and Equate, Search Team led. Those efforts in migrating much of the documentation over to again, Hugo and delivered that to the Overclock Labs team for management in a darker eyes file. + +Tyler Wright: again that docs 2.0 but working group also continue to improve the structure and the layout of the documentation, and how the user flows through various parts of documentation site, so much, appreciate again, all the efforts of that working group, again, I believe that the Dockerized file has been passed over to the Overclock Labs team for management. So the Docs 2.0 Working Group has successfully completed their mission and again, continuing to move forward in this special interest group that meets monthly + +Tyler Wright: Just want to. Again, remind everybody that if there are folks in the community that have some technical ability and want to contribute to documentation this work or this special interest group is open to all members of the community. So if anybody has any documentation that they want to, Again, feel free to Wright's, documentation, add in a PR and then again it'll get reviewed by folks in this special interest group and we'll be merged taken live. So again there is a need for more folks in the community to contribute to documentation. I know Scott has been leading those efforts in the past, but because the team is so small, again, there is a desire for more contribution from the community in updating and creating documentation. + +Tyler Wright: So if anybody's interested, please feel free to message me or put a message in Big Ducks. Discord group. + +Tyler Wright: Real quick before I open up to any discussion. there's some documentation that will be shared over the coming hours and discord most specifically. I know that Scott has been working on + +Tyler Wright: Has been working on documentation as there is a validator upgrade happening tomorrow around 12 pm. If all things continue to push in the same direction, they are with that proposal. Again, there's a proposal right now that's up for vote for a small, validator upgrade Believe, that proposal is 231. And again, that upgrade will be happening tomorrow at 12:00 pm Eastern time 9:00 am Pacific time that documentation will be shared and discord a little bit later. So if anybody has any questions related to the validator upgrade happening tomorrow in the documentation associated with that, please feel free to leave a message in chat again when that documentation is available, + +Tyler Wright: I know that Scott's and Andre and other members of the team have been working on some improvements to the provider documentation. So I know that again over the past week or so. I think there's been a number of changes and upgrades to the provider documentation for those that are Building Providers and Managing Providers on the Akash Network. Scott's, I know that you've had a big hand in many of those efforts. Is there anything that you want to mention specific to that documentation that's been updated. + +Scott Carruthers: Yes, it hasn't been merged yet. But yes, the big update will be. as we're going through Testnet and as Mainnet launch, we wanted very concise instructions for those that want to bring GPU resources on to the network. And there's also, some divergence and steps of there's obviously some things involved and they provider build that are not relevant to A provider that is not hosting GPU resources, like Nvidia, drivers and runtime installs, and things like that. But now going out over time, it's not + +Scott Carruthers: efficient for us to maintain two completely. Separate provider instructions and docsolutely. So anytime To be something like provider version update, missing air prone to have to make those updates in both spots. So, I've going through the process of converging, the provider instructions, and A existing provider instructions, and I pretty much have Completed. I think it's a very seamless process now where someone's not gonna have to jump back and forth between documents? there's some optional stuff for GPU providers that Non-gpu providers can just skip over. So, I've pretty much completed it. But as with anything before actually published documentation, I like to actually run through the instructions myself to make sure there's no, + +00:05:00 + +Scott Carruthers: Errors. So over the next 24 to 48 hours, I should be able to complete that testing and then I'll merge That new provider documentation. So again, it's not really anything. All that new. It's just kind of convergent of disparate documents at this point, but anybody in this gone through the process, will still look very, very familiar. + +Tyler Wright: Thank you Scott by clarification. + +Tyler Wright: Is there any other documentation that you've been working on over the past month or so that you think is worth noting and sharing with members as a team and folk that'll be listening in later? + +Scott Carruthers: I mean, primarily it over the last month, that's may not upgrade documentation and the stuff that I previously. Mentioned with. GPU provider documentation. I just send out a announcements to the insiders, the occasion ciders today so that they can distribute the message we're now bringing in the Akash sandbox and to + +Scott Carruthers: Were now opening the Akash sandbox for use across. All different types of new user. Onboarding and experimentation. So we're no longer going to have to provide faucet manually. Divyo 20 Akt for initial user experimentation, so we're just going to be using the sandbox. Solely for those purposes. So the sandbox has been around for a while but We have to wait full client support for it. And now the Akash console and Cloud must deploy both support sandbox. And we also obviously needed to ensure that there was sufficient. + +Scott Carruthers: Capacity on sandbox providers for new users to not give them a bad first experience and we've now completed all those items there's sufficient capacity on the providers. We believe we'll have to monitor that over time but we Believe there's sufficient capacity and now all clients support it. So that was another documentation that I Just announced this morning. And yeah, that's main Upgrade GPU providers, and sandbox documentation, or we'll come to mind since our last + +Tyler Wright: Excellent, thank you. Does anyone else have any Comments, thoughts about cost augmentation that they want to bring up right now? + +Tyler Wright: is there any? Glaring. I know that some folklines call, our also involved in the insiders communities or anything that might need updating that you all see on the community side or The insiders when you're supporting folks and discord and elsewhere, that might need some clarification. Be a documentation for folks that are using it. + +Joao Luna: From my side. Nothing that I found yet. + +Tyler Wright: Go ahead, Andrew. + +Andrew Mello: Good morning, everyone. Can you hear me? Okay, great. + +Tyler Wright: Yes. + +Andrew Mello: So I just wanted to confirm I know a ways in a whiles back we had in a multiple paths for provider builds and it seems that we are now fully in helm charts is the default path. that's what I understand. I just like to bring up a little clarification around kind of the layout of things and the high level is that our documentation still seems to push us. + +Andrew Mello: Through a variety of potential like provider pads and it just high level, note here. It might be nice to kind of dial in and focus in on those helm charts as that default path. Because right now, when you go to the Providers tab and build a cloud provider, it's still the original 45 minute fullcade s cluster, through that kind of path without the helm charts as being the focus there. So I just want to bring that up and I'm sure it's something that Scott is aware of. But yeah, just make things a little bit easier for people. + +00:10:00 + +Tyler Wright: Excellent. Thank you very much, Andrew for that perspective, and I'll stop. + +Tyler Wright: Is there anything else documentation wise that anybody wants to cover? + +Joao Luna: I would like to ask regarding the migration for the tudoro. + +Tyler Wright: Cool. I just want to Go ahead then. Yes. + +Joao Luna: Maybe that's a subject we can touch on. + +Tyler Wright: Absolutely. + +Joao Luna: So, what's the progress? Have you done anything with The docker image. that was migrated is it's still on the backlog To do. + +Tyler Wright: Yeah, so over the next week and even by weekend weeks, and that Docker image will be live on Akash with a specific URL that could be tested. And We'll share that out with the insider community over the next maybe 10 to 15 days for people to give feedback on the structure and path. There's still some discussion happening, unrelated to the docs around Hugo as + +Tyler Wright: a building block resource that will be used for the website. I think you could see that there was a website revamp proposal that went through as a part of that proposal. There is some discussion on whether or not Hugo is a better option than potentially Astro. There's not been a conclusion made but basically, whatever happens. the front end structure of how the experience kind of looks and feels the work that was done by a doctor 2.0 would not change. The only thing that potentially would change would be if you go is + +Tyler Wright: not geared to support, both developer documentation. The current a user documentation Ass show, might be able to do a better job of that and some other elements related to the blog and some other things. So there's a working group Akash website session happening on Thursday where we're going to get an update on Astro versus Hugo. and then again following that conversation will either Take the documentation sites out of docs 2.0, that Luna you an equation. Worked on live for again, feedback from the insiders by Friday or This week based upon the decision that's made amongst other cash website group. + +Joao Luna: Okay, got it. + +Tyler Wright: Anyone else have any questions? + +Tyler Wright: About that or anything else tax related. + +Tyler Wright: One other thing. Again, I think I mentioned this at the top of the call, but this dig is looking for folks that want to contribute to writing, new documentation, Scott who's been leading efforts on documentation for a long time. Needs to be focusing on other things core to the product and so the goal is to continue to push him towards those things, which means we're really going to need folks from the community to step up and contribute to at least developing phase one of new documentation. It can always be edited by folks, like anybody on this call that might be able to edit and test out the documentation before again, it gets merged. But if you all see anybody in the community, that's get looking to contribute and you see that there will be rewards, and potentially again, monthly, rolling down teeth for folks that + +Tyler Wright: Want to contribute to documentation on a consistent basis. Go ahead and + +Andrew Mello: Yeah, so just could you clarify it there a little bit, Tyler? What? The purpose is, obviously there's a lot of existing documentation, Are you looking to expand that documentation into specific directions? I heard the word rewrite there, out of nowhere. I mean Could you clarify a little bit what that is? And then second point is this only covering written documentation, my opinion is there's a bit of a blind side here with video documentation missing especially in 2023. So just to question there, if you could clarify that a bit and then that would help me know if I could somehow help out or get involved in direction. + +00:15:00 + +Tyler Wright: Yeah, so I think to start, as it retains to the word rewriting of documentation. I believe that the documentation is in a great position right now. But there are always times when as Scott maybe mentioned at the top of the call where the documentation is a little bit out of date because version change, there's upgrades that happen so maybe the definitely not rewriting documentation from The beginning. But always updating documentation, says as things change or writing of new documentation is new features present themselves on the network. So a lot of the efforts that Scott has done in the past, where new features have come on again. Now, there's a sandbox environment for folks to test those features Scott had to + +Tyler Wright: I had to go through and test all the features write documentation for folks that are going to be levity, news teachers, like ipleases persistent storage again upgrades, etc. So as we continue to move forward as a special interest group, and as a cost continues to evolve, there's a desire for more people to get involved in the process of writing. Some of that documentation in terms of video guides, there is a consensus amongst folks in the working group of cosh website that video guides are very much needed democus from the community has worked on a couple of video guides on how to deploy specific things on a console and cloudmose, as well as using the CLI Andrew, If you would like to have a discussion about what kind of video content you with to contribute or you think needs to be added to the state documentation. I would love for you to throw any. + +Tyler Wright: Questions in discord and then put an associated. This is how much it will cost me to create this content and this SIG there's dollars it's going to Akt available. That's this. Special interest group can pull from if it makes sense. So, + +Andrew Mello: And just to give you full clarity on what I meant by the video stuff, the Akash network YouTube last video was published three months ago and the last one before that, looks like eight months ago. That would be a great place to just, start building a documentation playlist and having our channel have updated videos, weekly or whatnot, just to keep subscribers, just to keep people interested. Even if it is just videos going into a, documentation playlist. But, it's so creating content and it's so putting it out there for people to engage, watch and share. + +Tyler Wright: Andrew, I can't agree with you more. So I think this is a great idea. I would hope that again, I know that you're working a number of things, but if you have time, if you could throw in the SIG, documentation discord channel and idea of maybe one or two videos that you would like to start with. And again, What a desired reward for that would be and we can continue to move from there. + +Andrew Mello: Yeah, what I'll do is I'll model out a little sample schedule for what a quarter or so would look like ideally again in these social media platforms. You really really want consistency because without it you're not triggering the algorithms at all, you don't get them excited or alive by, huge gaps of time. So consistency is really important and that's what I'll ideally come back with for a video schedule for some documentation. + +Tyler Wright: Excellent. Does anyone else have any discussions or anything else that they want to discuss? + +Tyler Wright: Okay, if not then again, much enjoyed the conversation today. Luna, if you want, please feel free to join that working group of cost, websites on Thursday and here live kind of what's going on and how it affects stocks 2.0 again much. Appreciate all the work that quesar shame is done on Dock 2.0 in helping migrate again, the documentation from Get book, but also helping with the structure as we continue to improve. And just again focus on user experience for folks. But again, much appreciate everybody on this call notes, will follow. Please let me know if you have any other questions and feel free to leave any comments thoughts or concerns inside the SIG documentation discord. + +00:20:00 + +Tyler Wright: there is a Syrian committee meeting rather happening on Thursday. look after that. And also some other special interest groups happening this week. So, again, much, apprecious, much appreciate everybody has a great rest of the day. Talk soon. + +Andrew Mello: So yeah. + +Scott Carruthers: Thanks everyone. + +Joao Luna: My thank you. + +Meeting ended after 00:22:19 👋 + 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-documentation/meetings/012-2023-12-19.md b/sig-documentation/meetings/012-2023-12-19.md new file mode 100644 index 00000000..e4e20a72 --- /dev/null +++ b/sig-documentation/meetings/012-2023-12-19.md @@ -0,0 +1,291 @@ +# Akash Network - Docs Special Interest Group - Meeting #12 + +## Agenda +- Update on Documentation. +- Docs 2.0 Effort. +- Community and Support Contributions on Documentation. +- Discussions on Video Documentation. + +## Meeting Details +- Date: Tuesday, December, 19 2023 +- Time: 7:00 AM PT (Pacific Time) +- [Recording](https://w3evlgbcqz4g4b4kicipe3gxrblirj4f2czs3eutaibrqrp7xtva.arweave.net/tslVmCKGeG4HikCQ8mzXiFaIp4XQsy2SkwIDGEX_vOo) +- [Transcript](#transcript) + +## Participants +- Andrey Arapov +- Scott Carruthers +- TG (Thomas Greco ) +- Tyler Wright + +## Metting Notes +#### Tyler Wright: +- Welcomed everyone to monthly meeting number 12. +- Discussed ongoing efforts to update and address documentation needs. +- Highlighted discussions on video documentation and the creation of a working group for Docs 2.0. +- Emphasized the transition from GitBook to Hugo for a more open-source solution. +- Acknowledged Scott Carruthers' significant hands-on involvement in 2022 and beyond. +- Noted Scott's role in transforming documentation from sparse and inconsistent to a usable state. +- Recognized Scott's collaboration with Andrey and the group effort to maintain up-to-date documentation. +- Highlighted Scott's proactive approach in Discord and other community platforms to ensure optimized documentation. +- Commended the two responsiveness to community needs and continuous improvement of documentation. + +### Community support for writing and editing documentation +#### Tyler Wright: +- Noted Scott's shift to an engineering role in the last four to five months. +- Emphasized the importance of community support for writing and editing documentation. +- Interest from both Insiders and the general community to assist in documentation. +- Anticipated Docs as a hub for those wanting to contribute. +- Announced a meeting at the beginning of the year to share the documentation framework. +- The framework will be available on GitHub, with live meetings for questions and support. +- Community Engagement and Documentation Process: +- Encouraged community involvement during calls to discuss documentation. +- Highlighted the documentation Discord channel for real-time communication. +- Outlined the process for community members to participate in editing or updating documentation through Pull Requests. +- Emphasized the ongoing nature of real-time documentation updates. +- Encouraged involvement from anyone interested in contributing, regardless of technical background. +- Mentioned upcoming framework with rules, regulations, and guidelines for documentation creation. +- Announced akt bounties for those actively participating in documentation. +- Highlighted the availability of ongoing conversations into the new year. + +### Transition from Hugo to Astro +#### Tyler Wright: +- Noted a shift from Hugo to Astro for documentation based on community and website working group decisions. +- Mentioned flexibility and support as key factors influencing the decision. +- Acknowledged the impact on the Docs 2.0 deliverables after the transition to Astro. +- Highlighted ongoing rework led by Piyush and his team as part of the website revamp effort. +- Acknowledged the necessity for a bit of rework due to the shift from Hugo to Astro. +- Emphasized the hands-on approach of the website revamp team in migrating the documentation. +### Video Content Plans: +- Thomas plans to speak with Zach about creating general-purpose videos not reliant on Docs 2.0. +- Emphasized the intention to get videos out ASAP. +- Reiterated the importance of creating content that remains applicable even without Docs 2.0 being fully operational. +- Tyler and Thomas discussed the idea of creating high-level content showcasing Akash Network features. +- Mentioned the possibility of creating content on Cloudmos deployment as part of the initial video plan. +- Tyler confirmed agreement with the idea of creating high-level content before Docs 2.0. +- Tyler encouraged content that highlights Akash Network features and could later be linked to specific documentation. + +### Website Launch Date Inquiry: +- Scott Carruthers inquired about the projected launch date for the new Akash website. +- Specifically asked if the launch date is affected by the holidays and if there is a firm date for Docs 2.0 launch. +#### Tyler's Response: +- Tyler acknowledged the question and provided information about the original plan. +- Explained that the revamp website working group is focusing on ensuring elements like light mode and mobile functionality work seamlessly. +- Mentioned that the technical work is expected to be completed within the next 10 days. +- Stated that the website launch is planned for early January when more team members are back. +- Emphasized that the launch date has not been finalized but is likely to be in the first or second week of January. +- Discussed the possibility of delaying it by a week if necessary but assured that it wouldn't be an issue. + +### Inquiry about Docs 2.0 Review Period +- Scott Carruthers inquired about the synchronization of the working revamp website for Docs 2.0 with the final product. +- Mentioned the concern that the current links to Docs 2.0 are not up to date, leading to potential confusion for reviewers. +#### Tyler's Clarification: +- Tyler clarified that the intent is for the working site to be in sync with the final Docs 2.0 product for review. +- Acknowledged the current state being not worth reviewing but assured it will be ready for review by the next working group session. +- Emphasized that staging links will be continuously updated this week and beyond as changes occur for Docs 2.0. +- Mentioned the plan for Thomas, Scott, Andrey, and others to start reviewing the updated docs by the upcoming Thursday. +- Clarified the current local state of Docs 2.0, which is not yet ready for public review. +- Confirmed there will be a period, possibly one or two weeks, for the community to review and make suggestions. +- Assured that direct links will be provided in SIG documentation, the website working group, and GitHub for accessibility. + +### Discussion on Links in the revamp Website +- Scott Carruthers raised a concern about the current working site linking "Getting Started" to the Akash CLI documentation without sufficient context. +- Inquired about how Piyush and his team are obtaining feedback on the direction and structure of Docs 2.0. +#### Tyler's Response: +- Tyler clarified that Piyush and his team are actively receiving direct feedback from working group sessions. +- Emphasized his role as a representative for the working group Docs 2.0, ensuring effective communication of feedback. +- Mentioned the involvement of Dennis in user experience and Zach Horn in marketing, both contributing to many of the pages, including the "Getting Started" page. +- Highlighted the "Getting Started" page, which focuses on tools like Cloudmos and Preator, providing alternative ways to start rather than directing users immediately to the Akash CLI documentation. +- Acknowledged that while the CLI is present in the documentation structure, it is not the primary focus and is placed further down the user experience tree. +### Concerns Regarding Documentation 2.0 Structure: +- Scott Carruthers expressed concerns about the structure of Documentation 2.0, particularly in categories like providers and feature sections. +- Mentioned potential issues with the sequencing of documents and deeper structuring concerns. +- Raised the possibility that there might be a need for significant updates beyond the "Getting Started" section. +- Highlighted a desire for a more organized and logical sequence of documentation. +#### Tyler's Response: +- Tyler assured that he has actively participated in Docs 2.0 working group discussions and the special interest group for documentation. +- Emphasized his efforts to articulate feedback clearly and involve engineering resources in addressing concerns. +- Stated that the working group for the Akash website has been highly transparent, with confidence that many concerns will be addressed in the new iteration. +- Encouraged waiting until the new link is provided before making specific comments or raising concerns. +- Acknowledged that while optimization is a goal, preserving elements that are working well in the current documentation is also essential. + +### Engineering Notes Overview: +#### Tyler Wright: +- Acknowledged Scott Carruthers' parallel work on engineering notes. +- Highlighted the need for more technical documentation for those building on Akash. +- Scott collaborated with the engineering team and community for detailed engineering notes. +- Emphasized the importance for those seeking a deeper understanding of the Akash Network. +- Engineering documentation currently available in staging for Akash Engineers. +- Engineering notes Will be part of the revamped Akash Network website on the docs page in 2024. + + +### Other Matters Discussed +#### Recognition of Thomas's Contribution: +- Tyler acknowledged Thomas's recent active involvement in the Akash Network Community. +- Tyler mentioned Thomas's commitment to contributing to technical documentation, both written and video. +- Highlighted Thomas's efforts in articulating skills and improving documentation and user experience. +- Expressed appreciation for Thomas's contributions and anticipated more in 2024. +#### Acknowledgements and Appreciation: +- Tyler opened the floor for any questions or topics participants wanted to discuss in the final Sig documentation meeting for 2023. +- Thomas expressed gratitude to Tyler for running the Sig meetings and acknowledged the helpfulness of Scott as he ramped up his contributions to Akash. +- Andrey echoed Thomas's sentiments, expressing his anticipation of working more closely with Thomas in the future. +- Wishes for happy holidays and a great New Year were exchanged among the participants. + +## Action items +- Tyler to provide direct links to Docs 2.0 in SIG documentation, the website working group, and GitHub for easy access during the review period. + +# **Transcript** + +_This editable transcript was computer generated and might contain errors. People can also change the text after it was created._ + +Tyler Wright: All rights, welcome everybody to monthly meeting number 12, I believe during The Specialist Group for documentation folks on this call meet and discuss active documentation any documentation needs to be updated there's been discussions in the past couple of meetings about video documentation Out of the special interest group docs there was a working group that was created to support Doc's 2.0 to really update the structure of the documentation and at the time moved from getbook to Hugo. So again there would be a more open source solution that the community can use + +Tyler Wright: On the call Scott Carruthers has been Hands-On very much of 2022 in the first half but really beyond that in 2023 getting the documentation into the state. It is with a great deal with support from Andre as well before Scott's had joined the team the documentation was a sparse inconsistent in some cases and that was just as the fact of a growing organization with again new features the product was continuing to evolve but Scott Carruthers did a great job over I believe his first year and a half with overclock Labs really taking that documentation to a state where users can use a documentation without + +Tyler Wright: needing support from anybody from the community and really leveling the documentation to a point where the kind of is today. Scott's again along with Andre have had a pulse on the support in Discord and other places in the community and made sure that the documentation was always up to date who again features improved as the product continue to mature as they saw folks in the community dealing with issues with the documentation or as a documentation change. They made sure that the documentation was optimized for the community and again made any changes where we're necessary. So I just want to shout out those that hurts there. + +Tyler Wright: as one of the big items this year was around working group docs 2.0 where a structure was updated for how the user documentation on the Akash Network would be outlined and laid out. Thanks to the croissants team for being a part of that process led by And halfway through the year again, a structure was initially determined Luna and his team presented that structure and a preliminary understanding of what the web of the documentation would look like to the steering committee and got some great feedback. Over the last really four to five months with Scott's moving into more of a engineering capacity to help build out the features of the Akash Network. It is really been. + +Tyler Wright: important to find folks in the community that are willing to support writing editing existing documentation and making sure that documentation is to the standard Which Scott and Andre lifted to there's been a number of folks in the community both on the Insiders and just in a general community that showed interests over the last couple of months to help support documentation. In 2024 docs will really be a place for folks that are looking to get involved the right documentation to ask questions. Make sure that the structure the format of how documentation look it consistent. + +Tyler Wright: There will be a meeting at the top of the Year where again the framework and the structure of how documentation should look when users start to get more involved in contributing to documentation will be shared again that framework will live a couple places and GitHub as well as there will be some live meetings for people to ask questions get some support just in case they have any questions about to get that documentation framework. There'll be something that's happening in the top of the year. But again as we get there, we want to make sure that folks are know that there's the possibility to get involved with documentation. + +Tyler Wright: The process as of right now is focus on this call and during these calls will talk about documentation. We can ask additional questions in the documentation Discord channel of there's something live that we want to talk about. And then again if anybody wants to participate in editing or updating a documentation In they can or make a PR and then Andrey and myself will look at those PRS and merge those as necessary to make sure it again the documentation is updated in real time. + +00:05:00 + +Tyler Wright: So as we again move into 2024, I really call upon anybody that's listening in to this call later or looking at the notes to know that they can get involved in documentation. If they're technical writer there are non-technical writer and they want to help with editing again always next there will be a framework. So the rules and regulations and guidelines and how the documentation should be created and how it should look. But again from there, there will be akt bounties available to those that want to participate in making sure that the documentation continues to be updated in real time. + +Tyler Wright: So again, those are conversations that will continue in to the new year and that's how we're kind of structure this sig in 2024 around again existing documentation is maybe up for PR and needs to be edited updated or talked about someone talk about those things during this think that meeting or if anybody has any suggestions for new documentation or just again a review of any outstanding documentation. + +Tyler Wright: cool one other thing that puts us kind of in limbo right now is after Luna and the quasarch team moved the docks over to Hugo as part of the requirements for the doc's 2.0 deliverables the Akash community and the website working group decided that Hugo was not the best approach moving forward for a number of reasons. But again the team on the website side to go in the direction of Astro because of his flexibility and support. + +Tyler Wright: Because the changes when computer go to Astro and meant that while the work of the working group docs 2.0 structure structuring and some of the discussions that were carried over into the ducks that will be on the website. There did have to be a little bit of rework that is currently going on with piyush and his team that's leading the website rehab effort. Again, it's a part of the new website. The docs will be moving from data cash dot Network to a/docs. That's not a change that's happening right now. But that is the change that's going to be happening in the future. So as a part of those efforts again the team that's doing the website revamp is going to be Hands-On and migrating and documentation over. + +Tyler Wright: Two again the more optimized Astro backend. + +Tyler Wright: One other thing I want to call out before I move on as we review 2023 is the work that Scott has done in parallel on some engineering notes. So again, the core documentation is around using the Akash Network deploying as a tenant becoming a validator upgrade documentation. Everything related to again the network. There are those that are interested in building on top of akash, whether it's their own clients or other tooling and just leveraging their cash Network and there it's a deeper understanding of what the Akash network is and how it works that again is not has not currently been outlined in the documentation that today + +Tyler Wright: Scott Carruthers has been working behind the scenes with the engineering team and certain members of the community for validation to design engineering notes that are far more technical documentation that deep died into exactly how the accost network works. the code base where things might be able to be found etc. For those again that are a little bit more Technical and looking to be to build on top of the cost Network that engineering documentation has been available for people to digest and it's staging + +00:10:00 + +Tyler Wright: area Akash Engineers that XYZ. But again, this documentation will also be a part of the new revamped a cost on network websites on the docs page. So again, I just want to shout out the efforts of Scott's across, the current documentation as well as the engineering documentation. something that'll be launched in 2024 with the goal of having more folks. They're looking to maybe help with support issues looking to contribute to the core code base Etc have the documentation that is a little bit more technical that does a deep dive into some of the concepts so that when they are ready to Support and help with the code base They Are Up level to a point of understanding that is necessary to build on top of the Akash Network. + +Tyler Wright: I'm sure there's plenty that I forgot again much appreciate Scott and Andre for all their efforts on 2023 and really before that and getting the documentation to where it is today. + +Tyler Wright: again as we also way to move into 2024, I do want to shout out who's also in the call Thomas who has recently gotten a little bit more active in the Akash Network Community. He's somebody that is going to be contributing to technical documentation, whether it's written or video in the last couple of special interest group sessions and working group sessions. Thomas has been doing a great job of articulating his skills and kind of taking the first steps and understanding what kind of content should be first up for showing showcasing, ways to improve documentation or improve the user experience for those that are trying to use the Akash network with video guides Etc. + +Tyler Wright: To much appreciate his effort that I know that as we move into 2024, there will be more from him and on the consistency front in terms of items that he's working on to support written documentation with video guides or just again to support documentation in general which is expertise and knowledge. So just want to call them out because he's on the call. And been very active. One other thing I want to call out is again inside six documentation. + +Tyler Wright: Thomas has started discussion around. Some feedback in terms of some videos if anybody wants to contribute. I know that I owe I believe a response as well, but I'll drop the link to that chat. In here and I'll drop it in the notes for folks that are watching later or looking at the notes later. But again, if anybody wants to give feedback, I know that Scott gave feedback on just a general high-level direction for video content speed. Cadence topics how things are linked Etc. Thomas is certainly looking for feedback there. + +Tyler Wright: I just went on a 14 minute monologue describing 2023 in great detail or in some detail rather. Does anyone have? Anything that they want to talk about today, I know that we're again kind of in a holding pattern as pollution is team are moving some of documentation over. I know that there's a staging site for the website to the cost Network website revamped on that website. There is that docs page is very much out of date as again Pierson is team grading the documentation over and optimizing so I think it wouldn't be a great use of our time to talk about that right now until it's in the states that is worth discussing and optimizing but Thomas I see your hands up. So go ahead. + +Thomas Greco: yes, so forgive me if my voices shot because seem to have got another sick or something. you can hear me, right? + +Tyler Wright: Yes, sir. + +Thomas Greco: Okay, All Yeah and just from Tyler's we spoke last week. and as you know Scott and I spoke about Showing some of the live docs 2.0 in some of the video content. And I kind of the need to put some of that on hold. I just want to Reiterate that I will be speaking with Zach about just getting some videos out the door. ASAP that don't necessarily rely on back 2.0. + +00:15:00 + +Tyler Wright: ;? + +Thomas Greco: being up and running and just more general purpose the content was still be applicable. So if there's something you're interested in. I could definitely find time for that. + +Tyler Wright: Yeah, I know that we talked about this in. Sig documentation that I'm a firm believer that some of that high-level content that maybe doesn't link I like the idea that Scott talked about when that's 2.0 is available and Thomas and others are creating videos for specific documentation linking to that documentation. So it's easy for somebody to find the documentation. If they need to read alongside. They're watching the video would be great. But prior to that there's anything that we can do that just like highlights at a high level the accost Network features Etc. I think those kind of content would be great or even Cloud most, + +Thomas Greco: You just took the words out of my mouth. I was going to say even my cloud most deployed. and that's one area I could cover and that was actually in. the word plan for the initial videos I was going to do so. There's some over that there. + +Thomas Greco: Hey, as long as you're on the same page. + +Tyler Wright: Yes, yeah. + +Tyler Wright: Go ahead Scott. + +Scott Carruthers: I'm sorry. I have to relate a question. So I'll just go one at a time. So, it's Tyler. what is the current? projected day for the new Akash website spending up and I think we've definitely always been under this standing understanding and that the expectation is that ducks 2.0 will launch of the same time. So I'm wondering what do we have a firm date on when we're supposed to live and also related to that is that impacted by the holidays at all. So, knowing that after this week, I'm going to be + +Scott Carruthers: out for two weeks return on January 6th. And yeah, could you just speak to what is the current projected date? And is it possible? It could be hitting during that period where some of us are out and I'm not saying that necessarily that's a showstopper. But just wondering what the projected date is and if it's affected by the holidays. + +Tyler Wright: Yeah, absolutely. That's a great question. the original plan was to launch part of the Cosh website on Christmas morning and the other part on New Year's but nobody was available not I'm just kidding. the plan is really open the next couple of weeks the revamp website working group has decided to make sure that the light mode mobile all the things are working not demise. So petition is team are working on those things over the next 10 days. + +Tyler Wright: Once those items are done. They're going to be reviewed by Dennis myself Zach. I'll bring an Andre to look at them as well because I believe he'll be around but the plan to launch a website isn't until early January when folks are back. I mean we made sure that the docs are look good in some of the other items. So again, the technical work should be done. 10 days from last Thursday, but again, the launch date has not been finalized yet, but we both but will be at a time and probably the first or second week of January. I think there was initial thought of it being around January 3rd, when more folks are back, but even if we have to delay it another week There's no problem to do But that's the initial plan right now. + +Scott Carruthers: And my follow-up question was some related to the launch date. so we know based on this specifically Tyler you're my direct conversation last week, and I think it's well known to the community as well that they Links that we have to docs to God. as you mentioned earlier in this conversation are not up to date. So if you visit the working site for ducks 2.0 that shouldn't be Taken as representation of what the final structure is going to look like And it's out of date. It's not in sync with where piercing his team are currently on Atwood Ducks 2.0. So my question is there going to be a period of time That working site is in sync with the final product and then there be a period of time where we can review. + +00:20:00 + +Scott Carruthers: On that working site or is that not the intent and they intend instead is that people are inspecting it in the background and we'll just rely on Behind the scenes design and structure sessions instead of having a link that would allow. The community to be able to review the content before launch. + +Tyler Wright: no, no, sorry if I misspoke the intent is that Hopefully by Thursday the next working group. + +Tyler Wright: For a cost website piercing his team will have the docs 2.0 in a state for review. The staging links always will be up to date this week. And then we'll be continuing to be up to date as things change for Doc 2.0. So I believe folks like Thomas Scott yourself Andre and others in the community will be able to start reviewing the updated docs this Thursday. But right now it's just in a local state,… + +Scott Carruthers: Okay. + +Tyler Wright: right so currently it's not worth reviewing but that's a Thursday should be and beyond that it'll continue to live and staging so that folks can give feedback async and patience team can continue to update as necessary. + +Scott Carruthers: Okay, so there be a period of possibly one or two weeks where that will be the date that people can review and… + +Tyler Wright: exactly + +Scott Carruthers: make suggestions. Okay. + +Tyler Wright: Exactly, and I'll throw those links when they're available in Sig documentation for direct link to the website. So people can see it there and also live in the Working group and the website working group. projectile and GitHub as well + +Scott Carruthers: All Yeah that all Sounds good and optimal, I guess I'll raise this question. How are they you and I discussed before just to get it out in public and maybe Andy and Tom. May benefit from the sum as we get access to that link and look at the new structure content. So in a discussion between you and I last week I talked about A concern that in the current working site that understood it's not up to date at all. But in the current working site it is linking people getting started to the costs toi documentation. And so I guess my question to kind of follow up to that conversation that we had as petition his team are. going through the current iteration of ducks 2.0 + +Scott Carruthers: I mean, maybe could you just speak into so how exactly is that working? how are they getting the feedback that we believe that we're getting started should definitely not just dump people into a cost CLI documentation without much context and as I guess that From a high level. What I'm asking is Pierson his team if they're working through. their current version of ducks 2.0 getting that input enough feedback on or how are they deciding on what direction to take they structure + +Tyler Wright: Yes, so they are getting direct feedback from those sessions and I'm being representative for the working group docs 2.0 making sure that those things are articulated but also Dennis on the user experience side as well as Zach horn on the marketing and also focus on user experience side. Have we Worked many of those pages. So they're getting started page really highlights some of the tools like cloudmos Prey tour some of the other ways you can get started that are not focused and really puts an emphasis on trying to make a user Journey that is as smooth as possible with the CLI not being optimal right now. the structures of the documentation is + +Tyler Wright: pretty above pretty much the only thing that we took from Dr. 2.0. That's I kind of outline but in the iteration from huge and the working group of cost website CLI is not the first thing at all. It's pretty far down the user experience Tree on how people are going interact, but it is there. + +00:25:00 + +Scott Carruthers: So I would say that my only concern and you may be thinking just wait until we provide you the link and then draw an opinion on that. I understand that I'm not trying to jump to conclusions. to me they're Possibly could be a concern that the first time that we have access to possibly find out that there's a decent amount of updates that are necessary. So the reason I say that is if you visit that link right now and you go into the provider section and some of the feature Sections and things like that. I would think that if Andy and I were to look at that to think about the user journey and building a cost provider right there. the current representation in that link is that + +Scott Carruthers: the categories are not structured and structured from that sequencing perspective of just simply what documents should come first and then also, some deeper structuring concern so I guess my point being is when I look at that the concern is not just in getting started, but they're probably a lot concern over. the structuring throughout docnts documentation 2.0. So all that's fine. And like I said maybe they're responses just wait and until we provide you the new link and go from there. But if it + +Scott Carruthers: If there's a lot of attention being paid to getting started, but we're following the structure generally of what I've seen. From the first iteration of ducks 2.0 the third Bay a lot of work that's necessary even outside of getting started. So again, maybe it's not concern and maybe All that's been. Adjusted and when we get the blanket wall. All look. It doesn't sound like There's participation in some of those discussions right now, so I don't know to me. It seems like possibly there could be a concern, but maybe we'll get the link in all as well. But those would be my concerns going into it. + +Tyler Wright: Yeah, I hear My only feedback would be I Tried my best to be a part of every Doc's 2.0 working group as well as the special instance group for documentation. I've taken everything that I've heard and + +Tyler Wright: Try to make sure that it is articulated as clearly as possible when things are not represented properly. I try to bring an engineering resources. So working group for a cost website has been extremely public over the last two or three months and I feel confident that once you all have the link that I'm sure it won't be perfect. But my hope is that a lot of your concerns will. + +Tyler Wright: Not be there. But again, I will save any comment until you all have the link in them. We can go from there. But everything that you've articulated is very much top of mind because I know there's been a lot of work that's gone into the documentation as it stands today. And I know that there's not really that much of a complaint from people in the community as things stand today. So we want to optimize the structure but make sure that many of the things that are here today on to the Future because they're working. + +Scott Carruthers: Okay, sounds good. Yeah, I don't want to race concerns when there might not be any so yeah, obviously we just need to see what it looks like when the new link is provided. the new work inside is provided. It sounds like on Thursday. So yes. It just voice and possibly some concerns based on what I saw with the previous. Iteration, but yeah, it's probably doesn't make too much sense to spend much more time on it and just wait till we get the link and go from there. + +Tyler Wright: Absolutely. + +Tyler Wright: Is anyone else have any questions? Anything they want to talk about today as we wrap up this last Sig documentation meeting for 2023. + +Tyler Wright: if anybody thinks if anything, go ahead Thomas. + +Thomas Greco: All I just want to say thanks you Tyler for running these girls. So Scott communicating with you. you've been really helpful and really useful as I really ramp up here contributing your cash. And then Andrey, I kind of assume the same. the new and not sure if we worked directly together as much but I'm sure we will in the future and I look forward to it. + +00:30:00 + +Andrey Arapov: They're looking forward to Thomas. Thanks for a nice words. And Merry Christmas guys. + +Thomas Greco: Yeah, happy holidays. Have a good New Year too with it for everybody if you don't talk. + +Andrey Arapov: the holidays + +Tyler Wright: That's absolutely thank you all much appreciate everybody,… + +Thomas Greco: See you. + +Tyler Wright: but we'll talk online. If anybody has anything else. They want to talk about feel free to drop it in Sig documentation Discord, but as Thomas said I just want to Echo much appreciate Scott as always big fan of his Andre the same just great guy and Thomas says, I'm getting to know you really like your Diligence and your communication style and so really excited to work more closely with you in To all those that'll be listening later again much. Appreciate your efforts over the Year I hope everyone has a great holiday season and happy New Year and we'll just picked us up in 2024 and hit the ground running with a lot more contributions from the community. + +Tyler Wright: Thank you everybody. Talk to you soon. + +Andrey Arapov: thank you my + +Scott Carruthers: Thanks, everyone. + +Tyler Wright: Bye. + +Meeting ended after 00:31:42 👋 diff --git a/sig-economics/README.md b/sig-economics/README.md index 7d3a1018..4756a976 100644 --- a/sig-economics/README.md +++ b/sig-economics/README.md @@ -21,6 +21,22 @@ Meetings happen every [First Wednesday of the Month](https://calendar.google.com | #7 | Wednesday, August 2, 2023 10:00 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-economics/meetings/007-2023-08-02.md) | [Link](https://github.com/akash-network/community/blob/main/sig-economics/meetings/007-2023-08-02.md#transcript) | [Link](https://fc2diejm5vhix53dnrxh7dh2bflkuufterrrnmjb54ng4ojumtkq.arweave.net/KLQ0ESztTov3Y2xuf4z6CVaqULMkYxaxIe8abjk0ZNU) | #8 | Wednesday, September 6, 2023 10:00 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-economics/meetings/008-2023-09-06.md) | [Link](https://github.com/akash-network/community/blob/main/sig-economics/meetings/008-2023-09-06.md#transcript) | [Link](https://nlzzmaec3zpmorkyh3f4w3tep2hy444funhf645cqroo7x4qtusa.arweave.net/avOWAILeXsdFWD7Ly25kfo-Oc4WjTl9zooRc79-QnSQ) | #9 | Wednesday, October 4, 2023 10:00 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-economics/meetings/009-2023-10-04.md) | [Link](https://github.com/akash-network/community/blob/main/sig-economics/meetings/009-2023-10-04.md#transcript) | [Link](https://zq6rzise7b65e5o4uq2t2dgfvdu5fjj4p2aluihozhraqk7eyyca.arweave.net/zD0cokT4fdJ13KQ1PQzFqOnSpTx-gLog7sniCCvkxgQ) +| #10 | Wednesday, November 1, 2023 10:00 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-economics/meetings/010-2023-11-01.md) | [Link](https://github.com/akash-network/community/blob/main/sig-economics/meetings/010-2023-11-01.md#transcript) | [Link](https://6cjhlgaiutfckbasf6sqjbypkrhyjgll463t67f7aw3af5gtghea.arweave.net/8JJ1mAikyiUEEi-lBIcPVE-EmWvntz98vwW2AvTTMcg) +| #11| Wednesday, December 06, 2023 10:00 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-economics/meetings/011-2023-12-06.md) | [Link](https://github.com/akash-network/community/blob/main/sig-economics/meetings/011-2023-12-06.md#transcript) | [Link](https://czik4rsznmpaxems7ffmui4fiaar7waib6gtwy5jt4pptosygpla.arweave.net/FlCuRllrHguRkvlKyiOFQAEf2AgPjTtjqZ8e-bpYM9Y) +| #12| Wednesday, January 10, 2024 10:00 AM PT (Pacific Time) | | | +| #13| Wednesday, February 07, 2024 10:00 AM PT (Pacific Time) | | | +| #14| March, 2024 10:00 AM PT (Pacific Time) | | | +| #15| April, 2024 10:00 AM PT (Pacific Time) | | | +| #16| May, 2024 10:00 AM PT (Pacific Time) | | | +| #17| June, 2024 10:00 AM PT (Pacific Time) | | | +| #18| July, 2024 10:00 AM PT (Pacific Time) | | | +| #19| August, 2024 10:00 AM PT (Pacific Time) | | | +| #20| September, 2024 10:00 AM PT (Pacific Time) | | | +| #21| October 2024 10:00 AM PT (Pacific Time) | | | +| #22| November, 2024 10:00 AM PT (Pacific Time) | | | +| #23| December, 2024 10:00 AM PT (Pacific Time) | | | +| #24| January, 2025 10:00 AM PT (Pacific Time) | | | + ## Leadership diff --git a/sig-economics/meetings/010-2023-11-01.md b/sig-economics/meetings/010-2023-11-01.md new file mode 100644 index 00000000..9adca6b1 --- /dev/null +++ b/sig-economics/meetings/010-2023-11-01.md @@ -0,0 +1,392 @@ +--- +title: "Economics SIG Meeting #10" +key: "sig-economics-meeting-10" +date: 2023-11-01T18:00:00Z +contributors: + + +- Bilal Khan +- Cheng Wang +- Deval Patel +- George Pro +- Halil Kerimoglu +- Kelvin Rodriguez +- Max +- Mousum XXX +- Pyakhurel Pasas +- Robert Del Rey +- Robert Koschig +- Rodrigo Rochin +- Scott Hewitson +- SGC | DCnorse +- Tyler Wright +- Zach Horn +- Zach Ross + + +--- + +# Akash Network - Economics Special Interest Group (SIG) - Meeting #10 + +## Agenda + +* Updates since last monthly sig-economics meeting. +* Open up to community for ideas or concerns + +## Meeting Details + +- Date: Wednesday, November 1, 2023 +- Time: 10:00 AM PT (Pacific Time) +- [Recording](https://6cjhlgaiutfckbasf6sqjbypkrhyjgll463t67f7aw3af5gtghea.arweave.net/8JJ1mAikyiUEEi-lBIcPVE-EmWvntz98vwW2AvTTMcg) +- [Transcript](#transcript) + +## Participants + +- Bilal Khan +- Cheng Wang +- Deval Patel +- George Pro +- Halil Kerimoglu +- Kelvin Rodriguez +- Max +- Mousum XXX +- Pyakhurel Pasas +- Robert Del Rey +- Robert Koschig +- Rodrigo Rochin +- Scott Hewitson +- SGC | DCnorse +- Tyler Wright +- Zach Horn +- Zach Ross + +## Notes + +**Introduction and Updates** +- Scott Hewitson initiated the meeting, gave a recap of meeting #9 and any outstanding items in discussions or on-chain related to sig-economics. + +**Discussion on Provider Incentives** +- The initial phase of the incentive model may be manual and target a select number of providers for ease of monitoring and to prevent exploitation of the reward system. +- A performance-based reward system is being considered, with uptime being on of the metrics for evaluation. +- The challenges of purely algorithmic reward distribution are acknowledged, with a human oversight component deemed a solution to manage any unforeseen issues. +- The need for a robust monitoring system for uptime is discussed, including the potential use of automated agents deployed on providers' systems. +- The importance of flexibility in the uptime measurements is raised, suggesting rewards could be adjusted based on the scheduled availability of providers to accommodate various use cases. +- The discussion emphasizes the need for a consistent and accurate measurement of uptime across tools to ensure fairness in the incentive model. + +**Community Questions** +- **Question 1**: Max asked about the difficulty of using IBC denominations of USDC and if there were any solutions or discussions of native USDC. + - **Answer**: Cheng stated improving UX in the current state is probablt not advised, once we know more about the techincal implications of native USDC it will be dissemenated to the community. +- **Question 2**: Robert Koschig asked if the provider incentives framework has been created or what stage it is at. + - **Answer**: Cheng responded by saying it is still in a draft form and will post those details in sig-economics on discord. He'd like to seek some feedback or suggestions from the community. + +**Closing Remarks** +- Scott asked for any final thoughts and promoted Discord as a platform for continued discussions. + + +### Action Items + +- Cheng will consolidate the current ideation for provider incentives and post in discord for feedback. +- All are welcome to contribute! Anyone who wants to contribute please visit sig-economics in the [Discord Server](https://discord.gg/akash) + +## Transcript + +This editable transcript was computer generated and might contain errors. People can also change the text after it was created. + +Scott Hewitson: All right, everybody today is the 10th. Sig economics meeting it's a little Milestone here. + +Scott Hewitson: So for today, we'll go through some of the things we talked about lasts meeting and then go through any discussions and Discord and then I'll pass it over to chain. It's given any major update and then we can open it up per usual. So last time we kind of talked there are some questions about the idps and community pools and we kind of said that the community pool is acting as all for now. So as IDP gets further ironed out and there's some engineering bandwidth to complete it. That's when there's no real time as of right now, but it's on the horizon. Talked a little bit about bounties formalizing that a little better Tyler and I have been working. + +Scott Hewitson: On making that a better program that's coming from the community support proposal five grand a month. Andrew had a question about tracking the community pool funds for a stable payments because there is some usdc in there. It's 45 cents worth. So I'm gonna drop a query that anybody can Use to check the amounts in the community pool. Actually did it earlier and I was looking at this so if you put it in your browser, it'll show you that's akt amounts and anything IVC. It should be usdc but if you didn't know IBC tokens are non-fungeable. So depending on the route that they come they will have different. + +Scott Hewitson: IBC numbers, I don't know what they call it IVC token order. So there's that. + +Scott Hewitson: ' Let's go through the Discord. We had folks Brought up some discussion about using usk it's a kujira's stable coin. So there's a little bit of discussion in there. I know Andrew asked if If he's here welcome to talk about it. If not, anyone can straight talk about it. Let's see. What else is in here? I know Piper Dev brought up. Some usdc gas payment feature. There's some discussions about that. So if you're on the call, you want to talk about that at all or have any thoughts on that? + +Scott Hewitson: And then yeah, I think that's it from the recap and last meeting and then talking about any updates since I know in steering committee right after this, they're probably gonna bring up the proposal that's live right now. And that was a lending pool for nitron. So we don't have to touch about that. at the moment. But if anyone feels strongly we can talk about it here as well. Yeah, that's about the recap and Cheng. I'm gonna pass it over to you. if you want to give any major updates and we'll go from there. + +Cheng Wang: Appreciate it amazing update and summary There's not too much to move on my end. Excuse me. I'm still getting over a little bit of a cold. I'm like 99% just have this lingering cough. So, excuse me, if I do cough. + +Cheng Wang: Close to the mic and blow your drums out. The big thing really is going to be that I'm looking forward to that is still under development in various stages just simply because it's just distractions and things and I'm not this old person working on it. I think I internally myself Greg where I'd eating around the provider incentives program right that we talked about before and one of the reasons for increasing the community pool tax is to get the pool ready to fund these types of efforts and one of the reasons why it's taking long is because just kind of peel back the curtains and breaking the fourth wall a little bit if you will is the complications around what + +Cheng Wang: in order to launch the incentive program. We definitely want to do it. but at the same time we don't know what is exactly right without actually going out there and testing it a little bit right? So there's some internal debate around what size we should calibrate it at how Loosely we should formatted or how tight we should button it up and it's really just around those particular parameters and what is the length of time? So for example instead of Designing a super? + +00:05:00 + +Cheng Wang: There's some thought hey should we just design something very programmatic get it deployed and have it run programmatically so that there's very little manual intervention that needs to happen. The challenge to that is you need a sink a lot of design effort and potentially engineering time into getting something like that across and there's a high likelihood of that not being the correct design simply because you don't know how the market and how people will react in the wild when things are actually implemented right kind of Mike Tyson at the same. Everyone's gotta got a plan until you get punch them out and better punch than the market reminding you what's right or wrong. + +Cheng Wang: So my thought is to get something done. That's lightweight. Let's say small amount, in the tens of thousands or when the low hundreds or something like that and instead of eyes the models that we know we want in some small quantity over a set period time. Let's say three months six months nine months, whatever the case may be right? Maybe not nine months so that's a three to six month and see how that pans out. Right with the participation rate is what people say what the feedback is all that kind of stuff and just kind of pull the trigger and do something really lightweight and get the thing going. So that's currently what we're internally hashing out. I do expect this to be hash out in the next couple. + +Cheng Wang: Weeks so that we will have something to the submit for discussion and GitHub. Of course Nothing's Gonna Be I couldn't just happened, right? So we'll submit something like that and next and in the coming weeks is my hope and engage you all as well as others who aren't on this call, but hopefully we'll be reading or listening to this at some point in time for feedback. + +Cheng Wang: So that's really the big thing provider incentives getting that I think nailed down is gonna be pretty big because I think that's one of the things we're currently missing to really ensure provider stability as demand continues to be bootstrapped. Right and there's some additional incent non-sensitive, excuse me initiatives that are coming online very very quickly you guys all like the thumper foundational model training initiative that was passed some time ago right in proposals and work on that is going to hit the ground running very soon. There's some Alpha there and as soon as those things start running we'll make the announcement and of course as those things continue to progress we will track those and make announcements and share progress as we have tangible things to share. And so yeah, look forward to that definitely keep your eyes peeled and years perked for that effort. Other than that, I don't really have + +Cheng Wang: too much else in specifics to share + +Scott Hewitson: awesome Thanks for that update Cheng, going along with that, Cheng said we're trying to figure out the best way to go about provider incentives, having more minds thinking about it in my opinion is better than less mine. So if anyone has any ideas, please drop it in the cig economics or if you got something you want to show we can spin up a working group or something but really, the idea if we go high level right it's to get percent or to get providers on the network and stay on the network when demand might not be there completely. we demands kind of been + +Scott Hewitson: It's a metric that I'm looking at all the time. And when you have varying levels of demand, providers will spin down but we really want them to stay there so that when demand comes we're ready to go and it's stable. So yeah, feel free drop in Deval what's going on? + +Deval Patel: Hey, so I got a message from Discord user called Joseph. He's looking for some kind of for demo if we can give him he has some Enterprise users who wants to use the GPU and CPU for the AI purposes and they want to like a demo to Showcase where we can run the better workflow on So if we can fasculate I'm happy to facility meeting in between Akash and him right and if you can showcase him that what kind of use case we can provide through Akash for the cheap purpose He'll be happy to run a few workloads formed Enterprise. + +00:10:00 + +Scott Hewitson: That's awesome. If you could throw all that info into a Discord and cig economics, I can follow up with you me are tired even chain can follow up and yeah, I know that'd be great. + +Scott Hewitson: Thank you. + +Scott Hewitson: Let's see. So that's kind of. What I had at the moment. Does anyone want to talk about anything in between since last meeting or anything you want to bring up any ideas really? It's an open floor. Everyone here is pretty open to good ideas. or any ideas really, yeah. + +Scott Hewitson: I know I Andrew's got a question for me somewhere. If she's on no, he's not on it. Hi, what's up? + +Tyler Wright: Yeah, I know we might talk a little bit about it later. And you talked about the proposal that's currently on right now. because we have a certain amount of time and Searing committee again, we might talk about with the later, but I would love to hear I know that Huey you do a great job of responding to these discussion throws a number of people that see the potential and what a cautious today and are obviously trying to figure out ways Whether it be lending pools or economics ESC initiatives, and I just want to hear do we have a hard stance that we want to here? I know that's on the case by case basis you're respond to these people, but I just want to hear from you and other members on the call if + +Scott Hewitson: Yeah, for Yeah, so looking at the + +Scott Hewitson: Proposal right now. It's got 41% turnout. So it's reached Quorum and it's currently a no vote. I think I put my opinions. I don't know if I put in an Insider Channel or not, but really my thoughts on this they're asking it's a small amount of akt. It's like 5,000 akt and they're just using it to bootstrap lending pool. If you haven't been on nitron, I've never used it personally. I went on defy llama and looked at their stats and kind of see how much liquidity is there there under a million and liquidity across the whole protocol or whole lending protocol, you compare that to osmosis who has got 70 80 million in liquidity. So in my mind, it's like this is a smaller player. + +Scott Hewitson: they're trying to get tokens on to their platforms that people use them because the more liquidity you have the better prices you get when you trade or when you're lending you get better prices. So yeah, I mean another point I brought up was it is a small amount. and it's incentives for 90 days. So, once those 90 days are up it's like What more value is being brought to Aka I don't know and I don't know if those people keep their deposits there, I think fiber brought it up that it needs to be above the staking rewards amount for anyone to keep money there because why would you not just stake it or there's less risk and higher return? So those are kind of all the thoughts that I had around this. + +Scott Hewitson: I think I said I was 50/50 but leaning to know but then if it did pass, it's also a smaller amount smaller we do these little experiments and see what happens a little bit. So yeah, that's kind of where I was thinking Ty is that answer your question? or Cheng over to jump into + +Cheng Wang: Yeah, I go everything you said Scott. I'm in line with you completely there. I just want to add a little bit more context like I know. Sega economics here in terms of the economics effort. this is well within our purview to talk about here. So it's perfect to bring these up and in terms of where our focus and effort needs to be to really drive the Network adoption. coming from another perspective like what is our ultimate goal here at a koschi? + +00:15:00 + +Cheng Wang: Nothing right vaporware or other kind of POS economics stuff that we're all very familiar with not that those things don't have their time and place they do right exchanges taxes Etc. They all have their place and needless to save bootstrapping those things aren't easy. So, my heart goes out to I totally understand the condition that there were in it's kind of cold sore problem we have to deal with it ourselves, right and in supply and demand you need incentives for example provider incentives to help get providers on and ensure providers stability so that we can ensure that demand can come in and see hey you go into a store and you go into a supermarket and you're buying plantains, for example, you don't want the store to be empty of plantains. You want them to be on the shelves, And so those are things that we are very aware of in this kind of suicide of marketplace problem or just bootstrapping anything. + +Cheng Wang: However, at this point in time really mainstream adoption is the key right for us and focusing all of our efforts and funds towards that maybe not all but the vast majority of our time and energy on that I think is the right approach here and it's the right Focus right? Because what ultimately is going to make I mean, what is for example people in Cosmos or outside of Cosmos room critique, let's say the cosmos Hub right what utility are they providing? what is Adam 2.0 all this kind of + +Cheng Wang: Often the feedback under critique. There's nothing like super tangible, right and for a caution Network, we're doing something incredibly tangible and as hard as hell but it's finally really gaining traction now and we have incredible stuff in the pipeline coming down where our did the internally I think what I like to say is we need to demonstrate. I mean for all of us here, we probably know in one way shape or form, right but we need to show the public time and time and time again. Anything the traditional Cloud can do a cost can do. + +Cheng Wang: We believe that we know it's possible. Right and we're marching towards that every single day. We're working on this project, but it's about demonstrating that as much as we possibly can and continuing to show the public what we're capable of so, I think the Sega economics as well as all economics efforts currently should be in support of one person's opinion should be vast majority in support of that particular effort to drive adoption more so than anything else + +Scott Hewitson: I think that was greatly said I just add one last little bit to that. So I taking his whole thing and add it and Distilling it to one sentence. I think the community pool should be used only for organic Network if things that will drive organic Network spend and lending pools trading like it's kind of secondary. so thanks for all that thanks for all that Cheng and Ty for the question. + +Scott Hewitson: Does anyone else have anything they want to bring up any questions floor is open for anything? Really? + +Scott Hewitson: Yeah, Max what's going on? + +Max: Hey guys. Yeah, like you said I just had a question about the usdc on the cash and I know you spoke a little bit Scott in the beginning that depending on the channel that you use for IPC transfers you get a different IBC denim. + +Max: I wanted to know what's the plan to? address this issue and I remember hearing about maybe native usdc on a cash and stuff like this. So yeah, what are your thoughts about the usage of USBC and also for providers the incentives to use usdc or I think there's an incentive to use akit instead of usdc. Maybe around but yeah, that's about this. + +00:20:00 + +Cheng Wang: Yeah, I would say yeah. + +Scott Hewitson: changed you want to + +Cheng Wang: Yeah. Sorry, I would say in terms I'll address the incentive thing first because that's the easiest thing to address for using it was in the design of I think when you're saying the incentive to use akto or usdc you're kind of indirectly referring to the take rate, right? Because the take rate is so much higher on usdc than akt there's an incentive to use the native token for payment processing. And I think that is definitely the case especially early on right where folks are trying to especially now with + +Cheng Wang: The price action being what it is and kind of the momentum there. I think people are viewing more of a hold on akt, right then sell on AKC. So in that regard people are saying hey, what, I would like to risk optimize for more akt if I'm a provider and also I get to keep more of it because the take rate is so much lower. So there's definitely that and that was intentional in the design. I think we talked about it too right where we want to ensure that native token always has the kind of the leg up if you will in that regard usdc and other tokens are associated will always Prefer, obviously, these parameters are all changeable via governance, right and that's the whole idea of it. But I mean the original intention was to prefer higher take rates for other tokens because again it doesn't + +Cheng Wang: Because it doesn't use akt directly and we want to ensure that the value capture as well as the value creation to akt is never broken and that chain remains strong to ensure it's Implement rather a higher take rate for these other currencies and that take room goes back to the community pool. Right? We're currently in the community pool in the future some IDP sub pool, whatever it is, that adds value continues to fund the development of a caution Network, So again, I know this already Max of course, but that's just the loop right and that's the reason why that exists going forward using us DC natively, I think I don't know what the exact. technical + +Cheng Wang: constraints are precisely to make that happen what we do know for example in arguments at least whom we're close to is kava has already done native usdt via kava. So we're trying to get scheduled time with their engineering team and our engineering team to talk and understand. + +Cheng Wang: What it requires and what that kind of looks like because supporting to just understand what the technical guts are necessary to support native usdt and Native usdc right the end result. I don't know the technical bits are but the max you're so that me probably definitely but in terms of the end result, it'll be as if you're using Akash or atom or anything else it'll just be another token within Cosmos and it'll be fungible there wouldn't be usdc via osmosis on Akash, It's like and then that is only in order to get back to you as DC. You have to take it you see on Akash send it back to osmosis. + +Cheng Wang: Use the apps of bridge back to usdc in order to get usable usdc on exchanges right or something like that or to put back into your own wallet somewhere or something like that. So, we're trying to understand what the technical implications and requirements are to support your CT natively on Akash, that's step one. And that should be happening with the next week or two that conversation the very least and then from there we'll be able to better Define what are the next steps as far as building support for it? And on either right? I'm pretty sure these are core implementation, And so that's where we currently are. So once we kind of bridge that Goldberg That we're currently in this initial really rough implementation of uscc. It'll be a lot easier and things will be fungible. I think I'm pretty sure 99% sure. + +Cheng Wang: half the time + +Max: Yeah that makes sense and perfectly answers my question and I guess follow-up question. do you think it's worth putting effort right now to improve the ux to use usdc from osmosis or not worth it, since it's not very good ux in terms of IBC and non-fundibility of + +00:25:00 + +Cheng Wang: I would if I were betting man, which I sometimes am. I would say probably not worthwhile improving the ux around this current IBC denom shenanigans. I would probably in order to make a more. Well informed decision I think will have the conversation with coffee scene is AP. Like I said next week or two once we have that conversation. I think we'll be able to judge a little bit more. With the greater degree of certainty and understanding what the right path forward is for, staple coin Not true, but direct stable coin support rather than just whole hopping around thing. Yeah. + +Max: Sounds good. Yeah, I think I agree with your bet I mean if the conversation and all the details are to be talked about next week or soon enough. definitely not worth trying to + +Max: make the IVC then stuff in the department experience easier since it might be absolutely in a few weeks. So yeah, All right. Thanks. + +Cheng Wang: Yeah, absolutely or just a cleaner implementation right instead of designing around something that is suboptimal to just have a cleaner flow in designing around that I think closer to where the end State ultimately should be right. + +Max: Yeah, for sure because right now you need to know the exact denim to put in the sdl for providers to bid on it, but even us as developers, we had a hard time figuring that out. So can't imagine for anyone else. + +Scott Hewitson: Ross normal Focus impossible + +Max: That's exactly… + +Scott Hewitson: just Okay. + +Max: what I meant. + +Scott Hewitson: I'm just playing. + +Scott Hewitson: No, that was a great question. And thanks for the thorough response string would appreciate that. Yeah, Robert what's going on? Good to see you here. you got. + +Scott Hewitson: maybe he'll jump back on. Or maybe he was trying to leave and not raise his hand. there we go. + +Scott Hewitson: Hey Robert. Were you trying to ask a question? + +Robert Koschig: Yeah. He's basically to check in back on the topic of provider and this in ideation. is there already something or you really start basically from zero? + +Cheng Wang: There are some initial thoughts Robert circulating around and like I said, we'll definitely share a collated higher conviction version of our thoughts summarize and GitHub discussions before anything goes live so door. everyone will have a crack at it. before these things go live in terms of will obviously we want to Share something that is cohesive something that is well thought out and has a reasoning explained behind it. So that when we get into the discussions, right people can really pull that apart and there's not a lack of detail. That's the reason why it's like taking a little while because there's debates of how should you do this, but I think we're coming together on a closer understanding at this point. It's just about nailing down things like + +Cheng Wang: The specific GPU models, we should incentivize in this first batch because what we want to keep in mind is this is going to be the first iteration. It's not like the end all be all. So if there's a particular model not supported that doesn't mean it won't be supported later on. You know what I mean? It's just hey, there's this one thing we want to do. Let's start and do something small but quick and so then get some learnings from it and the second iteration will be better in the third fourth Etc. So on and of course not build something over engineer something where we back ourselves into a corner and spend so much time on it and effort that it ends up having to be being changed, dramatically or completely. So yeah that's where we are and we'll get out I'll put gas on that and get that shared publicly as soon as we can I'm hoping in the next week or two is guess. But yeah, just that would be the goal. So that at least the next say economics? + +Robert Koschig: Okay. + +Cheng Wang: We can have something tangible up there that will have already been subject to some amount of public discussion that we can continue to hash out here if anything. Yeah. + +00:30:00 + +Robert Koschig: That was basically like… + +Cheng Wang: please I'll see economics. + +Robert Koschig: we can start here if we want because what comes to mind when we talk about,… + +Cheng Wang: For sure. Yeah. + +Robert Koschig: incentivizing up time one model that I like a lot is Hopper. Does it live clear? Does it the probabilistic payments? And not true if you know it, but it's basically, you don't get a reward like every block or whatever but it's like a likelihood that you get it and obviously you can say If you have a certain type of GPU that we need more than the other, you're likely to this higher and you need to collect not just one, lottery this week winning ticket but five and that's over time. So it's on average if you're up all the time because you randomly send out the tickets right to and if your life you can collect it. + +Robert Koschig: And that's why you have an incentive to be alive because if you missed it because you're not up and running and you're not gonna get it and obviously the downside of all this is This is a little bit complicated to implement. I mean, you can tell that I'm not a deaf so I can only make up a fancy incentive models. But yeah, that's one component for sure that comes to mind that that feels like one idea to kind of go after the uptime incentivization besides the other constraint. Obviously that when there is demand you kind of want to slow down the absolute bucket of + +Robert Koschig: This It's just inverse to when there's actually demanded you would just cap it or even shrink it down. So you only have a Baseline and whenever there's no demand people still get this minimum in incentives and if there's demand and this Baseline emission is zero, basically + +Cheng Wang: Yeah, I think this is Definitely closer to there are some elements of that are very in line with what we're thinking as well. So hypothetically I'm a provider that I have, 10 gpus whatever the case may be in those gpus are models that the network wants to incentivize because they're important to adoption and keeping the supply on so hypothetically when those resources come on, we'll say The idea the incentives is to create a floor right? I think that's where you're talking about here where if you're earning more than the floor you don't get incent you shouldn't also double dip incentives probably right or if you do it should be something smaller. And so the idea of incentives here is to ensure that providers aren't losing money. + +Cheng Wang: Per se by operating on a cost Network so that they can continue to sustain those operations. Whatever they're kind of like break even costs are and of course everyone's a little bit different but the way we can't calibrate it to each person's like economics situation, Every providers economics situation might differ a little bit. So we'll have to use some sort of generalistic approach to parameterize it and so yeah, I think setting a floor is a huge component of this and then anything beyond the floor is going to be just + +Cheng Wang: Gravy, I think that the provider keeps and not incentivizing anything beyond that I think there's some thoughts around it as well. do we just say instead of eyes the floor? Let's say your floor is a thousand a month right in emissions and you get the Thousand no matter what and the excess you keep is or is it if you make up to a thousand in actual deployments, then you don't get the rewards at all or some small amount, So there's some gradients there between those approaches and then the other thing is definitely in the initial implementation won't be by block period because that requires programming right and Engineering effort, so I think it'll largely be limited to some small amount. Let's say 10, 20 or 30 providers, whatever maybe or chip types maybe like 10 two or three four types and maybe 10 or 20 providers something like that depending on how that's + +Cheng Wang: Framed and the economics will have to match. Those things in order for people to come online use it Is it enough incentive? So those are kind of things because what we don't want to do is overpay, it's okay A little bit especially if it's small scale, but we want to hit that sweet spot right where incentivizes people enough to join and keep on but it's not so much where people are just going to necessarily arbit right to say, what I'm getting five grand a month for these machines that I can go out and lease on some Cloud for 200 a month. Yeah. Okay, of course, I'm gonna do that, we all want to create too much of that scenario either. + +Robert Koschig: yeah, I mean that makes it almost sense and I really like also the kind of cost markup a floor anchor so to speak that's Yeah,… + +00:35:00 + +Cheng Wang: anchor here + +Robert Koschig: really good. Obviously and if you then even tie it to a limited amount of providers because then you kind of avoid the issue of if a cash token all of a sudden goes up and you don't adjust, all of a sudden you have 500 people coming in just for the farming so to speak. Yeah, that's for the things you want to avoid. + +Cheng Wang: Yeah. + +Cheng Wang: Yeah, and I think the initial implementation will be pretty manual to it'll be like, hey these 10 providers that we're incentivizing we know their provider addresses, right? And so we're going to monitor those providers for uptime and we can easily keep track of it. and not necessarily give out the rewards per blog period but her X interval whatever right by weekly monthly whatever the case may be in order to and I think manually process the processing those things will be a little bit painful in the beginning but I think it'll give us a great degree of understanding and control so that we don't get into How their algorithmic runaway scenario where one of the snare is a yield Illustrated, for example. Happens yeah. + +Robert Koschig: Yeah, but for sure interesting right to think about the way how to incentivize that time because right that the probabilistic payment stuff is more like, you put the pressure on the Node operators to be like, yeah, if you're not up, it's not my fault. You need to collect the stuff whereas there are other networks right that more we measure the uptime nimm for example, does it they have a performance factor for the rewards? So you get rewarded according to how could your performances and the performance basically is uptime. So right over the past 24 hours if you were just the ping I think in arbitrary interval and if you've been up only 80% of the time, you get pen penalized on the rewards that you would actually get if you up fully 100% So it sounds like in the beginning to keep it simple. You're more like using this type of measurement where you will just look at the actual data window when they were up. + +Robert Koschig: Is that something you could actually do also a lot larger scale more permissionless to kind of measure up time. I mean also I don't want to steer too many, spot here. I just like the discussion. So if anybody else has other questions for sure stop us. + +Cheng Wang: No worries I think you had something to go, but he had a Henry's. + +Cheng Wang: You're 100% right? Yeah, that's a great idea great point and I think in between right? So I'll collate the existing thoughts and share them in say economics so we can get the discussion rolling totally agree. I think it's a great idea and I'll do that sometimes today for Love it. Yeah,. + +Cheng Wang: Exactly public accountability. I'm gonna do it today 50% Just Let's see. What else I think wherever you asked a question previously. around Yeah,… + +Scott Hewitson: No, I was just as we're talking about this Robert really appreciate you coming in. + +Cheng Wang: I think is there a programmatic way to monitor uptime in those things like that? + +Scott Hewitson: You've been in the past two and… + +Cheng Wang: So I think A Deval was on the word,… + +Scott Hewitson: you always have good things to say. So I really appreciate that. I was gonna ask you Cheng do we have something that we can throw into cigar economics and… + +Cheng Wang: but I think he dropped but yeah as far as praeter and stuff like that that would probably lean on their Tech to monitor this stuff. + +Scott Hewitson: Discord just maybe a rough bullets of… + +Cheng Wang: I probably believe there's that kind of capability and… + +Scott Hewitson: what we're thinking, kind of how we've been going right? + +Cheng Wang: in addition to that once we know their Address right on the provider address we can easily monitor via prater's dashboard. + +Scott Hewitson: Some internal folks right some stuff and then it goes on discussions and it's all right, that's kind of the 90 percent product and then any final tweet … + +Cheng Wang: I don't know… + +Scott Hewitson: I think there's interest and… + +Cheng Wang: how far back that information goes… + +Scott Hewitson: some smart people out there that can help steer some of these things. + +Cheng Wang: because they do show you up time. I don't know if it's a two week period or whatever it is,… + +Scott Hewitson: So if we … + +Cheng Wang: but what we could do is whatever that + +Scott Hewitson: put out a 30 or 40 percent, some bullet points of this is… + +Cheng Wang: Time period is let's say it's a seven day. + +00:40:00 + +Scott Hewitson: what we're thinking get some inputs. + +Cheng Wang: I'm just throwing out a number… + +Scott Hewitson: You never know when … + +Cheng Wang: if it's a 70 period we can do rewards every seven day period right just say hey you had 20% uptime you get nothing… + +Scott Hewitson: great ideas come out and get implemented into that final or not the final but next step of discussions or… + +Cheng Wang: because you suck or you have 90% Plus or… + +Scott Hewitson: it's kind of like, all right,… + +Cheng Wang: 99% plus up time you're grades. + +Scott Hewitson: we've already made up our mind almost + +Cheng Wang: That's what we want. Then you get it and we can do some sort of thing. That's a great idea too late some sort of gradient where beneath a certain amount of uptime you don't get any rewards and some Take a percentage that you are up you get additional rewards right to incentivize greater uptime too. I think is reliability and providers. That's… + +Scott Hewitson: awesome And… + +Cheng Wang: what that does right you want someone who's like having it on all the time not On and… + +Scott Hewitson: he doesn't do it today everyone hit him up on Discord. + +Cheng Wang: off on and off. Okay. + +Tyler Wright: There's a case where maybe somebody has a100s that they need to use during the day, but then they want to make them available on a cost Network for 10 hours and they know that 10 hours is every single night of specific time and it's scheduled. We want to make sure that they're not being penalized for something. that we would want to encourage theoretically on the marketplace. I think there's other elements of the uptime metric as it is stand today that could use some tinkering but I think that as you all think about incentives up time is certainly very important, but I think it's just one piece of the provider puzzle, obviously GPU type is another piece that you all know about but I think it's just a piece of that puzzle and determining that Precision determine for incentives. + +Cheng Wang: Only with you. good point + +Max: Yeah, Thanks for bringing that up and I was aware that there was this good discussion in the signal it takes about this. But for Maybe one solution to this is that providers could specify the schedule that they want to be online and we could base Based ourselves on this to calculate the uptime. That way if it's scheduled to be online for just a few hours during the day. We can check that and also we've done some work. instead because currently the way we check the updine is just by fetching or pinging the status endpoints from providers. + +Max: And sometimes that isn't very reliable for some reason some providers are actually online, but their status endpoint they're making some changes on their DNS config in the status point isn't online, but their provider is online and they work running. and so yeah, we made some work to work towards deploying and agent on each of the providers automatically So there would be at least one deployment on all of the providers. that runs the agent and gives us the actual API endpoints that we would query on that. + +Scott Hewitson: Max good + +Max: specific deployment and we can also do some benchmarking and + +Max: other types of metrics to gather more data about the providers Which there could be used also for the incentives? Maybe just thinking about this right now. But yeah. + +Max: Maybe we can talk about it in a separate color something. + +Tyler Wright: Yeah, yeah, if you want to come to Sig analytics, maybe we can create a separate call where you pray towards some other folks get together because to your point Max at first use case. I was talking about where people are trying to Compute online for specific schedule period of time it's like a newer thing that is being explored. But the way that uptime the second point that you're making about how up time metric is taking right now is something that I think is worthy of further discussion amongst the team so we can make sure it's the same across all tools and makes sense for everybody. + +Tyler Wright: So I'll set up some time for us to talk about that whether it's next week and Sig analytics or prior to that. + +00:45:00 + +Max: Sounds good. + +Scott Hewitson: awesome Does anyone else have anything else that they'd like to bring up to the group? We've got about 11 minutes left of the scheduled time before steering committee. + +Cheng Wang: Please do definitely considering Community if you guys have the time. + +Scott Hewitson: Yeah for Already, it looks like we don't have anything else. So action items anyone who has ideas wants to contribute to The molding or developing of the provider incentives, Please drop it into Sig economics and Discord and Cheng is also going to drop kind of what the internal teams thinking about at the moment very rough. Nothing set in stone. So Yeah,… + +Cheng Wang: Don't judge me. + +Scott Hewitson: that's the big action item this one. With that, I think we can conclude today's session and as always appreciate everybody and we'll see you here shortly. + +Cheng Wang: Thank everyone for coming and participating. + +Robert Del Rey: Stay safe guys. Thanks. + +Robert Koschig: Thanks. + +Cheng Wang: As well. Bye. + +Meeting ended after 00:46:20 + diff --git a/sig-economics/meetings/011-2023-12-06.md b/sig-economics/meetings/011-2023-12-06.md new file mode 100644 index 00000000..5ddcad18 --- /dev/null +++ b/sig-economics/meetings/011-2023-12-06.md @@ -0,0 +1,190 @@ +--- +title: "Economics SIG Meeting #11" +key: "sig-economics-meeting-11" +date: 2023-12-06T18:00:00Z +contributors: + + +- Cheng Wang +- Dimokus +- Mariela Tanchez +- Max +- Robert Del Rey +- Robert Koschig +- Rodrigo Rochin +- Scott Hewitson +- Tyler Wright +- Zach Horn + +--- + +# Akash Network - Economics Special Interest Group (SIG) - Meeting #11 + +## Agenda + +* Updates since last monthly sig-economics meeting. +* Open up to community for ideas or concerns. + +## Meeting Details + +- Date: Wednesday, December 1, 2023 +- Time: 10:00 AM PT (Pacific Time) +- [Recording](https://czik4rsznmpaxems7ffmui4fiaar7waib6gtwy5jt4pptosygpla.arweave.net/FlCuRllrHguRkvlKyiOFQAEf2AgPjTtjqZ8e-bpYM9Y) +- [Transcript](#transcript) + +## Participants + +- Cheng Wang +- Dimokus +- Mariela Tanchez +- Max +- Robert Del Rey +- Robert Koschig +- Rodrigo Rochin +- Scott Hewitson +- Tyler Wright +- Zach Horn + +## Notes + +**Introduction and Updates** +- Scott initiated the meeting, gave a recap of meeting #10 and any outstanding items in discussions or on-chain items related to sig-economics. + +**Discussion on Provider Incentives** +- Cheng highlights internal progress in developing provider incentives, focusing on key aspects such as the size of the incentive, its duration, and specific targets, despite limited public developments. +- A potential pilot campaign is being discussed to gather data and inform future strategies, with a debate over starting small (around $100K for 30-60 days) versus launching with a larger pool (potentially $1 million) to ensure sufficient participation and rapid progress on the demand side. +- The current inclination is towards a larger incentive pool to attract premium tenants and providers, with a 60-day duration deemed optimal. The initial focus will be on high-performance chips, with future incentives adjusted based on the pilot's findings. + +**Exploring Token Engineering and Simulations** +- Scott suggests involving token engineering communities for simulations and scenario planning in token distribution. Although not an expert himself, he sees value in using bounty funds to hire someone skilled in this area for better understanding and planning. +- Cheng agrees with the idea, emphasizing the importance of sharing the outcomes publicly if community funds are used. He suggests modeling various scenarios, like token distribution and its impact, to engineer positive behavior among providers and avoid market dumping. +- Robert Koschig, a practitioner in the field, offers to introduce experts, and they agree to discuss further details, offline. + +**Further Discussions and Closing Remarks** +- Cheng describes the thorough validation and testing of tenants, ensuring demand is met before launching provider incentives. He mentions overcoming old system limiters and preparing to meet the increasing demand for resources, particularly GPUs, to support potential pilots and applications. +- Cheng highlights the network's commitment to openness and transparency, contrasting it with other projects that rely on hype. He suggests a challenge to other projects to disclose their actual utilization and deployments, emphasizing their practice of openly sharing statistics and real usage data. + +### Action Items + +- Scott will contact Robert Koschig to learn more about token engineering and all the work he is doing in the space. +- All are welcome to contribute! Anyone who wants to contribute please visit sig-economics in the [Discord Server](https://discord.gg/akash) + +## Transcript + +This editable transcript was computer generated and might contain errors. People can also change the text after it was created. + +Scott Hewitson: All right everybody. This is the 11th. I think economics call. last month, we talked a little bit about provider incentives went through, kind of the chat and Discord if there's anything that was going on in there since our last call from a proposal side the community events signaling proposal pass. That was just a text proposal. So it'll be a community spend one for that coming up soon. and yeah, not a ton of + +Scott Hewitson: traffic this month or since the last call, but I'll kick it over to Cheng if you want to add any provide any updates on provider and Sinners and mind you after last call he put in a message into Discord and Sig economics where you can read it's all work in progress, but just to see where we're thinking where we're headed. So with that all I'll pass it over to Cheng. + +Cheng Wang: Thank you as always so hey everyone welcome in a little bit of a crew today. But hey, it is what it is hard things usually have fewer people wanting to volunteer for it either case in terms of Provider incentives. That's really the big thing that I think has gotten the most progress internally. Though there hadn't been a lot of public progress in terms of pushing the prop live or pushing a discussion. Excuse me live first, right? There was a lot of internal ideation around it. So the initial and I'll kind of appeal the curtains back a little bit to kind of bring people into that discussion and kind of the reasoning behind and one of the big things around the provider incentive discussion was really three or four three hours a characteristics one was size. + +Cheng Wang: Of the provider incentive right number two is duration how long we're gonna run it for and number three would be what specifically we want to incentivize So those three things are really really important in terms of the size. I think that's the probably size and durations size probably is the most important thing. The original thought is we're will definitely go with the pilot proposed the pilot around in other words run like a campaign initially to see it's one of the purposes will be to gather data right understand what the engagement looks like understands public response to it and understand ultimately how the + +Cheng Wang: How it will perform right and that will help inform subsequent iterations of either another test campaign whatever it is or full-fledged ones and initially these campaigns will all be done manually, right and ultimately we don't want to put anything on chain or write code against it because we quite frankly don't know how they actually should be designed on a go forward basis that can be repeated. again, and initially it'll be a lot of fact finding I haven't done so in terms of the size of the campaign itself + +Cheng Wang: There were two schools of thought either go really really small and small here relative terms, I think initially we're thinking 100k or so as far as incentives stretched over a month or two 30 to 60 days, right? And then there's their pros and cons the pros that it's small it's low risk, but the con of it is and I think it's quite a big one, which you won't get a lot of participation right? Because there's the amount of so tiny especially anything about incentive advising potentially a 100 chips. You're not going to get too many. And we've run into so for example the thumper exercise, right that's currently being done in completed is a 50 to 60,000 exercise and that considered small in So if you do a 100 km pool + +Cheng Wang: One Thumper comes in or even that one and a half commitment in the entire pool will be exhausted as far as resources. So going small really I think potentially pigeon holes us into a corner that we don't want to be pigeonholed into So you want to have been able to have more on the shelves right for people to come in if we want incentivized demand and the supply, excuse me. The other side of it is Beyond the other side of it is launching with a bigger size. + +Cheng Wang: enables us to move more quickly on the demand side and engage with Partners engage with potential cost customers and get them using Akash more quickly. because a lot of the partners that we were currently talking to right now will come in and say hey we want to do something we want to experiment we want to do proof of concept. We're great we walk them through we show them how to set up a wallet. We shouldn't have to use cloud most which has been, absolutely Kick-Ass right? But then they run into the thing how many resources do you need to they're like, we need 40 50 XX whatever it is, right the resource. we currently have a fraction of that. So we definitely want to be able to move quickly because the space moves very quickly. And so if we go too small in the beginning, We don't generate the momentum. We want to generate we don't get the size of Supply that we need and three we might put ourselves behind the eight ball, right because the space moves quickly if we + +00:05:00 + +Cheng Wang: Don't act ourselves and be the first movers and leaders in the space that we currently are. Someone will pass Us by right at some point in time. So we definitely want to and essentially hear. If tldr go big or go home, right? So I think the thought process at this point now has been I think rightly tuned towards a much larger pool probably in the million dollar range right pilot for 60 days and incentivizing a group of three probably high medium low-end Data Center Grade gpus right and 100 something like 100 at the high and 80 gigabyte. We wanted to find what the specific parameters are around that and audit It ultimately right be able to see all that stuff and the cloud most imperature guys, like the tools being brought on board. There will be instrumental in helping us validate. A lot of the stuff in addition to other things will have to do + +Cheng Wang: that part one and then in the middle tier, I think a6000 or something of that ilk and then in the lower chair, I'm not sure whether it's viewing hundreds P40 something like that t big x-ray whatever the Chip might be so that's number one in terms of Probably in the million dollar range to really get enough Supply onto the network. So that more than one Premiere tenant. Hopefully handful maybe more Premier attendance can really come on and use the network right and really put it through its paces and see the network. Scale number one number two. + +Cheng Wang: the duration is probably 60 days 30 likely too short to really get any sort of significant data. And for this thing to kick off, 30 days sounds like a lot but I don't think it's enough. So 60 days is probably going to be The Sweet Spot there and as we get data and information coming through we'll be able to fast follow with a secondary pilot or just a second iteration program focusing on something a bit more specific. + +Cheng Wang: Whether it be a higher high-end chip medium and low and whatever the case may be that second tier incentive will be tuned towards one of the learnings or Google learnings that we extract from the initial campaign. so we talked about all three things right like what specifically there's an advising. So that's being hashed out. what should be the three I think the first tier is pretty obvious a 100 80 gigabytes. Probably reason for that is they are the highest performance chips. That are also the most effective level, right? Because if you go at the upper end with h100s sure they're the most performed that are also the most expensive and the hardest to come by because they're the newest or the most demand and also they are + +Cheng Wang: There are fewer simply by virtue of having less time on the production line, right and be more complicated complex to manufacture all that stuff. so that's at the high end and one of the open up or pause there for the time being and just sharing, that's a bit of information with everyone here and for imposterity as well + +Scott Hewitson: I got a question. So it sounds like the first iteration or… + +Cheng Wang: Far away man. + +Scott Hewitson: two, it's manual. It's kind of do a big but we're also learning do you? Personally see any value in bringing in there's these token engineering communities and people that do simulations and all sorts of cool stuff. Maybe it wouldn't be as applicable to one of the earlier rounds but I've been thinking, we've got Bounty funds there's tons of mechanisms we can find someone that's good at, the token engineering we can play out different scenarios and run simulations. And I mean, it's not my area of expert I am very interested in it, but I just don't have the time to dive into it. I just wanted to get your thoughts on that. + +Cheng Wang: I think it's a great idea to bring people in and people want to volunteer and especially after because we're gonna share all of this data because it's using public funds right the community pool. So the onus is on us to track all this information and ultimately share it right with the community one put it all together collated and share that data will ultimately be presenting on and sharing it across, the internet right so that people can see what's going on there. So I think modeling now what potential different ideas even right and in addition to simulations would be very very interesting. So for example, what we don't want ultimately so distribution for example, right as you distribute token rewards to + +00:10:00 + +Cheng Wang: providers that come and qualify for this program They will either view akt as a specular speculative asset in which they will hold right for whatever duration whatever else or there are some that will just say. Hey, this is a cool thing that I got. I'm going to cash it in right away and sell the tokens, right? so + +Cheng Wang: we don't want is a case where you get a bunch of incentives and Alum sum whether it's a per weekly weekly and a monthly basis whatever the case may be right and just end up dumping it into the market. That's one area where we don't want. So one mechanism that we could introduce is a bonding curve right to say hey, if you get these rewards you can choose to extract them the same day and you'll get some number or you can wait a little bit longer and you can get a tiny kicker or something like that right different scenarios. We can definitely model out and think about and that way to essentially engineer Behavior, right? I'm encourage certain types of positive behavior and feedback loops. So that what I mention is by no means a direction we're going but those are important discussions and I think also have so totally agree we should + +Scott Hewitson: Yeah. Yeah,… + +Cheng Wang: engage anyone… + +Scott Hewitson: I mean that's a variable that you could put into the simulation. + +Cheng Wang: who wants to do that + +Scott Hewitson: You can put in inflation you can put in what you think, Community put proposals there's all these variables parameters that you can put into ting this simulations that it's like if we want to add something we can add something so I'll do some. + +Cheng Wang: Totally is there anyone here that has that or wants to do something? + +Scott Hewitson: I know Robert koschig is familiar with it. I don't know if he's practitioner Robert is here today. Yeah. + +Cheng Wang: practitioner + +Robert Koschig: Yeah, I mean I am practitioner and I could for sure introduce you to some folks and token engineering the area. It's interested. + +Scott Hewitson: That would be great. I think the other thing is I don't know how much it costs to have to commission someone to look into this too. I don't know if it's a couple hundred bucks a couple thousand bucks so that would be very helpful to we can talk offline if you want to DM me or I can DM you in Discord if that's all right. + +Robert Koschig: Julia + +Scott Hewitson: Okay. appreciate that + +Scott Hewitson: I remember talking about it in the past. So that's why I brought it up. + +Cheng Wang: Yeah, definitely. + +Scott Hewitson: Does anyone have any other comments questions or concerns about anything that Cheng said and if not, we can open it up to general questions concerns, okay. + +Cheng Wang: I don't have a question for myself. However, I do have something I do want to share all so is this on GitHub? No, not yet Max. So this is something that we just talked about lightly last time in Discord and in Discord and cigar economics Channel within Discord and just in these particular live and conversations. So not quite yet and we will push this to get help discussions a hundred percent but internally one we hold some out because it's been this kind of pulling and pushing back and forth. Should we do that? There's a little bit and it's just kind of all over the place and naturally We want to be able to think it through very carefully right and do it the right way and inherently, I'm a little bit more conservative and saying let's just do a smaller pool, but then there's when we open up discussion internally. It's like + +Cheng Wang: Does going small really achieve what we want to achieve right? Because if you think about when you launch let's say you have a supermarket or clothing store, And there's a grand opening to the store. Do you stop the shelves full of stuff? So then people come in they see they have things to buy that's kind of the idea here. Whereas if you go small you're like, hey soft opening you can only buy one t-shirt and your left sock here. do you really want to go into the store? Right? So + +00:15:00 + +Cheng Wang: here's the reason for we want to be able to stock the shelves with ample amount of gpus that we have high conviction will be used right and do that and at the same time where we want to before we launch the provider incentives one of the reasons why we've been so careful is you don't want to launch incentives prematurely without demand that's been qualified. So now we're getting to the point where okay, we've seen all the training can be done fine-tuning can be done. All the inference stuff can be done right now. We have confidence in all of these things can run and through the thumper exercise. We ran into historical ancient limiters that we had initially put on the system before the network launch because we want to make sure that there wasn't a workload that could break potential. We don't know if it would or wouldn't try but this is four years ago, but through the thumb for exercise we unveiled right we ran into. my God these ancient limiters that we put on in terms of + +Cheng Wang: Number of resources that can be requested. I'm sure very well right Max and so Be able to peel that away if we have launch all these incentives and stuff like that and people came in and ran into this issue. what the f*** I can't do what it is I need to do this is terrible, That would be a horrible look so we got to the point where we really feel tested all of these rather use cases and now we are talking to more and more people and they're telling us. Hey, we want to run a pilot but + +Cheng Wang: you ain't got enough chips. So we're like hold our beer. We'll be back. we're gonna get those chips. We'll talk to providers A foundry's been Right and we'll incentivize at this point in time. Right caution network has gone to the point. It is now So with incentive now, we will be able to ultimately get a lot more demand and use on the network and just showcase really start to Rev that engine right and push on the RPMs if you will. The other thing I wanted to mention is regarding I guess it's somewhat data-driven is in talking to Partners and talking to just people in the biz if you will in general. + +Cheng Wang: One of the things with the cost Network that is absolutely amazing is our openness and building openness and planning openness and coordination our statistics usage again, shout out to Max and the Max's and the Prater team and making all of that possible as far as the stats available and the network a lot more usable and Powerful right having said that of it's interesting because I don't know how you guys are familiar with shooting yours cat, but I feel like it's like schroding or stats for us right by virtue of us having our statistics completely in the open. We can be asked we can't lie. We can't hide behind anything in the The stats are and so as a result people within crypto who's typically have been working and operating on the hype and their projects out there that are deep in space. I don't need a name names right you go out there. You can find stats about them close Source. They don't build any open. You don't know what their usage looks like. + +Cheng Wang: All you can rely upon is just hype and your imagination, right and as a result of that people's imaginations run wild in a positive and as well as a negative and when it's overwhelmingly positive it can bring those projects up to whatever Heights they are at despite not having fundamentals to back it up. versus for us we're doing things openly and in the right way, right and having the statistics themselves allow people to I think look at us with a far more fine tooth comb and what I want to really get across in this freaking Soliloquy here is to say + +Cheng Wang: it'd be cool to go out there and challenge other projects. what is your actual utilization? How many deployments you got running? what workloads do you have? because we'll show us yours because we show everyone hours. That'll be a cool challenge, I think. + +Scott Hewitson: Thank you for that soliloquy. + +Cheng Wang: slash and rant + +Scott Hewitson: I think there's a lot of good stuff in there for sure. + +Scott Hewitson: So going off of that. Does anyone else have any other comments or concerns can be completely off the topic of Provider incentives, anything anybody wants to talk about the floor is now open. + +00:20:00 + +Scott Hewitson: All if nobody has anything they'd like to say right now and you might think of it, in an hour. So please drop it into Sig economics and Discord. I want to try to keep the conversations going there. And as always appreciate what everybody does and with that. I think I'm gonna end the call any last things. + +Scott Hewitson: concern + +Robert Del Rey: Thanks Cheng. Stay safe everybody. + +Cheng Wang: You see Robert. Thank you. See everybody. + +Zach Horn: Thanks guys. + +Zach Horn: Take care. + +Cheng Wang: Take care. + +Meeting ended after 00:20:48 👋 diff --git a/sig-providers/README.md b/sig-providers/README.md index f93a19e4..53d11d8b 100644 --- a/sig-providers/README.md +++ b/sig-providers/README.md @@ -24,11 +24,22 @@ Provider SIG covers everything pertinent to Providers on Akash Network. This inc | #7 | Wednesday, July 26, 2023 08:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-providers/meetings/007-2023-07-26.md) |[Link](https://github.com/akash-network/community/blob/main/sig-providers/meetings/007-2023-07-26.md#transcript) | [Link](https://uhtiiuhhwfdou4iqzzpavcyys5zi7o7zkm4surfahhhqvogmkxia.arweave.net/oeaEUOexRupxEM5eCosYl3KPu_lTOSpEoDnPCrjMVdA) | #8 | Wednesday, August 23, 2023 08:00 AM PT (Pacific Time) | Coming Soon | Coming Soon |[Link](https://nx67v3sczxu3p7okp6c2gjo3npkxrm77kehza2upyyolb3qzi4sq.arweave.net/bf367kLN6bf9yn-FoyXba9V4s_9RD5Bqj8YcsO4ZRyU) | #9 | Wednesday, September 27, 2023 08:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-providers/meetings/009-2023-09-27.md) |[Link](https://github.com/akash-network/community/blob/main/sig-providers/meetings/009-2023-09-27.md#transcript) |[Link](https://c5g4xir7o2v6il2syhpnqgaooslncply3whcz64ykkn4anqppzha.arweave.net/F03Loj92q-QvUsHe2BgOdJbRPXjdjiz7mFKbwDYPfk4) -| #10 | Wednesday, October 25, 2024 08:00 AM PT (Pacific Time) | | | -| #11 | Wednesday, November 22, 2024 08:00 AM PT (Pacific Time) | | | -| #12 | Wednesday, December 27, 2023 08:00 AM PT (Pacific Time) | | | +| #10 | Wednesday, October 25, 2024 08:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-providers/meetings/010-2023-10-25.md) |[Link](https://github.com/akash-network/community/blob/main/sig-providers/meetings/010-2023-10-25.md#transcript) |[Link](https://2aefpzwgiwj6jzkl5fdsn7us3pjprpnpkoqqrrsu6bjaukktnxya.arweave.net/0AhX5sZFk-TlS-lHJv6S29L4va9ToQjGVPBSCilTbfA) +| #11 | Wednesday, November 22, 2024 08:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-providers/meetings/011-2023-11-22.md)| [Link](https://github.com/akash-network/community/blob/main/sig-providers/meetings/011-2023-11-22.md#transcript)|[Link](https://2ubf2cciht62e3qpxjur4h3ihccbyk6v2hbanktvxq2wcnifp5sa.arweave.net/1QJdCEg8_aJuD7ppHh9oOIQcK9XRwgaqdbw1YTUFf2Q) +| #12 | Wednesday, December 13, 2023 08:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-providers/meetings/012-2023-12-13.md)|[Link](https://github.com/akash-network/community/blob/main/sig-providers/meetings/012-2023-12-13.md#transcript)|[Link](https://ro5kevc2mbgfpzyb7ufa5bor6thecu23sbzrqrham53ivpiljp2q.arweave.net/i7qiVFpgTFfnAf0KDoXR9M5BU1uQcxhE4Gd2ir0LS_U) | #13 | Wednesday, January 24, 2024 08:00 AM PT (Pacific Time) | | | | #14 | Wednesday, February 28, 2024 08:00 AM PT (Pacific Time) | | | +| #15| March, 2024 08:00 AM PT (Pacific Time) | | | +| #16| April, 2024 08:00 AM PT (Pacific Time) | | | +| #17| May, 2024 08:00 AM PT (Pacific Time) | | | +| #18| June, 2024 08:00 AM PT (Pacific Time) | | | +| #19| July, 2024 08:00 AM PT (Pacific Time) | | | +| #20| August, 2024 08:00 AM PT (Pacific Time) | | | +| #21| September, 2024 08:00 AM PT (Pacific Time) | | | +| #22| October 2024 08:00 AM PT (Pacific Time) | | | +| #23| November, 2024 08:00 AM PT (Pacific Time) | | | +| #24| December, 2024 08:00 AM PT (Pacific Time) | | | +| #25| January, 2025 08:00 AM PT (Pacific Time) | | | ## Leadership diff --git a/sig-providers/meetings/010-2023-10-25.md b/sig-providers/meetings/010-2023-10-25.md new file mode 100644 index 00000000..63e11c40 --- /dev/null +++ b/sig-providers/meetings/010-2023-10-25.md @@ -0,0 +1,375 @@ + # 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 +- Cheng Wang +- Damir Simpovic +- Deval Patel +- Julius Haus +- Rodrigo Rochin +- Samuel Walker +- Scott Carruthers +- Tyler Wright +- Zach Ross + +## 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** + +_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 provide a special interest group monthly meeting number 10. During these monthly meetings. We discuss all things related to the provider on the Akash Network. We usually get a large participation of folks that are supporting providers and Beyond so much appreciate this group. I know there's also been some community pool. That has been granted to the pretor team for a lot of work that they've been doing over years of again building quick and easy tooling for those are trying to become providers on the Akash Network. So we monitor the work that they've been doing in the progress that they have whether it be related to basic pray to our functionality or specifically some work that's been coming out of the working group for the content moderation and some of the API work that they've been doing. + +Tyler Wright: I know that Benjamin's also here and talked about a topic that he wanted to bring up related to auditing providers. And so I do want to give him some time to talk and give a presentation if If there's anybody else that has any specific action items or talking points that they want to bring up feel free to do so. Go ahead Deval. + +Deval Patel: Yeah, so I'm getting ready for the partial demo of the things what we are building right? Meanwhile if somebody can go ahead and do something. I mean give the demo benjaminers here off whatever he wants to show for next five ten minutes, That could be nice right? Meanwhile, I can prepare the provider to I'll show you guys something, okay? + +Tyler Wright: I appreciate that. And I just want to shout out. I don't know how public this information is, but I believe developed a new father. So congratulations on that. I know it's been a hectic time for you over the past couple of weeks. + +Deval Patel: Yeah, thank you. + +Tyler Wright: Congratulations. + +Tyler Wright: excellent Andrey I know that you've been working with a number of folks in the community and again we've gotten some updates recently from Andrew Mello. I was hoping that he'd be able to attend this meeting because again, he's been working on some cooling that we talked about at a high level at the last thing providers monthly meeting related to chaperone tools and some automated content moderation tools that he's been building but Ben are you able to kind of discuss what you've been thinking about and working with and get some feedback from The Specialist Group or do you need some more time as well? And then we can talk about some other topics in the meantime. + +Benjamin B: Yeah, I could take my account. + +Tyler Wright: Okay, Yeah, so I'll hand it over to you and you can walk us through what you've been thinking about. + +Benjamin B: also + +Benjamin B: Can you see my screen now on Discord? + +Benjamin B: awesome I don't have much of a presentation really and… + +Tyler Wright: Yes, yes. + +Benjamin B: I don't really have that much to discuss. I'm hoping that people will come with feedback or questions. But basically me and my brother we created a small. proof of Concepts we created an idea for how a track providers Automatically we could track their online. we could train that we could Benchmark them. And we could save the historic data to using other systems. + +Benjamin B: And our hopes for this product were to create an auditor that automatically all the time on the different levels. So let's say how the Other deployment in mind you don't really care about uptime being close to 100% but you still want it to be on a somewhat reliable provider. So what we could do here we could have. + +Benjamin B: this related to this we could have something like if a provider has been online more than 90% We can sign them with one address if they have been online. 95% we could sign them with another address and every piece of data we can collect we can create. One address where we sign them for that and then you could create really flexible filtering. We would also want to eventually collect and create some historic data, so if you wanted to see How old is this provided really? This goes hand in hand with start page, by the way. Basically if you have the data in your hands or if you can access the tools. to access that data + +00:05:00 + +Benjamin B: you can make better assumptions than just trusting in auditor. Blindly, this older has signs this provider. Of course, I will trust them because I trust all that. This is not really that. and these ones are used ideas for now we Haven't even considered those that much I want to also share this video. I will share with me shout as well. I go in explaining how it works a bit more. where it is used and how + +Benjamin B: Which you can watch later the project is not active now, but if we get enough feedback if we get enough. Discussion around it and interest maybe we will restart it again. We initially created it for the hackathon. But we were very disappointed seeing there was one project created over a year ago and somehow it won the hackathon. + +Benjamin B: Was anyone have any questions or ideas? + +Tyler Wright: Thank you Again, if anybody has any additional questions comments about what then Ben is talking about, please take a look at the YouTube video that he dropped in the chat and again, feel free to leave feedback in providers. One of the main things that we're trying to do with many of these special interest groups is trying to connect people that may have whether it be businesses or pray to our team. Will there be ideas like Benjamin, and his brother are kind of trying to figure out what's next. It would be great. + +Tyler Wright: It would be great to again get additional feedback. We also have a number of folks on this call that are running providers whether it be CPU provided to GP providers on the network of various sizes so much. Appreciate everyone on this Samuel Walker left a message Ben in the chat + +Benjamin B: Do you mean where it would be host? Because if it's that case most of the services will be holding on the coach. I believe. The only thing we did not toast in a car was the front end. As well as the database but database could. Definitely be run on a coach. + +Tyler Wright: Thank you again. we're in the process of I know that out of the last six providers meeting. There's been a great job conversation around content moderation. The pretor team has been working on some content moderation solutions that they're going to be demoing over the next couple of minutes to just finalizing some things right now while we wait does anyone else have any other provider related issues comments? I know is Andre on this call. He is not too. yes. Yes. I know that andrey's been very active with folks of various sides in the community Andre not to put you on the spot. But while we're waiting, is there anything of note that maybe you want to talk about provider-wise that might be good for folks of that are running providers and they cost Network. + +Andrey Arapov: Yeah, just make sure you follow the announcements from the provider announcement in the Discord and we'll be good. Other than that I could have any issues just is normal as usual just writing a providers Channel. Let me know directly. However you want other than that providers have been running quite smoothly a couple of providers. I mentioned another call had some issues but mostly firewall related issues the nibble of block and Andrey, but they fix this issues. And not long ago damir had some Yeshiva. I believe it's related to the other attended upgrades been enabled. This kind of thing was causing a lot of havoc. For the annuity enabled providers where a media plugging was getting stuck and was causing the entire convergence cluster. + +00:10:00 + +Andrey Arapov: You get stuck on basically I couldn't remove that new deployments and those more kind of subtle issues unless you go in and check the cluster and it's solved by basically disabling the upgrades and they're putting the provider and all but three years ago. since then that time haven't had any reports related to that and + +Tyler Wright: Perfect. Thank you Andrey. + +Tyler Wright: Samuel, I know you can't talk right now. that you brought that issue up. we actually talked about this issue. There's another number of special interest groups that happened providers is obviously one that's focused on providers on the cost Network. We do have a weekly specialist group called support where we go through all the Open tickets in the support repo, which is related to core product. We triage those issues. That's where a lot of members of the Court team come together and triage any issues. We look for members of the community to see if they can help solve any of these issues and Implement Solutions via code. But again, we talk to community about specific issues that issue number 137. That's your talk about related to the providers. I believe it's a known issue. We're trying to see and we talked about this a little bit during the court. + +Tyler Wright: That might actually be a duplicate issue, but that's something that we're looking to solve in the next couple of weeks with some potential tooling. But again, I'm going to reach out to you offline and make sure that you have access to the video from the six support meeting so you can kind of see what was talked about related to one issue 137, but we can also again talk async if you have any more questions details or in cool + +Tyler Wright: guys want to mention the ball and all the work that he and degar have done with pretor which again is a easy way for folks that are trying to set up a provider to do so be doing tool the prey to our team has worked very closely within the community group structure working within again, some of the inaugural working groups around content moderation as well as being a large contributor in sick clients and providers. So they've been again working very closely with members of the community and the core team they've been very active during test Nets, obviously as we let up to mainnetics there was a lot of work that had to get done. + +Tyler Wright: For folks to be able to deploy gpus on the Akash Network a number of folks that think over 50% of the community uses. Prey towards a tool versus the CLI to set up a provider. So again, the Preorder team is very Hands-On very communicative and really a great support in helping during that test that period and Beyond so just want to shout them out before they show all the progress that they've made on content moderation. + +Deval Patel: Thank you Yeah, so in gender content moderation, there were three things to moderate at this point of time. the wallet addresses second was images and that is A host means of where the URLs to be hosted and stuff like that, So first thing I wanted to show you guys in terms of wallet blocking, right? + +Deval Patel: Through the deploy tool cloudmos, what I have done is that we have deployed our modified version of Provider service in this left hand side what you can see These are the logs, right? And basically from the locks you can tell right what you can see basically here are particular line and I'm going to highlight this right' this wallet address is the only wallet it is allowed but found this wallet address, right so somebody tried to deploy something right, but we got created because that wallet address is blocked, And yes, as you can see here, right? I'm going to do the same thing here read apply to + +00:15:00 + +Deval Patel: Yeah, so as you can see here, these are two lines, Which matters right which is blocking the wallet address I know that the wallet address blocking is there right in + +Deval Patel: Price scripting right but we are replacing this with the allow list as Right which is going to be implemented soon as well as this one, right? So yeah it's similarly applies the rules that here. We are blocking it. Right? And other thing is that where we can allow specific qualities only to be hosted on the provider. So those things gonna happen right as you can see here right now, we are blocking it. Right but similar things you can do is that we can allow the wallets to be there. So yeah, that's number one thing what we have done And as can you be able to see that not our provider has been here Our provided is something Neo doctors.com, right which is not here and it's on my favorite list as well. Right? So as you can see + +Deval Patel: sign of Provider here Yeah, so that's something what we did for the blocking the car allowing the wallet address. I'm going to close this list and switch over to the wallet address, which actually allows. + +Deval Patel: Of the wallet address, And as you can see here, this wallet address here right is ending with KJ and zero seven, right and here it says clearly that only this wallet interest is allowed to be hosted on this Provider right cage engines and 07 right? + +Deval Patel: Im let me deploy. This one because I want to show you something else but on that too. remove this accept list for now right and going to go with the employment + +Deval Patel: In this case, what should happen is that should complete means our bid should come here, right and you will notice that We do not have any error at this point of time There should be somewhere a bit complete message. + +Deval Patel: It because of some RPC. Let me just That happens sometimes I'm not sure but I'm going to talk to Andreas that so yeah, there was some bug like we came in right and the fabric I'll show this thing to entry after the meeting. for Scott + +Deval Patel: Yeah here it says the build field But here I can see my provider actually made it. Anyways, I'm going to accept this page for now, right because this purpose the segment of the demo is to show you guys that we are blocking the image right any image right now, just to show you guys the demo right? We have blocking the image, which is a calculatics actually right anything to do with the Athletics. We are blocking it right not to show you guys anything with actually content or something, right? So we are blocking the accusatics thing. once we deploy + +Deval Patel: so here, It says the error while sending the Manifest for the provider image name contains the accolatics which is not allowed right and that way we are basically blocking the image, right and we're not allowing manifest to be Posted on this provider So I don't think I mean no explicit content are any content which you don't like or which you don't want to like to host it right? We will not be hosted right then that's a demo for the image blocking. our image a lot Okay. + +00:20:00 + +Deval Patel: I'm going to close this at this point of time because this list will not be hosted and will not be up and running right. I want to mention here is that there is another part in the moderation API, which is called management API where provider will be able to close the lease as well. Right? And if that happens then here right now manually deploy has to manually close the lease, If that happens then provider we be able to close the lease as well. Right? And that's something it came out from the working group and we are going to implement that as well coming days. Okay, so that was a segment to which is blocking the images, right? + +Deval Patel: let if I don't have the image, which is a Catholics. Let's say I have Tetris came right? I'm going to deploy this right but notice here. + +Deval Patel: Guys, I'm going to say that anything with the case code is calm as in host name, right? I'm going to block it because that's providing my profile domain name, right? And I don't want to host anything on my provider domain basically, right other than the other thing other things can be word related on Etc or stuff like that or anything which you do not want to entertain on your provider, right that can be too. Okay. So I'm going to say here that I don't want anything to be hosted regarding anything to face.com which is why domain And going to deploy this right? So as soon as I said click on this + +Deval Patel: Yeah, it says bead Complete because I use the Allowed wallet address right? So paid is complete. I'm going to use this wallet address at this point of time. I'm into deploy the Manifest will go through this time because for it as it searches for word accostatics, which is not that right and that Trace is allowed but it will give me another error saying that host him contains a scooters, right which is not allowed at this point of time. So basically my manifest did not go through right and I can close this list because anyways this police is dormant. There is no actual deployment running behind it. Right? So I'm going to close this. + +Deval Patel: And successful scenario means that any of these things does You means I have my wallet address whitelisted. I have my image white listed, right and I'm not using the Illegal or blocked domain and that would be Predator app.com, So let's say I have the preterite.com domain name, right? And if I want to host that here right that I should be able to do that. + +Deval Patel: Yeah, so bit got complete means the page should come here. Right and I can accept speed. From my provider and going to accept it. So now the image passes the domain name passes the blocking list, right? So that should successfully deploy the project or the game. + +Deval Patel: And as you can see here, I can go to this thing or here and I can play the game, right? + +00:25:00 + +Deval Patel: yeah, + +Deval Patel: This is the progress of so far of we have made going to update the thing which can be more dynamically and allow this block and disabled things to be allowed from greater app itself. And as well as the CID tax, that's what we are looking at this point of time right now as well. As we are going to implement the management API in next few days actually and going to release this updated version of the provider service and give it to the taste testing to the core team and internal people means to me or other people can test out right and once they are happy and to the basement we can push it to the main net. That's the plan at this point of time. Yeah. I'm open for the questions if + +Deval Patel: had + +Tyler Wright: Don't have Andrey. + +Andrey Arapov: Is it like they do modify the provider code or used something else? + +Deval Patel: No, I'm being modified provider code. + +Andrey Arapov: ICI reporting to submit the full requests for the Upstream. + +Deval Patel: Yes, we are going to submit the pull request as soon as we had done with satisfactory with the dynamic codes in terms of cids updateable as well as we are done with the allow and block list both and things like that. It will take a couple of days. + +Andrey Arapov: Okay, fantastic work. + +Deval Patel: But yes, we are going to put the question. + +Andrey Arapov: Thank you very much for the main come for work. Looking forward to pairs. + +Deval Patel: Yeah, thank you. So that the plan like we did this and I'm not sure and it is here in the call or not. But what we would like to do like we would have liked to do is that we would have gone to the provider service you wanted to understand how to provide a service code is written and things like that and that way in future if anything happens if there is a more work towards the coordinator service and if we are able to contribute then we would be able to conflict we would like to contribute that was the nature of this exercise to do. + +Tyler Wright: Yeah, I think Deval to that point. I believe you have access to a + +Tyler Wright: Issue inside the Akash project roadmap specifically for Content moderation. I know a Neil would like to been here… + +Deval Patel: Yeah. + +Tyler Wright: but has a conflict today. If you can update that issue with some of the things that you mentioned here and then I'm going to drop in the notes in the video. That'd be great reference point. So a Neil can catch up and get next steps and we could talk about again further support of provided services and content moderation. + +Deval Patel: Absolutely. + +Tyler Wright: Benjamin National sorry had your hand up. Go ahead. + +Tyler Wright: Yes, I was going to bring those up much appreciated. I had these to the notes but Ben dropped in some strategies that I think he created around the price script that might be worth looking at them. And again, I think members of the core team also be looking at those and then Benjamin asks sdl can be valid with a lot of weird characters that are not recognized could apis be circumvented by some weird characters and that's something that Andrey was all so mentioning you might be worth testing. To follow the ebony direct comments related to testing some of these nuanced cases with weird characters. + +Deval Patel: Yeah, so our proof take this request and consultation as Right and our priority will be fulfill whatever the work came out of the working group first, right? Once that is done hundred percent, We will entertain all the requests which comes through this call or any means right and we will examine that our real need of that and we'll make the call definitely. + +Deval Patel: I hope that answers you. + +Tyler Wright: Perfect. Yeah, thank you very much. Does anyone else have any questions about any of the updates that the prior team has been working on as pertains to contact moderation and management in moderation apis? + +00:30:00 + +Tyler Wright: cool + +Tyler Wright: I want to be conscious of folks time, but I do want to because there are so many important members of the community here, especially on the provider side. I do want to see if there's any other topics related to the provider experience that anybody wants to bring up now, again, there's so many talented folks here that are running large clusters of either GPU providers have been on the network for a long time and maybe some of if not the first gpus to be run on the network again. I'm not gonna call anybody out by name and But there's a number of people in this call that are very intimate with the provider experience. I just want to see if there's any other talking points any other topics worth discussing or anything next that should be potentially a high discuss and point after content moderation that anybody wants to start to bring up right now. + +Damir Simpovic: May I sorry I didn't raise my hand. + +Tyler Wright: Of course. No, go ahead. + +Damir Simpovic: so hi folks. What happens if? somebody just clones the image in for instance. We saw now that you're blocking the akashlytics what happens if somebody just takes this image renames it? + +Damir Simpovic: just uses the same exact image. But it has a different name. + +Damir Simpovic: I'm guessing that that image would still run. But yeah. + +Andrey Arapov: Yeah, damiro. I think you're pretty much right. I think that they are escaping based on the image name of this room, and I just want to mention that the other day. I was trying to run o. My minor on Foundry provider things is here. And they basically were just killing the process even when I found into the typical simply Ubuntu image container running and then I just like run XM rate. I was just getting killed. So there are some systems that can be employed in your very faster. We should be monitoring this kind of things and I'm not sure exactly what solution they are using. Maybe is that can give such some more lights on that nice. + +Deval Patel: Yeah, so on that part, I think the tooling what I entry model had right would be helpful or that is now I think under Community as well. Right and we can expand that are to address the school. Another thing is that let's say we are going to give the management API where they can look into the content of the + +Deval Patel: Image are things like that. Right and they will be able to close that as well. + +Tyler Wright: I saw Zach put a message in the chat. Zach are you or any other providers currently using The Chaperone service from Andrew Miller? I know that Andrew has it running on some of his providers, but I just want to see if anybody else's been able to run it and has any experience with it. Hoping Andrew would be on this call. + +Zach Ross: Yeah, I've been running it for the last couple weeks actually. + +Tyler Wright: excellent + +Zach Ross: Let me pull it up really quick. But basically it in its current state will look for specific images file types and… + +Tyler Wright: Yeah. + +Zach Ross: processes and delete the namespace for the lease if it doesn't like what it sees with respect to you can list out your own kind of file types to look for. so + +Zach Ross: for example My company was not all that enthusiastic about some of the Ubuntu images that were being run on our provider that were kind of playing around with SSH Keys. It looked like so I was able to ban any kind of sshd file types which on the one hand has caused good acting leases to get terminated. but I think it allows us to be able to worry a bunch less. Like Andrew said on the last meeting. + +00:35:00 + +Tyler Wright: Excellent. Thank you very much Zach for timing. I appreciate that. + +Scott Carruthers: Is Zach I'm sorry. I think I missed the very beginning part of that. what was the necessity for images that are including SSH + +Zach Ross: so it checks for The Chaperone service checks for keyword files image names and general processes that are going on in the cluster. let me link the file to you guys. I can find it really quick. a bareback + +Tyler Wright: No problem. Again, while Zach is handling that if anybody has any other topics of discussion again, this has been a very active group. I would love for there to be a priority list of things that folks on the provider community on the cost Network want to handle obviously Beyond content moderation. There's a number of things that I think that can be improved or go ahead Zach. + +Zach Ross: Yeah, so just linked it right there. Another thing that + +Tyler Wright: Zach, Your signal might have broken up a little bit. + +Zach Ross: it's + +Tyler Wright: But I can hear you again. Maybe it's just me can anybody there? But anybody else have any issue hearing Zach? + +Deval Patel: Yeah, I think in broker. + +Scott Carruthers: yes it cut out for a minute, but + +Zach Ross: Sorry about that. Yeah, so I was looking into some pod security standards and… + +Tyler Wright: That you're good. You're + +Zach Ross: least deployments on Akash run the containers as the root user. And I think that was a consideration that my security team was kind of interested in preventing. So I looked into certain mutation policy where we could actually just have kubernetes by default adjust the root user to another user for when these containers are spun up. And I was struggling to find any mutation policy, but there's some good validation policy available. I was just curious kind of what your guys's thoughts are on maybe making some Network changes to Create a separate Akash user for all these container deployments. + +Scott Carruthers: Do you have any thoughts on those regards? + +Tyler Wright: right + +Andrey Arapov: If the question is to make sure they're through users blocked for the user deployments so they can just deploy anything except for the root user. For that there is some security policy cells sharing the other day. It's possible to Implement on the community level but on the level of cash. it has to be a future request basically because all things need to be changed. such as Docker image to the specify the user and this things need to be checked as well. So it's more of a deeper consideration and probably worth starting up some discussion in the cash Repository. + +Andrey Arapov: With the use case and these things like Mr. Be drafted there and the other question is that is the default user root or not. But I think it's the other question. believe because normally all the processes are running as root in the system But whenever a user runs something in the container, it is a root process. There is also remapping possibility of the user IDs. But it's also another thing and it has all drawbacks. So yeah, it's worse. Of course the discussion I believe. + +Tyler Wright: Before we move on to Samuel. Zach. I was just gonna say if you want feel free to drop a discussion. There is a steering committee meeting tomorrow. So if you have the bandwidth to drop a discussion today, I can make sure that it gets passed on to the core team members and it could be discussed tomorrow during steering committee. Otherwise, we could discuss async in that GitHub discussion and then set up some time either separately or maybe during a Sig meeting to discuss further. So I would say that's the next steps there for sure. + +00:40:00 + +Zach Ross: I should be able to make it tomorrow. So I'll do my best to join you all there. + +Tyler Wright: Awesome. Go ahead Sam. + +Samuel Walker: Hey there. Yeah, I just wanted to follow up on the topic of the kind of best situation security policies and all fun stuff meeting Web book. And I'm like some of my Lots up and move to come over but in a nutshell on what I have found useful and this is not being applied to me just running information in general. I'd like to do that for more memory job. Bruno has been useful for applying anything web hooks in addition to kind of running policies related to everything like a positive label or Paul needs to not run as root or such now, there's things that can even go to further we have permission what books Mission policies but I feel like that be a primary tool that would be useful to close your providers. I'm going to more detail about + +Zach Ross: You said kyverno Samuel? + +Samuel Walker: Yes, okay Bruno. So it's essentially an agent that runs on the cluster or often cluster. If you want to kind of go better more of this and it on because it can block, everything from being able to be deploy the first place but it's an open source project of similar to there was one other one that also supported all policies, but it was more native instead of for convey specifically. But can do everything from even analyzing images to whatever. You can simply putting Yama. Let me join my laptop here real quick. So I want + +Tyler Wright: No problem. Yeah, it would be great. If you could drop a link Samuel on the chat. I throw it in the notes for reference. + +Tyler Wright: Yep, you could. + +Samuel Walker: Cool. How's it going? Yeah, Bruno. So there was convertible and there is Opa which is open policy agent, but me and a lot of my team. for context + +Samuel Walker: I work for red hat on your ownership side of things. But I also run an LLC other side that holds a native kubernetes cluster, but we have both at times. Look at KY Bruno and open policy. agents It gets brought up occasionally and say infra on the Upstream side of things for kubernetes side. Not the here the six and kubernetesland, but + +Samuel Walker: Essentially, I've owners referred get some work today's native and you're doing essentially just multi. Yamlapping as you were declaring the speck and deployment an image of such kindness follow that line to do a check to see if it's not to what you have and there's a little bit of Red X nobody scared, but it's kind of simple to use. + +Zach Ross: In my experience. I also use chiviera now. I just wanted to make that known to everyone. It's been pretty easy to install with helm. + +Samuel Walker: On that I just have one follow-up question when it comes to such things like that because image referencing and I primarily use Hardware to kind of prevent certain images that don't pass a certain CPS score from my first place. what happens on Akash when maybe the system automatically accepts a bit but look, deploys the image in the cluster doesn't do it because of security thing like what is the profit probably method to I guess follow up with hey, this image is not allowed or is that what's being talked about now as far as how to notify. the Akashi to do that. + +Andrey Arapov: Is your question what happens if cannot get the image what happens to the User submitted or the request? Is that your question? + +Samuel Walker: But my question is more of how do I let the user know in advance or the blockchain? No Advance. However, I want to I guess put it that I'm not gonna be running this image because of my existing security policies. + +00:45:00 + +Andrey Arapov: definitely. This would deserves a discussion. I think of a higher team hardening of the cash cluster basically, but yeah because there are several ways, it could be I think broadcasting it over the blockchain doesn't make sense because the brightest will be spending tokens. And I think we could leverage something like provider attributes, basically. + +Tyler Wright: Yes Samuel to answer your question at a high level. This is something that actively being talked about right now. So these content moderation conversations having something that's actively been thought about by members of the community and overclock Labs team since Inception, but the focus has just been continuing to build the core product which it's continuing to grow and grow the community and again rely on members of the community to help figure some of these things out. So you're like and basically the ground floor of some of these conversations had being happening right now the prey toward team Deval who just gave a presentation these member of that the prayer team there are a tool that many people use to set up providers. They are building out Cooling and continuing to provide a services in some moderation and management apis. That is one way of controlling content. + +Tyler Wright: Generation there is another Community member angiomelo who used to be a part of the overclock core team who is also a large provider on the network who is developed his own Solutions and own kind of the experience as Andre just put in the chat Deval solution. And the priority team solution is a first line defense in The Chaperone services like a deeper Solution that's being built up. I believe Zach is and his providers have already implemented The Chaperone OS solution developed by Andrew mellow. So just continue conversations and always looking for contributions. I know that you've been involved a lot lately so much appreciate that. + +Tyler Wright: I know we have about a few minutes left again. Is there any other questions comments related to contamineration Benjamin? I see your hand up. Go ahead. + +Benjamin B: I just wanted to say it's not possible to send the information back to what it was rejected. when they send the manifest like we saw in the demo there was on the cloud most it mentioned something and was not accepted because this was in the STL a string was found still. Because it's not the extra plated and used in the entire system. + +Deval Patel: We are giving the air in terms of when the deploy it right and they will get this error actually regardless of whether they do it on through the GUI or through the CLI, right? That's not a problem. But when they want to look at the Historical or anything like that, then there might be problem or even if they deployed and they don't look at logs or they don't keep the pop-up messages and that is a problem in terms of saying that why about deployment is not up and running right but that's just users ignorance in terms of looking at the log or looking at the quip of I would say. + +Benjamin B: I think one solution could be. saving the logs a little and encrypting them in a way that it could be decrypted by only the tenants + +Deval Patel: Yeah and that's something and we can bring it up in the client meeting as well. Right? That's something falls under clients, preview because think about it right that whatever the logs in terms of providers. we have the logs and we are going to keep that there is no issue on keeping on the log on provider side. But how do we keep track of the deployments and why they got closed or why they got rejected right? That's something has to do with the client side, So yeah, I mean other than myself and to our Scott can answer more on this as well, right? But yeah. That's My overall suggestion + +00:50:00 + +Tyler Wright: excellent All Again, does anybody have any other topics maybe we won't focus on them today, but we can focus on them between meetings and at the next monthly meeting but if anybody has any topics that they want to discuss further, whether it be more specific aspects of content moderation or other topics on related to Providers, feel free to throw those in that year real quick and I'll add them to the notes or feel free to add them in Discord and we can talk about those for the meeting again. If anybody has any issues that they've opened up again, I'll make sure that if they haven't got a dress we'll get a dress but feel free to join big support which happens every two weeks Wednesday morning times eastern time and Pacific time and afternoon, if you're in Europe Asia and Africa + +Tyler Wright: But again during the sixth support meeting we talked further about specific technical issues happening with the core product and potential fixes. But much appreciate everyone's time. Thank you pray to our team for the demo and the work that you let you all have been doing will look for more updates between meetings in the sick providers group. And I know that thank you Zach for your employee provided on the work that you've been doing handling your provider using chaperone OS And hopefully you can get that discussion up so we can talk about it real time tomorrow. But if not again, we'll make sure that it gets a prioritized as soon as possible. You must appreciate everybody contributing today. Thank you Ben for the demo that you shared and again anybody has any further questions comments Feel free to reach out to me or feel free to drop them sick providers or any other respective channels inside the cache Network, Discord. + +Tyler Wright: Hope everyone has a great day and feel free to join the steering committee where again we will talk more about everything that's going on their Cosh Community, but more specifically I'm sure we'll talk about content moderation and some of the other topics happening in providers. So if anybody wants to join steering committee that's happening tomorrow and is a culmination of all the six and working groups that ends the month. Hope everyone has a great day again. Enjoy yourself. Thank you all for participation. Bye. + +Meeting ended after 00:53:15 👋 + + + diff --git a/sig-providers/meetings/011-2023-11-22.md b/sig-providers/meetings/011-2023-11-22.md new file mode 100644 index 00000000..b3f54bf5 --- /dev/null +++ b/sig-providers/meetings/011-2023-11-22.md @@ -0,0 +1,446 @@ +# Akash Network - Providers Special Interest Group (SIG) - Meeting #11 + +## Agenda +- Presentation on Auditing providers tool +- Discussions on Content Moderation. +- Presentation from Benjamin +- 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, November 22, 2023 +- Time: 08:00 AM PT (Pacific Time) +- [Recording](https://2ubf2cciht62e3qpxjur4h3ihccbyk6v2hbanktvxq2wcnifp5sa.arweave.net/1QJdCEg8_aJuD7ppHh9oOIQcK9XRwgaqdbw1YTUFf2Q) +- [Transcript](#transcript) + +## Participants +- Alani Kuye +- Andrey Arapov +- Anil Murty +- Benjamin B +- Damir Simpovic +- Deval Patel +- Jigar Patel +- Julius Haus +- Rodrigo Rochin +- Scott Carruthers +- Scott Hewitson +- SC I DChorse +- Tyler Wright + +## Meeting notes +### Updates from Praetor Team (Jigar Patel & Deval): +#### Accomplishments: +- Participation in GPU testnet and successful transition to GPU mainnet. +- Collaboration with the core team to enable Praetor providers in both testnet and mainnet. +- Rapid deployment of GPUs into mainnet within a week. +- Migration from old Provider Services to Helm-based providers with one-click upgrade functionality. +- Ongoing work on content moderation and management APIs, awaiting Cloudmos APIs for Praetor dashboard production release. +- Successful migration of Price script from AKT to USD, addressing technical challenges. +- Implementation of one-click functionality for provider binary upgrades. +- Continuous commitment to providing personal support to the community, leading to positive feedback and product improvements. +#### Challenges Faced in 2023: +- Nvidia driver issues and incorporation of new instructions from Nvidia Corporation into the backend. +- Time-consuming process to address challenges and integrate solutions into the mainnet. +- Collaboration with Andrey or Arthur to facilitate smooth Helm upgrades for community members. +- Challenges encountered during provider library upgrades, risking the loss of leases, requiring extensive efforts. +- Integrating content moderation and management APIs into the provider library with Custom Resource Definitions (CRDs). +- Overcoming challenges associated with modifying the provider library for seamless integration of new APIs. +- Initiation in May or June, involving the need to transfer blockchain data into a database for dashboard creation. +- Addressing challenges related to handling, manipulating, and retrieving large volumes of data efficiently for the Praetor dashboard. +- Overcame obstacles by obtaining APIs from the indexer after the acquisition of Cloudmos, simplifying the process of displaying leases. +- Transition from old to new price scripts, requiring adjustments in UI and calculations. +- UI challenges in upgrading calculators and status pages to accommodate USD numbers instead of AKT. +- Despite the challenges, the team successfully provided upgrades to the community, ensuring a smooth experience for users. +- Accomplished improvements in UIs, calculations, and overall product functionality. + +**Plans for 2024:** + +- **Unified Praetor Dashboard:** + - Aim to revamp the dashboard for a unified experience. + - Provide a clear picture of provider performance in Akash. + - Enable users to view leases, financial projections, make provider changes, and access technical data. + +- **Contributions to Core Provider Services:** + - Building on the experience gained in content moderation and management. + - Contribute more to core Provider Services with a focus on collaboration with the community. + +- **Embedding Features into Dashboard:** + - Integrate features from the three-a-side product (calculator, status page, provider messaging) into the dashboard. + - Enhance the visibility of provider messages for improved communication within the community. + +- **General Dashboard Improvements:** + - Create an upgrade path within the dashboard for streamlined updates. + - Consolidate settings into a single page, allowing users to modify prices, URLs, and update providers. + - Display provider versions and health status for user convenience. + +- **Enhanced Support Functionality:** + - Improve support mechanisms for quicker issue resolution. + - Implement a system to email team members with detailed logs in case of errors, creating a support ticket. + - Provide users with clearer error messages and direct contact options within the dashboard. + - Enable direct communication with the support team from the dashboard, reducing reliance on external platforms like Discord. + - Implement an improved support system on the dashboard for users to submit messages and receive timely responses. + - Address issues of users getting lost in a high volume of messages within the current system. + - Introduce a more organized and efficient support queue. + +- **Documentation and Education:** + - Upgrade documentation to provide clearer instructions and guidance. + - Create new instructional videos to align with the latest Praetor version, especially focusing on GPU enablement. + - Consider developing an educational course on AkashEdu for Praetor's newer version, ensuring alignment with the fast-paced development. + +- **Community Engagement:** + - Enhance participation in the community across SIGs, working groups, and new teams. + - Offer assistance to new teams, as demonstrated by the example with Luna's status API. + - Collaborate with teams to provide data that can improve their products. + - Actively contribute to the progress of the Akash Network and embed upgrades into Praetor as they occur. +### Discussions on Praetor Presentation: +- Clarification sought on whether certain features are exclusive to Praetor providers. +- Emphasis on the optional nature of improvements for both Praetor and non-Praetor providers. +- Discussion about technical aspects and implementation progress as things develop. +- Proposal to share the presentation for community feedback and in-depth discussions. +- Reinforcement of the commitment to maintaining a low cognitive load in the user experience. +- Anil inquires about feedback on upgrade notifications and discusses the concept of enabling users with committed GPU resources to bring them onto Akash. +- Deval provides feedback on upgrade notifications and commits to overcoming any delays in the future. +- Tyler acknowledges the discussions on GPU leasing and suggests further offline discussions. +- Tyler Plans for sharing the presentation in Discord for community feedback and the intention to be more flexible with meeting times are outlined. + +### Benjamin's Presentation: +- Benjamin Not creating another demo, but summarizing community responses and plans. +- Market research: 10 responses, 9 out of 10 positive feedback, indicating a need for the project. +- Proposal: Estimated 350 hours, $50 per hour, totaling $20K. Open to adjustments based on community feedback. +- Positive feedback on discussion; no negative comments yet. +- Tyler requests Benjamin to give a one-minute elevator pitch for those unfamiliar with the pre-draft discussion. +- Benjamin describes himself as a Vanguard, involved in tech support on Akash Discord, with a backend developer brother. +- Project idea originated from a hackathon to create a tool for evaluating providers based on specific criteria (audits, region, quality, uptime, etc.). +- Aiming for automated tooling similar to multi audits and Overclock Labs. +- Emphasis on KYC for both providers and tenants to establish trust. +#### Benjamin's Pre-Draft Discussion on GitHub +- Tyler Wright appreciates Benjamin's work on the [pre-draft discussion](https://github.com/orgs/akash-network/discussions/386) on GitHub and encourages questions or comments. +- Tyler emphasizes the importance of avoiding duplicate efforts and seeks collaboration opportunities. +#### Participant Questions: +- Alani Kuye acknowledges Benjamin's rundown and asks about the realism of the estimated hours and milestone-driven deliverables. +- Benjamin confirms the Milestones will be established after the initial five hours and mentions a detailed proposal in progress. +- Alani inquires about the project timeline and gets confirmation that it's a three to six-month effort, with more details on Milestones coming in the draft proposal. +- Alani asks about the go-to-market strategy, including how the project will be promoted and adopted by the community. +- Benjamin explains that for certain aspects, it depends on partners like Cloudmos, Praetor, and the Reworked Akash website team. +- Benjamin mentions the need for marketing for specific deliverables and emphasizes the user's decision to adopt the service. +- Tyler Wright raises questions on the openness of the project and which parts will be open source. +- Benjamin expresses the belief that everything could be released as open source, with a distinction for personal information in KYC. +- Rodrigo Rochin inquires about auditing tiers, including the possibility of free audits for insiders. +- Benjamin explains the consideration of different tiers in general auditing, dependent on provider fees and needs +- Alani Kuye recommends allocating a budget (e.g., $1,000-$5,000) for marketing efforts (Twitter ads, LinkedIn ads, etc.) to gather user responses and feedback. +- Anil emphasizes the importance of creating touchpoints within Cloudmos and Praetor workflows for better marketing visibility. Recommends integration within the deployment process to enhance user experience. +- Alani agrees with Anil and highlights the significance of building a narrative for the product. Stresses the importance of data literacy and avoiding scenarios where a product gains likes but lacks user engagement. +- Deval mentions existing touchpoints and expresses willingness to collaborate and integrate with the new auditor tool. +- Deval proposes working together with Praetor, Cloudmos, and community providers, focusing on creating integrations that suit everyone. +### Concerns about spamming providers +- Scott Carruthers highlights recent discussions with Benjamin about network protection from spam. +- Scott Carruthers proposes starting a GitHub discussion for detailed input from the development team, with a potential discussion in the next SIG providers meeting. +- Benjamin agrees with the plan and expresses readiness to set up the GitHub discussion. +### Other matters discussed +#### post-mainnet upgrade Issue +- Scott Carruthers: Raises concerns about a reported issue where searching transactions by Akash provider address in block explorers is no longer working post-mainnet upgrade. +- Seeks feedback from the community to determine if this is an isolated case or if other providers are facing similar reporting issues. +- Tyler Wright Expresses gratitude to the presenters and participants for their time and contributions. +## Action Items: +- Praetor Team to share the presentation in Discord for community feedback. +- Tyler to schedule an offline discussion regarding GPU leasing. +- Deval, Jigar, and Anil to continue offline discussions regarding the idea of enabling users with committed GPU resources to bring them onto Akash. +- Tyler to plan future SIG Providers meetings, considering increased flexibility in meeting times to accommodate participants from various time zones. +- Benjamin to initiate a GitHub discussion on network protection from spam. +- Scott Carruthers to coordinate and ensure responses on the GitHub discussion on network protection from spam. + +# **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, again, welcome everybody to the most recent edition of the During these monthly meetings folks that participated in the providers special interest group come together to talk about issues related to Providers on the Akash Network. Some of the topics that have been high in the priority lists have been around content moderation over the last couple of months the pray toward team as well as crypto and coffee from the community. I've been developing various solutions to help with content moderation on the Akash Network. Last meeting the pre-core team gave a demo of the work that they've been doing around content moderation the meeting prior to that Andrew Melo gave a demo on some of the work. He's been doing with again crypto and coffee with the + +Tyler Wright: Chaperone tool that he's been working on and some of its functions around content moderation. There's also been some just general conversations around provider issues, and I know Andre who's on the call. There's a great job of connecting with providers in the community and helping them with issues as well as simple and a number of other folks that are on this call and maybe not on this call. Cool, again that there's a couple of action items on the agenda for today including the pre-tor team has been working diligently this year and a number of efforts that provider builds and provider Management on the Akash Network. They've been working on content moderation as a part of a working group content moderation that started at the end of 2022. + +Tyler Wright: And so I want to give them the opportunity to get updates on all the work that they've been doing this year. Maybe some pain points and then again I'll look ahead of the highest level on some things that they're thinking about for 2024. And then beyond that Benjamin from the community is thinking about taking on a new project. He's submitted discussions and GitHub pre draft discussion around potential idea that he's looking to explore further. So want to give you an opportunity to talk more about his auditing idea and feel questions directly from folks on this call. If anybody else has in the action items that they want to cover during this session, feel free to add those and if there's any time left we can talk about again the main Nets eight upgrade and any other items. + +Tyler Wright: Cool with that said I'm going to hand the floor over to jigar. and Deval to give us an update on all that they've been doing with pretor and I'll just be taking some notes in the background. + +Jigar Patel: Thanks, Tyler. Let me share my screen. + +Jigar Patel: So before I start my updates I want to thank everybody at the core team who helped us in a lot of issues resolving issues. We caught obviously numerous challenges solving the problems that were in hand in 2019c. So thanks for the core team. Everybody was fantastic also a lot of community members as well. They helped us our taste our product that was the big thing because it helped us to take look at a different angle and look into different kind of configuration before product is working on that as well. Right? So just wanted to say thank you for that and I'm gonna start with + +Jigar Patel: the accomplishment that we did in 2023 so + +Jigar Patel: let me start with the first huge thing that we brought into printer, that was a huge thing. We are to participate in a GPU testnet and then obviously taking that into GPU midnight this time we did something different. We actually worked with the code team to bring the Predator unabled providers going into testnet as well as well into the main so we had a gpus within a week or on going to minute. So because we also + +00:05:00 + +Jigar Patel: We also moved from old Provider Services into Helm based providers and also giving them apart to build to upgrade that into one click so they can just like cricket and they can go into the hampus provider, right that was a huge achievement for us. We are finishing up content moderation and management apis and we are also finishing up please dashboard right now waiting on a couple of apis from crowd most to once that's available. I think we're able to push that into production. + +Jigar Patel: another big thing was a high school updates, which we moved from akt to USD and that was also a huge kind of like + +Jigar Patel: Technical challenge for us where for us it's just not giving them, what the newer provider available to use the USD based price groups or new product will use your enable libraries, right? We have to give a path to upgrade the old row address into the new one. Right? And that's most of the challenges lies where giving them one quick functionality, right and over the time. We also did numerous provider binary upgrades with one quick anxiety. And one more thing that is very very important is giving support to the community, right? We get a lot of compliments where Think that what this fantastic we get personal. + +Jigar Patel: Support from our team members to the community, And that's like we celebrate our Victory. if people say that we can help them with whatever issues they have Whatever the servers or whatever the machines they got, we actually find a way to help them also improve our product as well right that help us tune to our product. and the next time that issue don't come off with another provider right so that help us a lot. but that brings us to What are the challenges we faced in 1993 right we obviously was not like a smooth ride or as a highway, right? It was more of a bumpy road as you can see so + +Jigar Patel: obviously each project that we take let's say if it's a GPU enablement or hand upgrade everything comes with the technical challenge right let's say for gpus right it was and we are driver issues insurance and new instructions coming from Right, I corporate that Into the backend, right? That was a challenge that took us a lot of time to figure out and put that into the station and then into the minute also Helm upgrade that was not easy part. We had to go back with Andrey or Arthur a lot of time and get out like how we can + +Jigar Patel: how can help our community members do or smoothly upgrades. Right? We Face a lot of issues that also in the meantime upgrading all the providers World losing leases. That was a huge challenge that we faced and 2023. Also, when we started working on the content moderation or management apis the provider Library that's understanding the library from the start and adding the moderation EPA into this with the series, right? That was a huge challenge for us. + +Jigar Patel: To make a list dashboard. We actually started this in a meeting May or June and at that time we figured out that we need to have all the data from the blockchain into database. + +00:10:00 + +Jigar Patel: So we started running all of pipelines to get all the data's to show the list as well and then obviously positive a lot of challenges with the huge data or to store and then manipulate that data and retrieve the data into swing the least dashboard a lot of work went there. And then we finally settle into getting the apis from indexer after the buyout of the car almost obviously. So figure out that's the easiest way to do it if we get the EPS from index here. it's easy to show the lazy's and we're able to close the leaders with the provided Library up here coming soon. + +Jigar Patel: Moving from old script to new script price script that was also a challenge again, right everything comes with the individual or technical challenges. also UI challenges how we had to upgrade or calculation calculator. We had to upgrade our status + +Jigar Patel: Yeah students page where we are swing all we had to upgrade all our uis where they were able to now put the USD numbers instead of we could use right. but at the end of the day, we came out of this challenges and we were able to provide all the upgrades that we wanted to give to the communities. We want to provide that a very smoothly right? So obviously communities they just like looking to upgrade their provider, but obviously at the back end we were facing a lot of changes. but coming into 2024 we have a reason how we wanted to improve our product and + +Jigar Patel: again, right all the feedbacks are welcome. This is what we think we want you guys to give us a feedback on it There is not a proposal just Overview of what we wanted to achieve in 2084, right what we want to do into our product what we want to do where we see the pinpoints and where our community face problems in general how we can fix that. + +Jigar Patel: so interest ready for we're looking to kind of like a revamp over dashboard and the way we want we see our dashboard is any related stuff They can able to do it in our provider in our task force, So basically unified dashboard. they should be able to see all the latest this would be able to see all the financial production they will able to see + +Jigar Patel: Or they were able to do changes into the provider, They should be able to see technical data. you can find a right if they wanted to see how they're kubernetes is performing right? So unified a period dashboard with the new design obviously will have providers see clear picture how they're performing in Akash, right and as we are getting traction like we are seeing a lot of Liz's like please or overall is monthly leases are very very increasing. + +Jigar Patel: Be able to see a lot of new providers will come into Akash, So even though they may or may not become provider with the Prater. We wanted to give this functionality. So to every provider so they can just go and check all the providers related data, Also this year we started contributing to provide a service with the content moderation and management this give us the understanding of Library. So we want to contribute more to the core Provider Services, So obviously with the help of the order and we will obviously pick up the work whatever it's in the issues or whatever. I will start working on the + +Jigar Patel: With order and in the core team to put more work into core provider service. We also wanted to put a finite dashboard into provider. So they were able to see technical datas. As I said now also wanted to improve the three a side kind of a product that we created for a community which is calculated status page and provided messaging. we wanted to put embed that into dashboard. So. + +00:15:00 + +Jigar Patel: Even how much can take advantage of provided messages Because lately I was seeing that a lot of Provider actually put a message into their provider for employers to see but obviously the connection is not there. So we want to improve that and general dashboard improvements like we want to create. + +Jigar Patel: Upgrade path we want to update our price scripting you want to update our kind of I will put everything into settings page. So that settings will have all the updates if they wanted to change the price. If you want to change the url of the priority if you want to change. let's say if you want to update or update the provider show them what versions they are in so then what newer version is available also the health right of the auto provider stuff like that. It's a general implant. We want to also improve our support currently people are complaining about something and then we just had to let go back and check all the logs, right so we want to create a + +Jigar Patel: Create a functionality where let's say if they're becoming provider and if something happens on the road some error happens, We want to see what that will email all of our team members with the detail of the locks, right and just create a kind of a ticket number or something like that plus also give them a better error message saying that what happened. Please contact this at this Community member or this one in all of this code when they contact us, we'll have a better idea. You have to go there and what happened? Maybe they're sudo issue, If something like that very often people we kind of for five issues everybody has + +Jigar Patel: if they are bringing the kubernetes. They forgot to label. The grain is known to Node 1 something like that. Right? So those kind of things we wanted to improve into support, right And if they have any issues, they suitable to contact directly to us from the dashboard so they don't have to go back into Discord. + +Jigar Patel: Are right and this is what get the support put your message here click here. And then we have a few kindness cue from our side. So we get a timely and healthy everybody right currently current system. Sometimes obviously community members help them, but sometimes what happens is some people + +Jigar Patel: Get lost into a lot of messages, So we want to improve that. Obviously we want to upgrade our documentation and instructions videos probably will create another education course on a class CDU for a newer version of crater with gpus enabled on Right so current videos are very old. Obviously, we are fast-paced operating all the stuff. So obviously it will be over in a month. Right but we wanted to put gpus there because a lot of new provider are coming with the gpus and that helps them to understand what's the process? + +Jigar Patel: Are internal we want to improve Network, And if you wanted to have more participation in the community across the six and across the working groups and obviously newer teams. We want to help them as well because obviously Be it they're just think about the Luna right? I mean he wanted to have a status API for him, right? So obviously we just jumped into and created API for them and now he's using their API to figure out which is reliable provider, right every time when someone uses one answer as a part, right, so something like that. We wanted to have everything any team if they think that we have a data. + +00:20:00 + +Jigar Patel: Will give them right and basically making their product better, So we want to improve that as well. This is like overall general or 2024 roadmap and obviously. With the accounts is progressing, right? + +Jigar Patel: We'll have all the upgrades that Akash is doing right which obviously I didn't write it here. But just think of this way, if the next minute it's something huge comes up, Obviously, we're going to embed that into our Trader right and all the subsequent populates history. So yeah, this is just like our roadmap, If you have any questions, If you have any feedback, please let us know if you think that there's something missing here if you think that this is what you should do, We'll be happy to be happy to add that into a road map. Thank you. + +Jigar Patel: escort + +Scott Carruthers: Hey jigar. yeah. Thanks for the updates on 2023 achievements and 2024 roadmapbooks really good and really concise vision of what your team is working on. I'm going back to the 2024 roadmap. I don't know if you go back to that first second, but on items three and four. so item three says + +Scott Carruthers: tentacle information for Prater providers and I think this will be applicable to number four for provider message announcements is That I know that three says for Prater providers, but if you're getting that technical information from the club most I, obviously you could display that for any provider. So I guess my overall question would items like three and four you anticipate only again applicable to Providers Bill through the Prater app, or would that be services that any provider would be able to + +Jigar Patel: Yes, so basically the conference desk. I'm carbons and grafana like that sport or technical data. That is what's the memories is right not from the cost standpoint, but the hardware standpoint, So basically we just literally going to install the fanaa right into our Trader. Is going to be often up right here. They wanted it. They can test the technical information. I was talking about and obviously provided message announcement is available for everybody. It's not for just Twitter approach also we obviously + +Scott Carruthers: Okay. + +Jigar Patel: we're gonna have some kind of like a mechanism to securely store if we think that the way to security store the communities config file and use it to improve our providers right then obviously, it will apply to non-preter Provide operator providers, So obviously this is overview right? But obviously when we go into each of the functionality will explore more like, how can we put that into non-preter providers and prayer providers both? + +Scott Carruthers: Yeah, and that Inception we're talking about this more as things progressed so we can talk about it… + +Jigar Patel: Yep. + +Scott Carruthers: so that makes complete says the technical information for some reason I was thinking of the dashboard being the presentation of Provider lease information and then things like that that you would just be getting from the club. us API, but obviously if you're installing Discovery mechanisms to get this information into grafana, then it would only be applicable to Prater if that's the only place that is being introduced. So yeah, like I said, I'm sure we'll talk about that more as it comes up. But yeah, that's hopeful. + +00:25:00 + +Jigar Patel: Yeah, and again and our Target to improve our product is that it should be optional or even non-exe let's say if you're not ready to provide it right process is we streamline the process with the instructions that we have from you guys So we're just thinking how we can merge them. Let's say if you became a provider from the CLI, and we're just finding a way let's say price group update right how you can calculate but something like that, So obviously that is a way we just need to find out ideally if they + +Jigar Patel: kind of like they used CLI the way we gave them the instruction it tissue able to use all this stuff. It's just like they just need to connect their control node, when stay connected if they followed our CLI instructions from They should be able to do all this stuff But okay, right. It's just finding the way to do that. Obviously that will be included in this one as well. + +Tyler Wright: I see sgcdc North put a message around it would be amazing it Prater app could be installed and removed from existing providers as Scott just mentioned jigar would be great. if you feel comfortable throwing this presentation in Discord and they either providers or maybe the trade ecosystem pretor app chatter maybe both I would love for people to give initial feedback. And then maybe we could turn this into initial discussion where we could start to talk about some of these objects or talk about some of these themes more specifically and get more feedback from Scott and other people from the community. Pardon me,… + +Jigar Patel: Yeah, yeah. + +Tyler Wright: but I think this is great. So I appreciate you taking the time. I'll give you some updates and Road. + +Jigar Patel: Absolutely, and just wanted to answer SGC are basically after the Hem upgrade. it's like if you install through Creator or even CLI, your provider is the same. It's not a different. We just like to use our own node because sometimes a lot of people have a very kind of not good computer and they want to become a provider with the Prater right? If you put the note on there. It's just gonna explore there. They're not gonna have law for resources left. So that's why we maintain our own node. That's only difference. So you can even ask any Community member for support. It should be the same as the CLI did good Alani + +Alani Kuye: Very hard to go on. Thanks for the presentation. I'm always super excited to these new developments what's going on and how it would help continue to drive to drive demand. But more importantly lower the cognitive load and the barrier to entry. my question is just more input the hybrid question really will this continue? to support the core philosophy of keeping the user experience. Low cognitive load so that we don't go back to the dark days. of CLI That's bad for demand. + +Alani Kuye: You're mute. + +Jigar Patel: Yeah, Absolutely. That's the first thought we were doing unified credit dashboard. Basically, we are just redesign the whole dashboard, right and obviously if you look back into 2022, Obviously, we are trying really one even though right when we started over design. we had a very small functionality and at that mind we created that dashboard but now we have improved or we have demand to include law of stocks. + +00:30:00 + +Jigar Patel: Keeping it the core philosophy of UI first right and to not put any kind of technical means CLI details into the UI, right and that's all That's all called to have it. It's not changed. + +Alani Kuye: alright fantastic. Thank you for reinforcing that. + +Tyler Wright: Go ahead and kneel. + +Anil Murty: Hey Tyler, Don't take a whole lot of time because I know there's other things to talk about but thanks so much. Jigar. This is amazing. I just have a couple of questions one is the last time you did one of your mobile Library presentation. One of the things that came out was it'll be nice for you guys to get a little more heads up when we do upgrades and such. I just wanted to kind of check in and see how things went in the last few upgrades. We have also increased the pace of upgrades as you all noticed. So just wanted to kind of get your feedback on that. And then the second thing was gonna give you was just a piece feedback on there for the roadmap is. + +Anil Murty: One of the things we're going to be looking at from a core team perspective and we'll try to write some discussions on this as well is the idea of enabling people that have committed to longer term contracts for the cloud resources or for the GPU resources. So today most of the GPU clouds out there, they require people to commit to a lengthy contract before they even let alone give them gpus it lower prices. One of the things that we are trying to investigate is it possible for people to take those GPU resources that they're committed to but are not using and bring them on to our cash. + +Tyler Wright: Go ahead Deval and then after divide just to want to we'll talk more about this offline,… + +Deval Patel: Yeah. + +Tyler Wright: but go ahead. + +Deval Patel: Yeah, let me answer. The first question you had about the feedback you want about we are getting enough handbag. It's up. Yes. Definitely. We are getting enough heads of and are staying that whenever you guys push right we pushed the one click updated as well right let's say It's a last time when you best pushed it was in the night specifically Sunday night at our time and we pushed in the morning, So it was 12 hours lag on our side, but we will overcome that as well going forward, So yeah, that's a commitment you have Other than that. + +Deval Patel: Leasing the GPU I think we should take it more offline and we'll discuss more in detail between me trigger and you and Tyler I would say right and we can go from that. + +Tyler Wright: Absolutely. All right. I do want to give enough time for Benjamin again pray to our team. Thank you for those update. If we could throw this presentation online and Discord, then we can get the more feedback from other members of the community about the presentation and then I'll work with the pray to our team to think about next steps again. As I mentioned. I do want to have another sick providers meeting before the years that maybe we'll have some discussions or we could talk more in depth about some of the things that the Neil talk about some of the things that Scott talk about some but things that our members of the community talked about specific to pray tour + +Tyler Wright: Looking to have that meeting sometime before December 15th. But again, I'll keep you all posted. So just look out for that. I'll mention this in steering committee whenever that happens. But one thing that we're trying to do moving forward is be a little more fluid with some of these monthly meetings so that we can get more participation. I know it's difficult and we have people that want to participate base all over the world. So I'm going to do it better job in 2024 of just finding times that work for more people so we can have more consistent conversation. I think this sick providers meeting is a good example of a successful Group, so Thank you of these items online but again + +Tyler Wright: Next up on the agenda is Benjamin who again has thrown a pre-draft discussion in GitHub? He's linked that in the chat here for everybody. I think he's done a great job of sharing that across a number of different Discord channels to get feedback and I want to give him some time to talk about their plan and get some feedback from the community. So Benjamin take it away. + +00:35:00 + +Benjamin B: Thank you I want to say here that I'm not going to create another demo. I believe that I've done one in the office hours and one in another city call. So what I want to do here is just summarize what has been. Written by us. And what's the community has responded? Let me start by the market research form right now. We have 10 responses where? on average nine out of 10 people or have positive feedback to the questions. So they believe that there is a need for what we're creating. + +Benjamin B: then for the discussion we have mentioned that we're going to create these things. + +Benjamin B: And I believe this is about 350 hours. + +Benjamin B: that we will be charging about 50 of dollars per hour. This totals out to about 20K, but I'll just keep ahead also. both depending on what we get from this conversation with back to we might be adding another. 52 on a hundred hours + +Benjamin B: the comments here are generally positive. We're just questioning. There's no negative feedback yet. And we have responded to all the questions. + +Benjamin B: this is the summer that I want to give. Now I'm opening up the mic for anyone else to ask any questions. + +Tyler Wright: Sorry Benjamin just for a couple of people that may not have read the pre draft discussion yet. It'd be wonderful especially out of the heels of Moultrie closing its doors. They'd be wonderful. If you can give a one minute elevator pitch on who you are in the team and what you all are trying to build and why you think it's important for the Akash Network. I know that you've already done that in other meetings, but some participants here haven't been there. So it'd be great to just continue to practice that high level pitch for. + +Benjamin B: Yeah, So I am a Vanguard. On the course, I do tech support on the coach through the community program written by Adam. My brother is a back in the developer working at the Swedish company. + +Benjamin B: we got this idea for the hackathon to create something where We would hold it providers not just from whether or not they should be audited yes or no, also so that we can create filters. So if you want something very specific. you want something from a certain region want something With a certain quality time in certain uptime in certain CPUs certain benchmarks, everything like that. You should be able to filter for that. We want to create automated the tooling providers or all that like this where this is included in this Then for General all the thing, this is similar to what multi audits have been doing and what? Overclock Labs is doing with their auditor. We want to kyc all the thing as well. + +Benjamin B: where providers can be kyc to become more trusted so that People know that. yeah, this is really who they say. They are. This is the company that I am trusting. This is the person that I'm trusting or for the opposite if providers only want the kyc the tenants they could potentially shoes to all accept bit from them. And this is scrapped. We also want to contribute to the cloud most indexer. Where we want to help them collect more data, which will be using for our own services. + +Tyler Wright: Thank you Again. There's a pre-draft discussion that Benjamin is introduced inside in GitHub and he's done a great job of circulating and starting to get feedback. I would ask if anybody has any questions here. Feel to ask those. You can also feel free to leave a comment inside that discussion which again is in the chat as well. But does anyone have any questions for Benjamin while he's here? I know that this affects the provider a great deal. So wanted to give some time to talk about it during the sick provider meeting but is anyone have any initial questions comments concerns thoughts and we also want to make sure that we're again not doing duplicate of efforts or anybody. Is there any thing that it's a part of this discussion that maybe other folks are already working on or + +00:40:00 + +Tyler Wright: again efforts can be combined. Just want to see if anybody has the initial fault comments. + +Tyler Wright: Go ahead Alani. + +Alani Kuye: Hey, hi Benjamin. thank you for the rundown. I'm super appreciate it and form from your estimations based on those hours. They look relatively realistic now deliverables wise, this is Milestone driven. The way you've broken it out. + +Benjamin B: Yes, so the only thing we will be taking before we create the Milestones is before the five hours here. So besides that we will have the Milestone. So when we're finished with this we will be able to spend these funds when we're finished with this. We will be able to spend those funds etc. Etc. + +Alani Kuye: Okay, fantastic and the Time Capsule on I assume you have just at least a high level project plan with a timeline in place that will support this. + +Alani Kuye: So if it's a six-month effort to have a general idea from a forecasting prospective. + +Benjamin B: we're thinking that it will be a free to six months efforts over around there. + +Alani Kuye: Okay, so two quarters, so if a big discount four major deliverables of a two quarters that tells me about every Four to six weeks. You'll be hitting one of those milestones. + +Benjamin B: Kind of story. Was that the question or + +Alani Kuye: No, I'm just a general damn trying to visualize from a timeline perspective if there are four major deliverables of our three to six month period if we ametize that over six month period that's about a deliverable rough, whatever four to six weeks. + +Benjamin B: Yeah, that sounds reasonable. We will go more into details on the specific Milestones. How much is allocated to each Milestone and how long it would take in the draft proposal that we're trying to get out until next week? + +Alani Kuye: Okay, that's fantastic and just finally too. Is there a go-to-market strategy around this? I mean once you build it and deploy it then Is it just like a tweet? Like and is there a general high level strategy to get this out to the community and drive some adoption? Because everything has to always go back to demand generation. + +Benjamin B: so for this part This will just be a portal cloudmus. maybe depending on what they want to do. Maybe they will advertise their API, but I'm not sure how much they will open up. This API. I know that the Creator is trying to get a hold of this API as well and the team building the new Reworked across website is trying to use this API as well. For these parts. It depends a little or actually for these parts. I believe this one will create demand almost assets the provider stuff the wants to use this to tenants that want to use this. I believe we will start using it as is… + +Alani Kuye: Okay. + +Benjamin B: but these two will have a bit more. Need for marketing. We will have to show users how this works. and besides that + +Benjamin B: it's up to the user to decide whether or not they want to use it. For this one. We already know that a lot of users really like having a general load For the tier based ones, I believe that this is great for automated deployments. But I'm not sure how much normal people will be using. This service because normal people might just research your providers. + +Alani Kuye: Hi, John. + +Tyler Wright: Thank you Benjamin for those answers online. I always appreciate my question for you based upon what I just saw. I think you were to talk about kyc based auditing. I know how that process will be done with that that obviously has to be closed Source information and how much of what you're asking for is going to be closed source. Yeah, those are some of the general questions that I have as I look through this predraft discussion. Go ahead rodri. + +00:45:00 + +Rodrigo Rochin: I can wait for benjaminzer. Or I had a different question about will there be tears auditing Tears like Montreal used to have A free one and then other ones with different perks. And insiders get a free free one. + +Benjamin B: What was that the last thing about Insiders? + +Rodrigo Rochin: We get out to for free, right? + +Benjamin B: If the inside they're skipped all it's for free. + +Benjamin B: All let me start with Rodrigo's questions So we will have some different tiers on the general auditing. but we have not yet decided how money this depends a little on. How much peace will be spent on all the things providers back and forth? So if we estimate that we will have to change these tears super often. Maybe we will not have a lot of Tears. but we will have most of the tears in. this part of the auditor + +Benjamin B: for Tyler's question whether or not it will be open source or not. And which parts will be open source. We believe that everything could be released as open source, but we could of course not release all the personal information on everyone for the kyc all the thing, but we could still release the software behind it. we want to be able to let other people. It's been up their own Auditors as well based off the same Services as we are going to host. + +Alani Kuye: I know we're running on time here. But if I may just add one minor recommendation if you could add a line item, I don't know what the number would be a thousand dollars five thousand. I'll let you do your own research just for marketing whether it's Twitter ads LinkedIn ads whatever it is because it's important to at least get the information out to the community of users. You can build a cohorts and the profiles all of that to get initial data back. So you get a good handle on how people are responding through it in case you have to make any changes Downstream. + +Benjamin B: That's a good idea. And if it doesn't get used we can just return it later. + +Alani Kuye: And just good for change management. That way you're not building a rock here. That's not gonna leave the town that you can find out right up front how people want to use it how to respond to it and you can pivot as necessary. Just being able to Market and get it's always important. Otherwise, it's gonna be pouring water in a basket Anil. + +Anil Murty: Yeah, just wanted to jump in. So yeah, that makes sense thinking about marketing but I think one of the things worth considering on the marketing side is Creating some touch points within Cloud most as well as play tour. So if you're a provider and you set up a provider Create or then having some sort of a touch Point within that workflow that says, okay now that you have a provider consider using this tool to get audited and then similarly, I think you talked about Cloud most already in your proposal, but essentially when somebody goes to deploy a workload then feeding them to apis from your product or your service so that people can actually filter and see more than just, it's been audited or not audited but also what level it's been audited to or what is some of the details around the auditing that's happened. So I think those touch points would probably be + +Anil Murty: a lot more valuable in terms of getting visibility to your tool. + +Alani Kuye: Yeah, and it builds a narrative. That's really what it's about. It's because at the end of the day, it's about the story I mean, we're building all those cool things. It's important to get it out there. Otherwise, we don't want stuff that we build you get 1,000 likes on Twitter, but you barely get one user and that data literacy is very important. Wow, the builders happening Deval + +Deval Patel: Yeah, so about We already have the touch point with the ultimate. Audit model 3 or if I mispronounce but yeah, we already have that and we are happy to have another auditor. To be in there right and whatever help needed and happy to provide. + +00:50:00 + +Alani Kuye: Thanks for that Anil. It was very helpful. I'm just visualizing that narrative and all the touch points. It gives a very strong continue. + +Benjamin B: I want to continue here seeing here that. We want to work together with greater app Community providers depending on who wants to join us on this effort. But we want to try creating Integrations that work for everyone. So for example for the whitelists, is this the formats that everyone wants to be using + +Benjamin B: and there's a few more questions here. Is there anything else? Otherwise, I'd like to thank everyone a lot for the questions and the recommendations and feedback here. + +Tyler Wright: No, thank you Ben for putting this together and sharing with us and again answering questions from folks on this call. I know you have some next steps and I think you got some additional feedback here today. So we'll look out for those next steps and discussions and then continue to again talk more in detail once we get that formal proposal. we can either talk about it again live after you put up the discussions in the next steering committee or in the next six provider meeting that maybe before the new year. Island I know we have a couple minutes left and I know some people have some other meetings I really appreciate the kind of folks have taken to listen to the prey to our team and all the updates that they have and also listen to Benjamin, and they're trap + +Tyler Wright: Discussion around a new auditing tool that they're looking to build on that came out of the hackathon. Go ahead. I actually Never mind. He might have just been doing a thumbs up again. If anybody had any other pop topic specific to providers or then, please feel free to reach out to me or drop those in the supervisor Channel Go ahead. + +Scott Carruthers: Yes, I know that we only have a couple minutes away many of us need to go over to office insiders and just to keep on schedule. I'm just gonna cover a couple of points here real quickly. So Ben and I have had some recent discussions he Ben has brought up concerns about protecting the network From spam essentially. It's a benite. No way we possibly talking about this topic during providers. We can definitely do that in a couple of weeks. But I'm since there's so much detail around that discussion and they episode discussion that we've gone into I'm maybe thinking that maybe we should start by if you would like to create a GitHub discussion and that will allow people like the core development team and + +Scott Carruthers: Andy and others too respond and then maybe after some good discussion and a GitHub discussion we can also cover on the next six providers. That sounds good + +Tyler Wright: That's something a great plan Scott. + +Benjamin B: I agree. Let's do that. + +Scott Carruthers: Okay. + +Benjamin B: You want me to set it up? + +Scott Carruthers: Are you gonna start the GitHub discussion and… + +Tyler Wright: Yeah, please. + +Scott Carruthers: And then I'll make sure that there's response. + +Benjamin B: Yes, sure. + +Rodrigo Rochin: I shared something that changed Channel. + +Benjamin B: I can do that. + +Rodrigo Rochin: Or sharing what other chains are doing about this band stuff. I don't know it be outside. Maybe it'll help. + +Scott Carruthers: yeah, so yeah, certainly Rodrigo so that's what I was as going to say. So I know that we only have a couple minutes here. This wall become clear if Ben would like so Ben ping me if we need to coordinate this at all, but we're just started the discussion on some of his concerns. This would be very unique to the Akash Network because we're talking about spamming providers. So just from a very high level Benjamin's concern was that at most actor could create a bunch of bids on the orders on the network to elicit bids and essentially exhaust provider wallets or protecting the network against mush's actors from launching very large deployments with a lot of resources and tying up kubernetes resources. we're in the bid process So this specific spam discussion would be very specific to the caution Network and cost providers. + +Scott Carruthers: So there's a lot in a very quick time. But bottom line is we'll discuss that more and discussion and maybe next and The other on top of that I wanted to raise was. A private contact me I'm stating that post may not a upgrade their reporting is And the reason that there were reporting was broken was a belief that in Block explorers like midscan or they block Explorer within Cloud most deploy that they had the ability to search transactions by + +00:55:00 + +Scott Carruthers: a cost provider address prior and now that's no longer working that that's a very interesting to me because I'm surprised that whatever work because typically on a block Explorer. It's searching for transactions by the creator of that transaction. So they're concern was they're now no longer able to go into Cloud most and be able to search via provider address for create lease activity and their claiming that works before the meeting upgraded. Theoretically there was nothing involved in the main net upgrade that would have had any impact on that. And again, I'm surprised that would have ever worked but I'm just throwing it out there to this community if anybody else's having and a block Explorer issues are reporting issues with their provider. If you could please let us know I want to ensure that this is just a one-off issue and that providers at larger having new reporting issues. I can't imagine that's the case, but I just want to elicit feedback if anyone else is having new issues from a provider reporting perspective. + +Scott Carruthers: And that's it. + +Tyler Wright: I could thank you Scott again. We'll follow up with somebody's action items between meetings. Thank you all for your participation today. Jigar Davao Benjamin. Thank you all for presenting appreciate all the questions from the community too. Many people have shout out. But again, hope everyone has a great day. Look out for an updated sick provider time for December. I'm going to be moving that meeting so that it can get some more participation. Hopefully, there'll be a number of things that have been moved since this meeting that will be able to discuss that meeting. So again appreciate everyone's time and effort today. I'll make sure this recording isn't made available very soon and we'll continue to push forward between meetings. But thank you all very much for the time. Yeah. We'll talk online. + +Benjamin B: Thank you. Bye. + +Andrey Arapov: And thanks, everyone. Bye. + +Alani Kuye: thank + +Scott Carruthers: Thanks. + +Jigar Patel: Thanks. + +Meeting ended after 01:00:19 👋 + diff --git a/sig-providers/meetings/012-2023-12-13.md b/sig-providers/meetings/012-2023-12-13.md new file mode 100644 index 00000000..46f45db2 --- /dev/null +++ b/sig-providers/meetings/012-2023-12-13.md @@ -0,0 +1,156 @@ +# Akash Network - Providers Special Interest Group (SIG) - Meeting #12 + +## Agenda +- Discussions on Content Moderation. +- 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, December 13, 2023 +- Time: 08:00 AM PT (Pacific Time) +- [Recording](https://ro5kevc2mbgfpzyb7ufa5bor6thecu23sbzrqrham53ivpiljp2q.arweave.net/i7qiVFpgTFfnAf0KDoXR9M5BU1uQcxhE4Gd2ir0LS_U) +- [Transcript](#transcript) + +## Participants +- Andrey Arapov +- Deval Patel +- Jigar Patel +- Max +- Scott Carruthers +- Tyler Wright +- Zach Ross +- Zeke E + +## Meeting notes + +#### Tyler Wright: +- Significant initiative discussed in previous meetings involved bringing GPUs onto the Akash Network. +- Core team, Max on the deployment side, and other teams collaborated to test GPUs on the network. +- Testnet opened to the public for GPU testing, leading to the launch of the mainnet with GPUs on the marketplace. +- Acknowledgment and appreciation for community members involved in unlocking GPUs for various use cases. +- Arthur and the core team working on provider changes and testing before sharing the availability of manufactured GPUs on the network. +- Acknowledgment of the work done by everyone. +- Praetor team's contributions to GPU changes and content moderation highlighted. +- Mention of Max and the Cloudmos team working on preliminary understanding of Provider attributes. +- Anticipation of continued conversation and development on Provider attributes in 2024. + +### Sig Support Meetings mentioned: +#### Tyler Wright: +- Mention of Sig Support meetings occurring every two weeks. +- Core team addresses issues awaiting triage in the [support repo](https://github.com/akash-network/support/issues/142), many related to providers. +- Recognition of Andrey, described as a provider "Guru," for instrumental support in managing providers and addressing issues. +- Issues affecting providers are documented in the support repo, visible under the "repo/provider" tag. +- Encouragement for active contribution or attendance in Sig Support meetings to address and understand these issues. +- Commitment to continued improvement in the process of tracking and resolving provider-related issues in 2024. +- Mention of the close collaboration between the Praetor team and the Cloudmos team on API endpoints. +- Invitation to Jigar or Deval from the Praetor team to share updates on how they are utilizing the mentioned endpoints. + +### Praetor Team Update by Jigar Patel +- Praetor team presented a detailed summary of their 2023 accomplishments and a high-level roadmap for 2024 in the previous meeting. +- Encourages participants to review the roadmap for insights into upcoming discussions and developments. +- Anticipates further updates and initiatives from the Praetor team in the new year. +- Completion of work on the CRD designed to block addresses, images, and host names for content moderation. +- Collaboration with Max and others for creating APIs, receiving requests, and adapting APIs as needed. +- Progress on creating the lease page and ongoing work on the daily page. +- Integration of blocking features into Provider Services to allow users to block images, addresses, and hostnames from the transport. +- Tyler expresses appreciation for the updates and encourages the team to continue sharing PRs and updates with the community. + +### Provider Feature Discovery Service Update by Scott Carruthers +- Acknowledgment of Scott Carruthers and Andrey's work on the Provider Feature Discovery Service. +- Feature Discovery to allow deep exploration of provider types, inventory, and specifications. +- Upcoming focus on provider incentives in the new year. +- Scott Carruthers provides a high-level overview of the tool, emphasizing its use in deep discovery of types, inventory, quantity, and allocated information. +- Scott mention a potential release candidate version before the new year for testing with selected providers. +- Expected release of the tool in the new year for general use. + +### Andrey Arapov's Update +- Tyler invites Andrey to share any highlights or focus areas for the community in the past few weeks and going into 2024. +- Andrey mentions the smooth operation of providers and a few minor issues that were addressed. +- Acknowledges a recent issue with providers' builds, which was resolved by restarting the Akash provider service. +- Upcoming work on a separate issue related to data synchronization between pods. +- Andrey highlights the effectiveness of a tool and ongoing optimization efforts. +- Emphasis on small, specific-oriented issues rather than global concerns. +- Positive note on the increasing number of providers on the network and looking forward to more participation. + +### Closing Remarks +#### Tyler Wright: + - Tyler expresses gratitude for the active participation throughout the year. + - A commitment to fostering more involvement from active providers in the coming year. + - Acknowledgment of the diverse representation, including CPU and GPU providers. + - Callout to Zeke for a reminder: Providers seeking the provider role should reach out for assistance. + - Appreciation for everyone's efforts and energy throughout the year. + - Excitement for the developments expected in 2024, including content moderation, provider microservices, and unlocking new features. + - Tyler looks forward to continued collaboration, growth, and making the Akash Network even more impactful. + - Wishes everyone a great holiday period and a happy New Year. + +# **Transcript** + +_This editable transcript was computer generated and might contain errors. People can also change the text after it was created._ + +Tyler Wright: All right, welcome everybody to providers monthly meeting number 12. During these provider special interest group meetings the group discusses any and all things related to the provider on Akash. + +Tyler Wright: It is been a very very packed year in terms of Provider conversations. One of the original working groups was around content moderation and pray toward team which has Representatives here today on the call have been working throughout the year amongst many other things provide a related to improve content moderation and build some content our moderation and management apis that they've been demoing in the last couple of providers meetings. There's also been some contributions from other members of the community including crypto and coffee that has been building a chaperone OS that is an open source solution that he's been working on the folks have been testing and interacting with so there's been a lot of work this year that's been happening around content moderation. + +Tyler Wright: This year the pretor team that was really one of the most used tools for building a provider on the Akash Network also made a transition to being Helm based in their approach. So this makes it easier for folks that are building to again have the same build process when they're using pretor as if they were using the CLI and creates synergies around support and around managing providers again, once they've been built so I know a lot of work's been done there from the prey to our team. + +Tyler Wright: At the last meeting the Prater team gave a really in-depth update on all the things they accomplished in 2023 as well as a roadmap that they shared in the providers meeting a high level roadmap for 2024. So if you have not seen on that roadmap, please take a look there again. our conversations will continue into the new year. I'm sure a lot more will be coming from the prey to our team very soon. I know that also another big initiative that came out of conversations in providers was around bringing gpus onto the network. + +Tyler Wright: so again the core team along with Max on the deployment side and a number of other teams and the akashico system works very closely to again the test gpus on the network create a test net that was open to the public where people can put gpus on network to the test. And then again have launched a main net that brought gpus onto the marketplace where again it unlocked everything from AI workloads to GPU Mining and a number of other use cases that are continuing to be unlocked by members of the community. So want to shout out again all the people on this call that participated in unlocking gpus. + +Tyler Wright: The first phase of that unlock was around Nvidia specific manufactured gpus. I know that one thing that is ongoing right now is there is work happening around being able to bring manufacture gpus onto the network. We talk about in the steering committee a fair amount. But again, if you look at the project board now linked to the AMD specific, I like to the issue inside the support repo. But again, you can see what's going on in terms of the project for engineering that is one item that is actively being worked on. I know that you can see that there have been implementations to the node. Have happened I think. + +Tyler Wright: Arthur and the core team are working on provider changes as well as some testing before again making this. For sharing with the community that again manufacture gpus will be available in network. So this is continued work to unlock the capabilities of a cost providers on the network. So I want to shout out everybody for all the work that they're doing. + +Tyler Wright: In addition to again all the on GPU side all the changes that put the prey to our teams done content moderation. I know that Max and the cloud most team have been working on r attributes and just preliminary understanding of Provider attributes. And I know that there will be continued conversation and continued development in 2024. So that's again something else. I want to shout out here today. lastly, I know that there's six support meetings that happen every two weeks during those six support meetings. + +00:05:00 + +Tyler Wright: A core team goes through any issues that have not been that are waiting triage and the support repo many of those issues. I know touch the provider Andrey who's on this call is a provider Guru. I don't know what the term above Guru is, but he is whatever that is and again is instrumental in providing and helping a cost providers that have any issues during again managing their providers or as deployments come in or as main Nets happen. he keeps it close eye on what's going on. And then again make sure that any issues that are affecting providers are put in the support repo. Those things are usually tagged reap as repo / provider. So again on this tab right here inside the support repo you can see all the provider issues that are very much. + +Tyler Wright: mind and I know that again during the six support meetings. They're talked about in a great deal. If anybody here has any input or wants to be more active contributor to helping to solve some of these issues or again wants to understand some of these issues in more detail and figure out timelines and prioritization. Feel free to join the six support meetings, and we'll continue to track again how these Shoes are solved in that and that Sig but again In 2024 will continue to reference the poor repo and make sure that things affecting the provider are at least getting attention. So again, we'll continue to improve that process in the new year. + +Tyler Wright: I know I've just been a rambling on for some time. Just giving an update on all the things that have been happening this year. I know that the prayer team has been working very closely with the cloud most team on some endpoints and has again been leveraging some of the cloud most indexer at apis. Jigar, or Deval. I know that you'll have some updates on the pre-tourer side in terms of how you're using those endpoints. Do you want to share anything here? And then again, if anybody has any other questions or any agenda items that they want to discuss feel free to drop those in the chat and we can just again get an update from the prey tour team and their work and then from there open it up to a general discussion. + +Jigar Patel: Next Tyler and thanks everybody for training support. So we've been working with the incumbent moderation. We have finished the work on the crd which designed to block addresses images and host names. So we put that for a quick question. Also, we are working with the Max and Thanks Max and other Max as well for creating APA and school soon we request after that and picking the apis as we need it, right. So that's a big help from Max and the max as well. It's a huge help creating appointment task force. That's + +Jigar Patel: The dreamed of and it's coming along. We created the least page and we are also working on the daily page right now. So that also will finish in this month. Right? So I will put that integrator and also once the blocking of will be available in a Provider Services. We corporate that To interpreter as well. So people can block images addresses hostname from the transport. So, that's the update. If you have any questions, please let me know. + +Tyler Wright: Go ahead Deval. + +00:10:00 + +Tyler Wright: Amazing. Thank you. we'll look out for again those PRS and then those updates to pray to our as they come and just continue to share them with folks in the community. + +Tyler Wright: does anyone else have anything that they want to talk about while you all are thinking about maybe some comments concerns? One thing I do want to call out and Scott Carruthers. Do not feel obliged to talk about this in any great detail right now, but I'm putting on the spot and that's what I'm trying to talk slower Scott's as well as Archer have been working on. + +Tyler Wright: A tool that's a provider feature Discovery service. They're working on this in parts. And I know that one of the main things that has been talked about in steering committee has been talked about in Sig economics and we'll be touching providers in the new year. So again, we'll be looking for a lot more participation from folks in the new year is around provider incentives. And I know that this tooling is going to be used for a number of things but provider incentives and understanding what again Each provider is going to be a part of that process. I don't know if you wanted to talk at a high level about what you're working on or just tell people to stay tuned and they'll learn more in the new year, but did want to call you up because I know you've been doing a lot of work there and that's on the public roadmap. + +Scott Carruthers: Yeah, I would say mostly just stay tuned for updates, but I think most people. have probably heard and steering committee in another forums at the idea of feature Discovery for Providers so this would be a service that will do deep discovery of Types and inventory and quantity and also allocated an allocated information. + +Scott Carruthers: So yeah, I would actually expect that that might be release and a release candidate version before the new year and then we can test it. I selected providers and then more generally release it in the new year. So yes stay tuned for further updates. But yeah, the general idea is feature Discovery Allow a very synonymous with the status endpoint currently, we'll allow a new features API endpoint that will be able to do. Praise of allocated and unallocated memory storage information and also be able to retrieve details on CPU types and attributes and speeds in different hardware specs. So yeah, all that should be coming very soon. + +Tyler Wright: Thank you cool before I open up to any other questions and again if there's no questions don't feel obliged. I do want to see Andrey again because he active with many members of and many providers solving things answering questions creating support issues Andrey. I want to see if there's anything that you want to highlight in the community over the past few weeks or anything you want to talk about specifically as we go into 2024 that we should focus on more from your standpoint on the provider side. + +Andrey Arapov: Hi everyone. So there have been many small things but none of them stuck in my memory. I don't write them down. So I cannot just keep it from the top of my head. I can't say I think specific. But other than that, the flight is pretty smooth in terms of spiders. So the only issue was maybe a couple of weeks ago or three weeks ago that providers stop bleeding. I needed to restart the cash provider service, but then I haven't seen this issues in that time. Then there is another issue that I will create a separate issue for that one. I won't highlight it now. Because it needs a extra. analysis from the depths. Currently working on figuring how to synchronize the data between pods in fast fashion because we cannot share the data between both using self. + +00:15:00 + +Andrey Arapov: So far figured that thing is a tool just working perfectly and currently optimizing it. other than that, I think that's all from my side. I don't want to focus on anything like specific because those things are rather small and specific Oriented things like they are not a global things. And yeah, we have more providers running the network. I'm happy to see that whenever I'm assuming any beat a lot of other bidding. Which is cool. And I'm Looking forward for seeing more providers and yeah, that's it from my side. + +Tyler Wright: Thank you Again much appreciate all the Andre does on the provider side. If you ever see Andre not available in Discord again. I know that people sometimes think that he's been kidnapped, but he needs some time to take vacation. So again, we try to make sure that he lets people know, but don't worry. He's not kidnapped. He's just again spending some time with family. So just want to let people know that To cool. is there anything else on the provider side? I know we have some active providers on this call and some many active providers that often join these monthly calls, but is anyone have anything that they want to highlight or talk about in detail or get some more clarity on as pertains to a cost provider or running a cost provider? + +Tyler Wright: cool if there's nothing else then again, we can just end this meeting again as we move into 2024. I'm going to make sure that there is more participation from folks that are active or they're running active providers. I do believe that this special interest group gets a lot of representation again from folks that running CPU provided GP. Rider so much appreciate all the effort that's gone into these meetings on a monthly basis this year. Hopefully, we'll continue that momentum. And as Andrey says continue to bring on more providers and unlock more features and solve more problems for folks. + +Tyler Wright: Yes, for those that are providers. Great call out Zeke. If you do not have the provider role and you want it, please just reach out to me or one of the Insiders that will make sure that you get that role. as soon as possible. if you see anybody out there that's looking for that role or having discussions around provider, but doesn't have that role. We'll make sure that that role gets added for them on Discord. + +Tyler Wright: Cool, if there's nothing else then again much appreciate everyone's time and energy today and this year. I'm really looking forward to what's to come in 2024 and Beyond I know there's a lot of stuff happening in the course side around again contact moderation provider microservices a number of different things on the provider side unlocking new features. So it's going to be exciting 2024 and really looking forward to continue participation continue to growth in working with all of you to make the Akash Network what we all know it can be I'll let everyone know what's happening with Sid clients if that's going to get moved, but again much appreciative one's time today, and I hope everyone has a great rest of their day. We'll continue to talk online. But thank you everyone. Have a great holiday period and a great New Year. + +Jigar Patel: Alright. Thanks guys. + +Tyler Wright: Over bye. + +Andrey Arapov: Thank everyone. + +Meeting ended after 00:19:17 👋 + diff --git a/sig-support/README.md b/sig-support/README.md index 921ca237..f51f2948 100644 --- a/sig-support/README.md +++ b/sig-support/README.md @@ -34,15 +34,20 @@ sig-support is responsible for defining mechanics of how support works at Akash | #16 | Wed, August 30, 2023 07:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-support/meetings/016-2023-08-30.md) |[Link](https://github.com/akash-network/community/blob/main/sig-support/meetings/016-2023-08-30.md#transcript) |[Link](https://h74pbkig7ehrbzkxe7njsglonsfukl3b4ft2acgalnjkjavwjipa.arweave.net/P_jwqQb5DxDlVyfamRlubItFL2HhZ6AIwFtSpIK2Sh4) | #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) | | | -| #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) | | | -| #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) | | | +| #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) |[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) |[Link](https://github.com/akash-network/community/blob/main/sig-support/meetings/023-2023-12-06.md) |[Link](https://github.com/akash-network/community/blob/main/sig-support/meetings/023-2023-12-06.md#transcript) |[Link](https://hzvr27yxq5skbo2dwiw6yums3dd4ujzhibdn44zpod5ebxslfinq.arweave.net/PmsdfxeHZKC7Q7It7FGS2MfKJydARt5zL3D6QN5LKhs) +| #24 | Wed, December 20, 2023 07:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-support/meetings/24-2023-12-20.md)|[Link](https://github.com/akash-network/community/blob/main/sig-support/meetings/24-2023-12-20.md#transcript)|[Link](https://kesic5sqastbfceerxf7d5zcqcumbjpipfw45q6oxxmcguazpotq.arweave.net/USSBdlAEphKIhI3L8fcigKjApeh5bc7Dzr3YI1AZe6c) +| #25 | Wed, January 10, 2024 07:00 AM PT (Pacific Time) | | | | #26 | Wed, January 17, 2024 07:00 AM PT (Pacific Time) | | | | #27 | Wed, January 31, 2024 07:00 AM PT (Pacific Time) | | | +| #25 | Wed, February 07, 2024 07:00 AM PT (Pacific Time) | | | +| #26 | Wed, February 21, 2024 07:00 AM PT (Pacific Time) | | | +| #27 | Wed, February 28, 2024 07:00 AM PT (Pacific Time) | | | + + ## Leadership diff --git a/sig-support/meetings/018-2023-09-27.md b/sig-support/meetings/018-2023-09-27.md new file mode 100644 index 00000000..0a62c9e4 --- /dev/null +++ b/sig-support/meetings/018-2023-09-27.md @@ -0,0 +1,308 @@ +# Akash Network - Support Special Interest Group (SIG) - Meeting #18 + +## 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. +- 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, September 27, 2023 +- Time: 07:00 AM PT (Pacific Time) +- [Recording](https://rub4watpfztxenu7ickmimwkdqfx2dav4soxm3g6dxgcvpg4a7gq.arweave.net/jQPLAm8uZ3I2n0CUxDLKHAt9DBXknXZs3h3MKrzcB80) +- [Transcript](#transcript) + +## Participants +- Ababacar Kone +- Andrey Arapov +- Artur Troian +- Damir Simpovic +- Emmanuel Arthur +- George Pro +- Max +- Rodrigo Rochin +- Scott Carruthers +- Tyler Wright + +## Meeting Notes +### Post Mainnet Six Upgrade Issues and Fixes: +#### Artur Troian +- Artur provided updates on ongoing activities related to the post-mainnet six upgrade. +- Mentioned that two issues would be fixed during the upcoming software upgrade: +- Validators Commission Issue: + - Explained that in the previous network upgrade, the validator's commission was set to 5% in the dryer mode but wasn't applied. + - Assured that this issue would be addressed in the upcoming upgrade. +- Deployment Authorization Issue: + - Described a problem where some deployment authorizations were connected to old API versions, causing discrepancies in querying and updating them. + - Assured that this issue would also be fixed during the upgrade, with the resolution expected in a few hours. +- Refactoring Provider Behavior: + - Highlighted a significant issue related to the upgrade involving the behavior of the provider. + - Explained that the provider, in its current design, kills everything right into the lease if anything goes wrong during the deployment phase. + - Acknowledged that this behavior is not correct and mentioned the decision to refactor it. + - Discussed the introduction of a new operator called "deploy" to apply manifests fast and separately handle deployment failures. + - Indicated the creation of a separate service to manage deployment after a specified timeout. + +### Support Ticket Updates: +- Artur provided updates on several support tickets related to deployment accessibility and provider audits. +- Andrey shared that for one particular tickets the deployment appear to be down and mentioned ongoing testing for stable diffusion. +- Andrey noted two more tickets for provider audits, one waiting for the enabling of firewall rules. +- Artur emphasized the need for labeling on the issues and suggested that they be labeled as "audits." +- Arthur Requested that the titles of all issues in the support repo follow a consistent format for easier identification and automation. +- Recommended that the titles include a keyword like "compliant" for auto-labeling purposes. +- Tyler Wright sought an example title from Artur for clarification on the desired structure. +- Tyler offered to update documentation to guide users in providing titles that align with the desired format. + +### Scheduled Software Upgrade +#### Tyler Wright: +- Tyler provided a quick update on the upcoming software upgrade. +- Mentioned that a proposal passed yesterday afternoon to address issues from the mainnet six upgrade, as discussed by Arthur. +- The software upgrade is scheduled for today around 9 am Pacific/12 pm Eastern time, approximately two hours from the current time. +- Emphasized that the upgrade will only impact validators. +- Urged communication among validators on the validators discord channel for any questions or concerns. +- Specifically directed participants to check the announcements channel in the validators discord for documentation related to the upgrade. +- Noted that Andy and others are actively available to answer any questions from validators. + +### Support Update from Scott Carruthers: +- Tyler handed over the floor to Scott Carruthers to provide an update on support-related activities. +- Scott mentioned the presence of Rodri, Shimpa, and Max, inviting them and others to share insights on support activities over the past weeks. +- Scott informed about the upcoming announcement in the Providers Announcement channel regarding the consolidation of provider documentation to avoid redundancy. +- Described the consolidation process, making GPU resource enablement on a host provider similar to handling persistent storage or IP leases. +- Emphasized that the GPU provider build documentation will be removed, and all information will be consolidated into a single process for clarity. +- Mentioned testing the new process with a mainnet test provider, ensuring it worked flawlessly. +- Requested feedback from individuals like Shimpa, Rodri, and Max regarding the new documentation. +- Mentioned that Rodri and Damir, as front lines of support in the insider community, might have additional issues to raise. +- Noted that the majority of support over the last few weeks has involved assisting new GPU providers as they come online. +- Acknowledged that, fortunately, the process for GPU providers to build through documentation has been relatively smooth. +- Highlighted the support provided for live GPUs, particularly addressing SDL questions. +- Stated that, aside from GPU-related support, the overall network seems steady, with some new user questions being addressed. + +### Damir Simpovic' Update on Support: +- Damir Simpovic shared insights on support issues, primarily addressing potential providers. +- Noted that some providers, particularly ex-miners, were not fully aware of Akash and thought they could shift their hardware seamlessly. +- Highlighted the misconception that Akash supports typical mainboards with limited memory and weak CPUs, making it challenging for these providers. +- Emphasized the need for clarification and education for such individuals +- Scott Carruthers acknowledged Damir's input and confirmed understanding of the issue. +- Recognized the challenges, especially for individuals with inappropriate hardware, even if the resources were otherwise suitable. + +### Discussion on Provider Attributes and YAML File: +- Max raised a concern about attributes in the provider YAML file not being in sync with the schema, causing them to be overwritten during upgrades. +- Mentioned that the attributes in the provider YAML file sometimes do not match the schema when providers update. +- Scott acknowledged the issue Max brought up and understood the problem. +- Scott explained that during a fresh Helm upgrade, the provider YAML attributes take precedence and overwrite existing ones. +- Scott Agreed that there needs to be a discussion on how to address this issue, ensuring that the schema from Cloudmos aligns with the provider YAML file. +- Scott noted the need for a conversation with Max and Andy to find the best way to deal with the problem. + +### Other Matters Discussed +#### Community Input on SDL Improvement: +- Max mentioned plans to work on improving the SDL builder and experimenting with simplified forms to make SDL creation more accessible, especially for new users. +- Acknowledged the complexity of the current SDL and the challenge it poses for users to learn a new YAML schema. +- Max expressed the intention to gather feedback from the community based on the updates to the SDL builder. +- Tyler appreciated Max's initiative and confirmed plans to distribute a form to collect feedback, discussing it further during the SIG Providers meeting. +- Mentioned that the collected information would be made available for use by Cloudmos and others interested in the data. +#### Announcements +- Tyler highlighted a SIG Providers meeting scheduled in 30 minutes, where updates from the praetor team's work and discussions on content moderation would take place. +- Mentioned that the praetor team is implementing solutions from the Content Moderation Working Group and encouraged community participation. +- Noted the positive reception of the provider attributes tooling from the cloudmos team and mentioned its implementation discussion in the last SIG Providers meeting. +- Announced a potential conversation during SIG Providers and the steering committee meeting about changes to the structure of the SDL. +- Requested community members actively using the Akash network to share their feedback on what is suboptimal about the SDL experience. +- Tyler will initiate the conversation during the SIG Providers meeting and possibly provide a type form for community input. +- Tyler encouraged participants to think about SDL-related challenges and share their thoughts during the SIG Providers call or through the type form. + +## Action Item +- Group await the upcoming fix for the provider behavior issue. +- Group to ensure that all support issues are labeled appropriately. +- Group to address and fix the validators commission issue and deployment authorization issue during the upcoming upgrade. +- Scott Carruthers to initiate a discussion with Max and Andy to explore solutions for the synchronization issue between provider YAML attributes and the cloudmos schema during upgrades. +- Tyler Wright to distribute a form to gather feedback on SDL improvement. + + +# **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 six supports During these support Special Interest Group biweekly meetings, looked at the open issues and support repo. If there's anything that needs triaging. The group talks about those specific issues and then triage is them. Led by Arthur. If anybody has any questions, comments concerns about a specific issue that they want to help implement during these six support meetings. anybody can talk about a specific issues, talk about it again. Ask questions about that issue, next steps, again. If anybody wants to contribute to solving an issue, feel free to join these conversation and talk about potential solutions, implementation etc. But without further ado, a handed over to Arthur to get us going with the typical agenda. + +Artur Troian: Thanks, Sarah everyone and your second share screen. + +Artur Troian: so, while I'm working on to Github from this browser, so we are pretty much still doing some things related to the post mindset sticks recap. + +Artur Troian: One of the issues is actually, two of them are going to be fixed later today. During the upgrade, these are 26. One of them is Related to the validators commission. So, + +Artur Troian: In previous network, upgrade The enforce or that was commission to 5% and it was in the dryer mode. So it was actually applied And this upgrade benefits. and another issue was related to the + +Artur Troian: Deployment. so, Some of the Depositive authorizations were used to connected to all API versions and That was in. Some discrepancy on the clients that they couldn't just que The tag was the point of authorizations as well as update them. So, we have fixed that and there's gonna be actually pretty much, cute today in a few hours. The. second, big issues related to the Boston upgrade was to refactor the behavior of the provider and that is + +Artur Troian: So right now provider is designed by that. It kills everything right into the lease, if anything goes wrong during deployment phase, which is not quite correct. We used to keep that for a number of reasons, but it's just time to remove that behavior now and refactor it. So we're gonna introduce new operator called deploy and that operator when I just wish for money fast And apply them if you just files it fails and then there is going to be separate service that kills deployment after some specified emails, I think, right now it's like Prime Minister. Anyways, let's get back to our. Routine things. So + +Artur Troian: second last, just my bolt. Okay. + +Andrey Arapov: Yeah, just updated, I think all of this tickets. So particularly those deployments cannot be accessed, so they're kind of to me, looks like they're down. So I ask the person who created this ticket to give me some updates and there are two more tickets for provider audits. One is waiting for them to enable firewall rules because they're looking, the node ports. Is an envelope provider is a 100. I'm actually testing it right now for stable, diffusion. I was talking earlier today is the day. + +Andrey Arapov: And yeah, and there is one more. I think it's all the request if you could open it, just see what's there. + +00:05:00 + +Artur Troian: So yeah, a few comments on those issues. So number one, they have to be labeled. I don't understand why they are not labeled. That's the audience should be the audio label. That's Number two, all of the issues in the support trip or The title has to be similar compliant. so I actually gonna put the github job for that but they should be somewhere compliant. And this one I'll give her new providers. Simon Assignee doesn't have any labels or projects so let's do the first so that's just too much the support. Issue. And so they have to be And this support level. + +Artur Troian: There's number one. Number two, is, + +Artur Troian: Projects. Yeah, I don't know if you need projects So Is that why? I want All of titles to be somewhere because by title, we just could do auto labeling on the description. So, it's gonna do proper labeling. And that's not just help us to draw the issues. + +Tyler Wright: Arthur are to give it a example title that you would like… + +Artur Troian: Yeah. + +Tyler Wright: because I don't think Andrey usually makes those titles. I think users from the community that want to have their provider audience. So we can either update the documentation to put it exactly in the format that you want and… + +Artur Troian: Mm-hmm + +Tyler Wright: and then again, as you mentioned, I'll do it automatically. It's okay. But a structure in which you want that title to be for all the audits, just drop it in there and then we can make sure the documentation is updated so that anybody that's trying to get on it, will follow that strict criteria. + +Artur Troian: Okay, yeah, good call. Yeah. So if you look at issue number 98, so that's how smart, sorry, the Commercial commits called I mentioned wrong land. It's not semantic. Question is the conventional commits? So It has the title and someone call and the description anyways. Yeah I will provide description of how it should be and then we're gonna have the Actual github action, that's gonna validate the issues name. I'm going to just mark it as incorrect. For a future Online. Build this one. Let's put the support on that. + +Artur Troian: guys. I'm going to draw. + +Artur Troian: yeah, so by the way, those two issues, they are the same. So we just have to Close that on. + +Artur Troian: One. + +Andrey Arapov: I mean not sure if they're the same interject. + +Artur Troian: They are the same sensing. + +Andrey Arapov: Okay,… + +Andrey Arapov: or call. + +Artur Troian: Yeah. + +Artur Troian: Disclose So yeah, that's actually the issues that I just described. There are two big items for Post upgrade and one of them, the provider. Does not behave. Correctly. If something goes wrong during deployment phase. Yeah, the fix is subcoming and we should be able to have that maybe because two So now let me just double check it out in three hours. So let me put A hurricane triage. actually does this one. + +Artur Troian: Everywhere. It doesn't. Okay, so that one is fully trust. Moving back. + +Artur Troian: It's double check. Okay, so you don't have any writing. Let me just make sure that all of this zero, we have any issues here. sorry one. Okay, and so one. + +00:10:00 + +Artur Troian: So this one was that issues fixed a while ago so + +Artur Troian: Just Okay, so that one is done. That one you just discussed and let me see if you have any severity to issues that needs to be together. All right. + +Artur Troian: These. + +Artur Troian: Yes, so that one is the duplicate of Person. And Bye. 1 21. + +Artur Troian: We don't have to have duplicate. I'll chart, what is that? + +Andrey Arapov: I think that was related to Luna deploying using different Ps3s or… + +Artur Troian: Okay. + +Andrey Arapov: something like this and I think it wasn't labeling. The deployment pro as appropriate and we never had this issues before. I think we can either close it or, it's not really an issue. + +Artur Troian: Issues. + +Artur Troian: Yes so this one 14. Yeah by the way yes some news this. Scott's brothers going to be more involved in the core development and I think there's gonna be really good first issues to start on. That's pretty much the long waiting providers, please. + +Artur Troian: You pretty much want to have separate transaction services, that's going to take care of all of the transactions. Coming up from the provider. And that's a register should fix all those use cases. And doesn't seem work for creating search, I think. + +Artur Troian: No. + +Artur Troian: Yeah, it's almost fixed. And juice. + +Artur Troian: All right, is that one is sorted out? + +Artur Troian: About. + +Artur Troian: Yeah, and we need to actually validate that issues and make sure you relevant. they're also through power and + +Artur Troian: You need to just one day. That was So in regards to this issues, there is nothing too much we can do on that right now. This is by design and divided. The tender means and specific a handles, the Instructions, So there's no archival server and, I mean, we need to think about that, but it's gonna be very big item. So there's nothing we can do about that at the moment. So, let me Double check if we have anything related to the + +Tyler Wright: Thank you. All the participated is there any other issues and the support repo that anybody wants to talk about right now any further Or we have members of the core team here. + +Tyler Wright: Cool. I just want to add on to what Arthur has previously mentioned. + +00:15:00 + +Tyler Wright: As Artur mentions, Scott Carruthers, who many of you all know as being very involved. In support along with Andrey, is going to be taking more of a step into internal engineering core product development. So again, working more closely with Arthur to help implement issues that you see the support repo help with new features and just be another hand to contribute to the core product. Scott is very talented. Go developer and again, has been instrumental in helping with documentation alongside Andrey and other folks in the community. And so again, as there's so much going on over the next couple of months and beyond as a class continues to grow, + +Tyler Wright: It's more of a desire and requirement for Scott to help support again with a core development. + +Tyler Wright: Also what I mention if there's anybody on this call that has go chops and wants to contribute, it's contributing towards some of this issues and support repo is a great way to do that. if anybody here that's on the insiders or vanguards sees anybody in the community that wants to contribute has go development experience, please push them my way. So that again, we can start to get them involved with maybe joining the six support biweekly being able to contribute to again a support issue talking to Scott and Arthur and others. If they have any questions about the code base. But again, always looking for folks in the community that can help create Saul for some of these issues and help us pushing forward. So very excited for all that, Scott's going to do, obviously, major, shout out to our turn, all the work that he's put in overtime and again, everybody else here. So + +Tyler Wright: just want to shout that Scott might be a little bit less involved in discord. Obviously, he's still going to check it a great deal, but In the past, I know Scott has been spent a lot of time in discord and again, we're not going to pull them out quick and all at once, but would like to limit his time in discord so that he could focus more on again core engineering objective. + +Tyler Wright: Cool. If there's no questions or thoughts about any support issues, + +Tyler Wright: Quickly I know that Arthur mentioned the tablet call. there's going to be a software de upgrade happening today again, there's proposal that passed yesterday afternoon to resolve some of the issues that are again trickled out of the main at six upgrade archers already talked about what those issues are. But again, that made that upgrade will be happening around 9 am Pacific 12 pm eastern time. So, we're about to think, lesson two hours out from that upgrade. This upgrade will only impact validators. So, again, communications validators inside the values, discord channel. If anybody here has any questions, please, look. And that validate discord channel. And in the announcements channel, where there's documentation related to the upgrade as well as I believe and Andy and others are active answering any questions, any validators might have + +Tyler Wright: There's two more talking points that I want to bring up the first being at this part of the agenda. We usually hand it over to Scott. And sometimes Rodrigo talk about just support in discord and other channels. So I'll hand over to Scott to give us an update on what's going on on the support front. + +Scott Carruthers: All right, thanks our. And so yeah. as you mentioned, we have Rodri and Chimpa and Max here as well. So, Maybe others that want to speak about some of the activity and support over the last couple weeks since we last men as well. before actually getting into support issues and especially for, Damiran Rodri. and Max, I'm just to make you aware. I'll be announcing In the Providers Announcement channel soon that any I've been discussing over the last couple of days that eventually we needed to consolidate the provider documentation so that we don't have these disparate GPU provider, build documentation, and they traditional home chart. + +00:20:00 + +Scott Carruthers: Provider build documentation, which is all using the same process. So obviously we need to consolidate those at some points at any time that we need to bump a version or making updates. Obviously we don't want to tain. Redundant information. So again, I'll notice this in the provider channel but we've now made the GPU resource enablement on a cost provider, very synonymous with how we handle persistent storage or IP leases. So a provider would the home create a Kubernetes cluster, go through the Helm chart build up their provider and + +Scott Carruthers: An operator crds and things like that, and then following that, you could then go into the optional Provider document to, install the Nvidia drivers and runtime, and things like that. So, again, it's just a consolidation. We'll be removing the dedicated GPU provider, build documentation, and consolidating that all into a single process. So I think it's all very clean. I went through a mainnet test provider, build yesterday following the new stuff and it all worked flawlessly but obviously appreciate any feedback from people like Shrimpa and Rodri and Max if you have any suggestions in that documentation but I think it should be really straightforward. Regarding. + +Scott Carruthers: They go ahead, Max. + +Max: Hey Hey everyone not any feedback related to what you mentioned, specifically the provider documentation, but it got me thinking about something that I was dealing with Damir recently is that in the provider that Yahoo file, there's a bunch of attributes in there for the provider that when they update their provider or I'm not sure exactly what's the process but + +Max: so with the provider attributes, schema that we've been working on implementing making providers adopted. And sometimes he Attributes in that provider that channel or not. Sometimes I think it's every time, there are not In sync with the schema. So, if the providers update with the firm in cloud mode, They get overwritten by this provider yaml file when doing upgrade. So, I'm not sure what's the best way to adjust this problem, but just wanted to mention it. + +Scott Carruthers: Yeah, so understand the issues so that they went through. Fresh helm. Upgrade or the PROVIDER.YAMO attributes would take precedence or overwrite existing. So yes, somehow that schema from cloud most would have to make it into or we'll have to have a discussion with how we could best address that are or deal with that going forward. So I'll make a note of that and I don't, maybe Max Andy and I can have a conversation about how we can best deal with that. But yeah, I completely understand the issue. + +Scott Carruthers: I'm so along with those documentation updates from a support perspective and again maybe rodri and Damir being front lines of support with our insider community, might have some other issues they want to raise. But primarily over the last couple weeks, since we met last majority of support has been obviously a lot of new GPU providers coming online, so supporting them as necessary. I think the good news there is for the most part been pretty self-reliant. I think GPU. Providers are coming online and be able to build their providers through our documentation without much issues. But obviously, we've been doing some of that support and then also decent amount of support. For GPUs. Now being live, just for + +Scott Carruthers: STL questions and things like that. Besides that office have my head. I think everything else within the network is rather steady at this point. So we answer some new user questions but a majority of the support has just been around The recent introduction of GP is I'm sorry I can't think of any other really prominent support issues over the last couple weeks and a demere Rodrigo or anybody else on the colony. thing else that you would want to raise from a support perspective, + +00:25:00 + +Damir Simpovic: That's about it. as far as I'm concerned,… + +Scott Carruthers: Okay. + +Damir Simpovic: there were a few + +Damir Simpovic: potential providers that Didn't exactly know what Akashi is. So yeah, Basically, there's been a lot of talk and buzz about Akash and a lot of providers kind of ex miners. came along and thought that they would just shift their hardware to But That's really not the hardware or The provider in a way that those are typical Main boards that don't support more than I don't know. A small number of a small amount of memory and very, very weak CPU. And yeah, basically. + +Scott Carruthers: Yes, yeah. Understood him in those even if they're resources were appropriate are but especially in those circumstances I would assume a lot of those individuals will struggle to get through a cash provider build. Yeah. + +Scott Carruthers: Yeah, if no one else has anything, that's it for me time. + +Tyler Wright: Thank you to all the empires and vanguards again. Who are Active in the community on a daily basis, dealing with users issues. + +Tyler Wright: A couple things I really want to call out Real fast. There's going to be a SIG providers meeting that's going to be happening in 30 minutes. We'll get an update from the prey tour team on the work that they've been doing as well as they'll be some discussions around content moderation. I know that the Creator team is implementing some solutions that have come out of the Content Moderation, Working Group. But if anybody wants to join those conversations, listen in contribute. I know that again at the last meeting, we talked about the provider attributes, tooling that, the cloud. Most team has been working on and it seems to be implemented very well people from the community seem to really like it. So again, that was a big conversation at the last State Providers meeting. But again, today, we'll just continue to get updates from the prey to our team, on the work that they've been doing since receiving money from the community pool, as well as again, conversation around content moderation, because I know some folks in the community have been talking about it and want to contribute to + +Tyler Wright: Various different methods for controlling content moderation. Additionally, I will have a conversation if time allows because I know there's some folks have to get prepared for this validator upgrade. I do want to ask members the community, I will put a message in the insiders and we'll talk about it a little bit during sick providers and maybe during the steering committee meeting, which is happening tomorrow. core team is looking to make some changes to The structure of the SDL. I do want to ask folks in the community. I know there's a number of folks here that are actively using the cost network, on a daily basis. We're trying to better understand what is bad about the what is less than optimal about? SDL experience, whether you are deploying or whether you're provider, + +Tyler Wright: I'm going to again open in that conversation up during state providers and then have some follow-up, maybe a type form that I'll share with folks in the community that we can collect some input over the next couple of days. So if anybody here is thinking about ways that they know they've had trouble with the SDL in the past or using an SDL on Akash, please think about those things, write them down and either during the sick providers call in 30 minutes to talk about it in more detail, or again, I'll share as a type form online. If folks would rather just write an answer. But again, we're looking for folks in the community to give real feedback about their experience with using an SDL and AKASH. So again, we could take that the user experience and continue to + +Tyler Wright: Improve the features around the SDL. Anyone have any initial thoughts or questions? + +Tyler Wright: Go ahead, Max. + +Max: And just wanted to mention that related to the SEO. I'm gonna be working in the Coming weeks to improve the SDL builder and maybe also experiment on Other simplified forms to build the SDL. Because we all know it's a bit. Becky and Tricky. Do you know all the details about how the SEO works and especially for new users Nobody wants to learn a new. yaml schema. Or language in general. So might. Yeah, I'll try to grab some feedback. I know in general. what's hard about. Yeah. + +00:30:00 + +Max: So they'll be working on that. So hopefully we can gather some feedback also from the community based on those updates. + +Tyler Wright: Yeah, so Max, that's a great point. What I'll do is I'll start to distribute that form and then again we'll talk about it during sick provider. So if anybody here can join that call, that would be great. We'll probably talk a little bit about it more and maybe some of the other sigs async, because of answers. Once those answers have been compiled, I'll make sure that that's readily available Max, so that have Cloud most wants to use it. If anybody else once that access that information again, it's open. I'm just collecting that information right now so that we can get a wide range of opinions from folks in the community. + +Tyler Wright: Is there anything else support related that anybody wants to talk about before I let y'all go? + +Tyler Wright: much appreciate everybody joining today. If anybody has any specific issues and the support repo that they want to talk about in more detail, they want to get Scott Arthur Andre or anybody else's opinion on. Please throw those in the six support channel. Just Attach that GitHub issue link with any questions and again, we'll look to get those address. But these meetings happen every two weeks around the same time. So again, feel free to join these meetings where you can figure out how to contribute to the class network from a core code base. Or if you just have any questions on any open issues that you might be helping the community with, or you just interested in yourself. + +Tyler Wright: But again, much appreciated, everybody's time and effort again. There'll be some more documentation to Scott mentioned coming down the pipeline very soon. If anybody has any questions online again, Please look out for myself. Andre other members of the insiders in vanguards. that are very active in discord which continued to grow the accused network. Question you all again sick providers happening about 26 minutes. So feel free to join. Yeah, hope everyone has a great day and again validator upgrade happening around 12, so busy morning. But, please let me know if you need anything in the meantime. Appreciate you all. Have a great day. + +Scott Carruthers: Excellent. + +Andrey Arapov: Over our flag. + +Rodrigo Rochin: Thanks. + +Meeting ended after 00:34:04 👋 + diff --git a/sig-support/meetings/019-2023-10-11.md b/sig-support/meetings/019-2023-10-11.md new file mode 100644 index 00000000..e2f4a554 --- /dev/null +++ b/sig-support/meetings/019-2023-10-11.md @@ -0,0 +1,183 @@ +# Akash Network - Support Special Interest Group (SIG) - Meeting #19 + +## 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, October 11th, 2023 +- Time: 07:00 AM PT (Pacific Time) +- [Recording](https://4bnijv3wt46kxmijhgq67y4tjt55h36c3yz7ubtakslbdyjord2q.arweave.net/4FqE13afPKuxCTmh7-OTTPvT78LeM_oGYFSWEeEuiPU) +- [Transcript](#transcript) + +# Participants + +- Andrey Arapov +- Naman Kabra +- Scott Carruthers +- Scott Hewitson +- Tyler Wright + + +# Notes + +- Tyler talked about what happenned in sig-support biweekly meeting #18. +- Scott led the team through triaging the isues. +- Assigned issue 130 to Andy. He will investigate further and close. +- Andrey talked about issue 129. This was affecting Europlots provider. +- Documentation and code is needed. + + +## Support + +- Mainnet 6 is stablized. +- The last month has been around helping users with SDL issues. +- The biggest issue in the last 2 weeks is Nvidia drivers auto updating. If there was an issue with the driver upgrade, the cluster would have issue. Documentation has been updated. +- Documentation updates can be found [here](https://docs.akash.network/providers/build-a-cloud-provider/akash-cloud-provider-build-with-helm-charts/step-11-disable-unattended-upgrades). +- Andrey mentioned that he has been working with SGC DC NORSE on the size of some files, but there have + + + +### Action Items + +- Look into AkashJS issues shared by Julius. +- Proposal for Validator 5% commission. +- Artur will look into AuthZ issue 88. + +# **Transcript** + +_This editable transcript was computer generated and might contain errors. People can also change the text after it was created._ + +Tyler Wright: All right, welcome everybody to six supports biweekly number 19. During these support biweekly, special interest group meetings participants go through active and open tickets and the support repo. The group triage is those and assigned to individuals, whether it be from the overclock team, or from the community, to help solve those issues. And then again, if anybody has any questions about any issues that are open, that could feel free to ask questions here. After that, we talked to folks that are usually on the call from the insiders of vanguards that are interacting with people from the community and discord telegram and elsewhere. And we just see if there's any support claims worth having more discussion about directly from the community. + +Tyler Wright: I know our tour is not here today, so I'm gonna hand it over to Scott to kick us off with a riassing open issues. A new issues that have appeared in the last couple of weeks in the support repo. So I'll hand over to you Scott. + +Scott Carruthers: Alright, thanks Tyler. Let me share my screen. + +Scott Carruthers: Okay, is everyone able to see my Screen. + +Andrey Arapov: Yeah. + +Scott Carruthers: Okay, so I think this is going to be pretty quick. If we look at the issues that been open over the last couple of weeks, there's only a couple and I think these are pretty quick, discussion points. + +Andrey Arapov: Yeah, I think I can just talk about them quickly. So the first one is the provide responsibility upgrades. do you need to explain details? What's the reason or just where we are? The state? + +Scott Carruthers: Yeah, we could just since we don't really have anything,… + +Andrey Arapov: The state. Yeah. + +Scott Carruthers: we can just go very quickly. So that's this the docs for this is definitely open or have been completed. The only reason I kept open was for the second bullet point. + +Andrey Arapov: that's true. So basically I just need to double check the sandbox I already checked the production is good and the sandbox basically when and upgrades are enabled and they're always some enabled by default on Ubuntu servers. and, the silently can upgrade some packages and break some stuff. We haven't seen this previously because we haven't been using convidia drivers. But now since that, we have providers that support GPU, including ours, whenever, in media driver gets upgraded + +Andrey Arapov: And get stuck this nvdp container and the Kubernetes cluster kind of gets in the state where I just like, waiting for something, but doesn't get through and the only way to solve it, you need to reboot the note, But doesn't impact they already running application so that's why we created this dog. Scott posted it in move to Dogs a cushioned network thing, thank you. and they providers so that they disabled the content upgrades + +Scott Carruthers: Yeah, and kind of being proactive. And every time during this support session, we also talk about the support issues that have occurred over the last couple weeks. I would say that this is probably the most significant thing this come up on our radar over the last couple weeks so we can talk about it a little bit more during that portion as well. But yeah, I would say that some providers being impacted by this may been our most significant issues. We're pretty late support activity over the last couple of weeks. + +Andrey Arapov: Okay. + +Scott Carruthers: So yeah, I think we're good with that. And then we also have the provider says, insufficient capacities, sporadically. + +Andrey Arapov: Yeah, I think it's possibly was related to this, and they ended upgrades was enabled on the provider because I've seen it the providers meeting constantly, but I just need to look up the locks once again just to double check this, and then I can close it. + +Scott Carruthers: What it makes sense… + +Andrey Arapov: So, Yeah. + +Scott Carruthers: since you want to go through that additional validation, before we do look any more code investigation or investigating. This deeper DME assign us to you for now and… + +Andrey Arapov: Yes, yes. Thank you. + +Scott Carruthers: you can okay. Sure. + +Scott Carruthers: Okay, and then, I think our area,… + +Andrey Arapov: The airport. + +Scott Carruthers: our last issue is Euro plots, starts bid in + +Andrey Arapov: I just checked on what's on the bottom of this. I think I started it. + +Scott Carruthers: Okay. Yeah. And that you said that I think I did read through this. + +00:05:00 + +Andrey Arapov: What we see next again. + +Andrey Arapov: Yeah,… + +Scott Carruthers: I won't + +Andrey Arapov: yeah, I remember basically there is a metal B container that is for ipleasing. And if it breaks, basically, it breaks the provider because he told me someone that's me on the call. Because we basically have a cash provider that is expecting, some information, it's talking to the operators and one of the ators, the inventory, operator and enter service and it basically cannot get iPS and because of that just provider + +Andrey Arapov: Basically, it doesn't solve self recover after you fix this metal will be stuff. So it's kind of interconnected and I think I already asked after about it in Internal Death channel some other day ago. So probably need to create the follow-up for this just to make sure the provider can self recover basically from this issues and update the Presentation Troubleshooting section because here all the comments are necessary for interval shooting this issue. Yep. + +Scott Carruthers: Okay, sounds good. Do you want me to? So it sounds like there's some documentation and also some code investigation needed. So as far as assignment, should I assign both UN Archer to this issue. + +Andrey Arapov: You can assign trust me and I will create a follow-up for Arthur that I was excited to him. So, Okay,… + +Scott Carruthers: Okay. Sounds good. Sure. + +Andrey Arapov: thank you. + +Scott Carruthers: And yeah, Tyler with that, I believe that reviews, all the issues since we met two weeks ago and just looking at the ones that appreciate that as well, just make sure there weren't any other ones that they weren't dealt with, during our last thinker that may have come in in a couple days after our last meeting unless we have assignment for everything and the span rate before our last two weeks as well. So yeah, I think as far as issues were in good shape + +Tyler Wright: Perfect. Thank you Scott. Thank you, Andre. + +Tyler Wright: Before I move on to an update from those that are actively supporting folks in discord and telegram. I do want to remind folks issues that go in the support, repo are related to the core products of again, the cash network. There is a separate repo that if anybody has any really issues related to console, they could put those issues there is also for folks that are using if you have any most related issues, I know Cloud most has been in transition and is now fully open source and within the Akash Network Organization on GitHub, feel free to drop an issues specifically into the cloud most repo. So that again, we can continue to maintain those three places where issues go and we can properly segment them, we will in the future again. Start to have Most issues as + +Tyler Wright: Of this, if the number of issues grows. But for right now, again, support repo until the cash network is for issues related to the court product. And then there's separate issues for folks that are respectively using console and cloudmouse inside those repos. So, I just wanted to remind folks of that. Cool moving along at this point during the agenda. Again we usually hear from folks in the community in the insiders and vanguards. I know we have a lighter crew today. Scott's I'll hand it back over to you. And I know Andre also very active working with folks in the community and discord. So, I'll hand it back to you. I think to talk a little bit about the issues that you just talked about issues 131 as well. If anything else that you've seen over the last couple of weeks in the community, + +Scott Carruthers: So as I was thinking of this session and wanted to highlight anything that's occurred over the last couple weeks of significance, it This is kind of been our state since we stabilize. I mean that sex and got through, GPU provider, builds the last I would say month has been A majority of support activity, is just assisting users with SQL issues or maybe some provider, build assistance, and i problems in the code base or code issues, but just assistance within the community. So that's certainly been a bulk of the activity. So, as I was thinking over the last couple weeks, the issues that we just tackled and discuss with the Nvidia GPU drivers, automatically updating, and that affecting + +00:10:00 + +Scott Carruthers: A new bit activity. And the documentation that we covered is really the only thing of significance as far as an issue that I can think of that's come over up over the last couple weeks and that's back by our review of the issues and there really wasn't anything else creative from a code level. So again, with documentation is now in place for the disabled men of the unintended upgrades for Nvidia GPU drivers. So that should just be a part of the normalized provider bill process. I think we should be in good shape on that issue. And again I really don't have anything else to report as far as core issues as mostly just some handholding of new users and some provider builds. Assistance. Andy, can you think of anything else that you've supported over the last couple of weeks that would be worth mentioning? + +Andrey Arapov: I guess maybe just a small thing but it's not an issues. Just rather the sinners provider of had made observation before. and again basically he noticed that he has high iops on the disc and we've checked together and this are just some customers decay based notes like kava or osmosis or aka they do have the right a lot on the disk and read from the risk. So this is normal behavior for customers decay based notes. So, if anyone any provider notices, this kind of thing, they can just use a IO top command. It's particular flags there and quickly identify which process is writing but it's like nothing unusual, really. + +Andrey Arapov: And other than that, I just want to say that it's been quite some time since we haven't had any drastic, big issues other than the very old issues that I reported before. + +Scott Carruthers: Yes I think to kind of wrap up. He has been a very stable period and again we're just assisting new users. And some users through image build processes, or provider bill processes, and things like that. But yeah, rather + +Tyler Wright: Perfect, thank you very much. Again, just want to shout out, Scott and Andre who have been working very closely with the community and discord for a while. as the cash network continues to grow. I know that Overclock has a small team Andre and Scott both heavy number of responsibility. the vanguards and the insiders have been doing a great job of really being hands-on and helping out the community with again, getting started any specific issues. The goal is over time to continue to leverage, the community to really be hands-on and discord and other channels. So that again folks Andre and Scott can continue to build new features. Continue to again work closely with providers and advance the Akash network. + +Tyler Wright: So I do want to continue to have folks whether it be listening in later know that they can participate. Again if you haven't joined the insiders program if you eventually want to become a vanguard, please feel free to join the inside program. Come to a sick community meeting get involved in discord. Certainly looking for more people that can help. with documentation whether it be just again, taking ideas that may become from the core team or vanguards and inside and insiders and helping to update documentation or again, as you see issues in the community, making sure that documentation is reflecting the most up-to-date stuff because again, we've been relying on Scott affair deal for that and Andre supporting. And again, we want to continue to have this be A team effort so that they can continue to work on other things. So I just want to shout that out. + +Tyler Wright: It's also a natural segue naman. Who's on this call, I invited him here and if he has the ability, I would like him to continue to join this. moving forward on demand is part of the node, Ops team, note Ops is been building some getting started cooling, that leverages AI technology and it's been leveraging the documentation on a caution there. I know that they're also working on some other projects on demand. I know that we talked about potentially doing A short demo here. But I think this audience is already seen the product and it's already been testing it. I know that you did a demo for folks in SIG community yesterday which I know what very well and I know there's gonna be continued testing. I just maybe have you briefly just introduce yourself but naman if you are open to it this is a meeting that I think if you can come to in the future basically and during this biweekly meeting + +00:15:00 + +Tyler Wright: The group, which is mostly folks from the core team and then inside is vanguards. But again, this is meeting, it's open to anybody, the group discusses open issues in the support repo related to core product, as well as talks about what's going on the community. I know that the tooling and Node OPs is trying to make it easier for developers to get started using a cache and obviously using other projects. But again specifically to Akash you're always thinking about and nodeops It's always thinking about ways to improve get started process. So this is a great meeting for you to be on the ground floor of what's going on. The community, what people are talking about? And this could lead to maybe some of those templates that are a part of your product, or again, streamlining, some of these things, whether it's + +Tyler Wright: Many people asking the same kind of question as an example about sdls, then the Note ops tool can be improved to service But again, I think this is a great meeting for you to be at. And again, you can also hear what's going on in as real-time as fashion with documentation updates that affects support and just beyond. So naman, I don't want to again, have you do a demo because you've done when the past but just, maybe briefly introduce yourself to this group if you haven't already, because I know some folks, know you and I've been working closely with you, like Scott, + +Naman Kabra: Yeah, absolutely. Thanks. Thank you so much. Tyler again, for inviting me as well. one of the very first six support girl, I'm attending but, really looks interesting to get some insights in terms of what's happening from the development side within the foundation and beyond as well in terms. So for all the contributors coming in, we're not actively trying to, simplify the developer onboarding at nodeops here and I've been actively working in this space since 2017. built out a couple of projects. One of them was acquired by circles and, was part of persistence team initially and then build out and NFT and currently, with no love sorrow objective as Tyler. Wrightly mentioned is to just, simplify the developer on boarding with two devs and + +Naman Kabra: And software guys, looking to get started with, particular protocol and eventually just leveraging AI as an catalyst here, but the goal focus always remains on. We taking care of everything when it comes to infrastructure and developers can just focus on their use cases and applications. So yeah. And, really looking forward to launch this as early as possible. + +Naman Kabra: You Tyler? + +Tyler Wright: Thank you very much again. Usually there's a number of folks from the Insider vanguards community but I know a lot of folks are in Europe or just traveling around. But again naman, this is a great opportunity, a number of folks from the core team, like Scott's Archer, Andrey, a Neil sometimes attend this meeting and it's a little bit more technical. But again, you'll be on the ground floor of what are some of them open issues? What are some things that are the community is facing and hopefully you can help streamline. And again this is also a good group that is already been testing. I know that soon everyone here is already taking a look at nodes since been testing and again we'll continue to share that in discord and continue to get feedback. + +Tyler Wright: All right. We've gone through the agenda. We've looked at open issues that haven't been triage in those issues have been triage. Thank you, Scott and Andre, we talked about support in discord and Telegramand, gave her brief intro of himself. And again, hopefully, we'll be able to continue to attend these meetings on demand. If anybody from that, has a go background and wants to help solve some issues for our costs. There are about toots available. So just if you want to pass that message along again you can work, I have more folks that want to work closely with the core team and help us. + +00:20:00 + +Tyler Wright: I'll get more cloud parity. But again if there's nothing else then we can certainly adjo This meeting for today and then again I'll follow up with notes recording and transcript make those available and then we'll meet in two weeks. Does anyone else have anything else that they want to cover? + +Tyler Wright: again, Scott much, appreciate you filling in and leading us to victory. I hope everybody has a great rest of the day and we'll certainly talk online. If anybody has any questions comments, please feel free to drop them in six support or again open up a support issue or again reach out in the community a number of channels but much appreciate everybody. Hope everybody has a great rest of the day. + +Andrey Arapov: Thank everyone. + +Tyler Wright: Thank you. + +Naman Kabra: Thank you. + +Meeting ended after 00:21:21 👋 + diff --git a/sig-support/meetings/020-2023-10-25.md b/sig-support/meetings/020-2023-10-25.md new file mode 100644 index 00000000..09678b64 --- /dev/null +++ b/sig-support/meetings/020-2023-10-25.md @@ -0,0 +1,379 @@ +# Akash Network - Support Special Interest Group (SIG) - Meeting #20 + +## 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, October 25th, 2023 +- Time: 07:00 AM PT (Pacific Time) +- [Recording](https://tiycqjxd7fzfrflpcqvbtv6urvk4vtbljtwr7kfpebsrd2p7hhvq.arweave.net/mjAoJuP5cliVbxQqGdfUjVXKzCtM7R-oryBlEen_Oes) +- [Transcript](#transcript) + +# Participants + +- Andrey Arapov +- Naman Kabra +- Scott Carruthers +- Scott Hewitson +- Tyler Wright + + +# Notes + +- Artur talked about Mainnet 8 upgrade. https://github.com/akash-network/support/issues/136 +- Artur talked about issue 133 https://github.com/akash-network/support/issues/133. Naming will help with clearing up confusion. This will also allow us to include package itself. +- Andrey asked will we name the provider-services version in similar way as the network? Artur mentioned that provider services naming will be complely different. +- Artur talked about issue 137. This is a known issue, and this may be a duplicate. The feature discovery tool may help with this. +- Artur talked about issue 135. This is something that needs to be looked into. This is marked as P2. +- Artur talked about issue 134. This is a weird issue that needs further investigation. Artur thinks that this is related to CometBFT. This may require a network upgrade. Need a P1 for this. This is important. +- Artur talked about issue 81. Tilt is not the best solution for this. This issue has been closed. + + +## Support + +- Scott talked about support in the Akash Network. There has been provider support, and some challenges getting GPU providers spun up. +- Andrey talked about some providers that he has been supporting. Nothing is out of the ordinary. +- Scammers have been prevelant. + + +## NodeOps + +- Naman talked about what they are building right now. +- Working closely with Spheron. +- Artur asked what current features from Akash side will be used with that? +- Artur asked what does "Template" mean? +- Artur mentioned that running a testnet on Akash Network is a bit complicated. +- Artur asked do they have integration with Leap Wallet or Keplr Wallet? +- Naman mentioned that Nodeops is targeting Web2 developers. + +## Action Items + +- Issue 134 needs further investigation. + +# **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 most recent edition of the six supports biweekly. I think this is addition number 20 during the support biweeklys. We look at all of the issues in the support repo which are mostly related to the core product. Of Archer Scott and the rest of the team triage those issues and prioritize them. We are looking for folks that want to get involved again. If you want to get involved in helping with support issues and support tickets. Feel free to reach out in the six support Discord Channel and we could talk about skill set that you can look at tackling an issue and then again join these conversations or leave comments and specific issues and the support repo. + +Tyler Wright: There are other repos pacifically if you have any issues related to Cloud most there is a issues repo or assist me. There's an issues section inside the cloud most repo where you can leave all issues related Cloud boats. There's also one for console. But again, there has been recent news that I'm sure we'll talk about a little bit later where console is no longer going to be up camp again. It's an open source product. So anybody can take it and run with it, but the overclock Labs team is going to now with a cloud most open sour And available to everybody overclock Labs team is going to take their resources and focus on some other projects and again leave console in the stages. It is in today. So Cloud most will be that preferred tool. + +Tyler Wright: Quickly, we'll have Artur lead us through triaging any issues Scott and Andre did a great job of holding down before 12. Archer was delay away at the last big support biweekly where we talked about again entry. We talked about any open issues. We talked about things going on in the ecosystem and Naman who was also on then engage a demo of the project that he's been leading called no doubts. + +Tyler Wright: After retriage issues today and here what's going on in the support repo. I do want to give Naman about five minutes to again talk in a very high level because I know that many people here if not, everybody has seen nodeops, but talking to high level about what nodeops is but more specifically talk a little bit about some of the future plans so that again some members of the core team like, Partner Scott Andre can get here first listen and Roger as well. + +Artur Troian: Thanks, Tyler. Hi, everyone. + +Artur Troian: green + +Artur Troian: All Yeah, there's some new issues popping up in the sports. Let's first Focus through this one. So they're almost trashed. This is related to the upcoming Network grade related to providing. + +Artur Troian: enhancing beats message with the compute offer from provider that's mainly right now targets use cases when deployment is being created with the Wild Card GPU request. And patterns often to know what provider actually offers them. So for example, there is a wild card request. For the GPU and there are two providers one of them give you 30 60 and another one given 49g for the same price. I wouldn't you to take from 90. Yeah, so these upgrade is on plan to be shares. So that's this week. and if we + +Artur Troian: if all those goods and we send upgrade proposal this field then. Sometime probably during November. We're going to run network, right? + +Artur Troian: Let's not see all unliment issues. Yeah, this one is. + +00:05:00 + +Artur Troian: Is related to Discussion about versioning of blockchain versions as well as minus versions of historically we've been calling each Network upgrade as they're like may not two minutes three minutes four minutes five. However, actual versions of them great or binary versions were these Euro 24 train to 20 and so forth. So if you like to and it's just great sales confusion, first of all outside of the team, which is an excitable as well as I think. It should be all aligned and another. benefit of that is + +Artur Troian: due to go implementation of versioning each major version is pretty much the new package so we can include package itself that allows us to include itself and easily handle previews the history of the previous network of rates. so we going to have that. Coming up. sometime this year, so it's still trying to figure out what's the best way to do that but the current upgrade is mine at seven the upcoming music with attributes up there. It will be mine that eight. So if the naming Go public after that you will name Akash node package because it'd be nine. So that's gonna be the mind. + +Artur Troian: We will try to cover that in ADR before moving on is that and that's pretty much it and from the subject. You can just pretty much aligns us the other chains. We will not give upgrades. The name some other changes do we don't see a reason that but it's just gonna be number. I think it feels self-describe the progression. Okay, let's see. + +Artur Troian: This is something new because there's some messages there, And the provider version is going to be completely different story. + +Artur Troian: And I don't go ahead. + +Tyler Wright: That they still might be a mood if you're trying to talk. + +Artur Troian: Yeah, let's move on and if he is able to speak this, so this issues is something new. Yeah, that issues has been popping up a few times. I think it's been already reported somewhere honestly, so I need to triage that and say that because it looks like an application but it's been So what the plan for now is Scott and I are working on improvements to the inventory. + +Artur Troian: That thing is called future Discovery and we will be part of the service. So as soon as we combine inventory processing within the ones service. Then we will take a look at that issues because it looks like to do related to the inventory behavior and you just need to fix it. It doesn't make sense to fix it separately. So + +Artur Troian: it's called let's maybe take a it looks like a duplicate to me, but I can be wrong. people provider, Let me see if you have waiting for a tree. + +Artur Troian: Yeah. + +Artur Troian: Yeah, we need to take a look at that as well. So that's the provider configuration. + +Artur Troian: So of yes, God, we will need to take a look at because technically that is related to the inventory should report amount of available. External ports, so that's really good call for the API. I didn't know if you include that right now or are not so I think actually that also implies for So for example, we want to report it inventory of IP addresses or at least blog. It doesn't have to be the exactly IP addresses but rather about count as well as How many ports available for each IP address just in case you'll need to think about that we don't have to implemented now, but we're gonna have to think about that. + +00:10:00 + +Artur Troian: So let's think about this issue is p kind of P2 for now. + +Artur Troian: All right. + +Artur Troian: What else do we have and wait in triage? + +Artur Troian: Yeah, this is a real issue frankly and it's quite a lot of problem investigation. So what happens is at may not sakes known as upgrade 24. We have a great. Christmas decay to 45.16 that looks like there are There was some breaking change. my suspicion is actually probably related to commit a bft for + +Artur Troian: so that needs to be investigated and it looks to me that we might need to fix schema. And do Network a great actually to fix that. So frankly I don't know at this stage. what does decision but it looks to me that it's all the broken state the data types after this upgrade are not compatible with the previous one and it unable to query the state. + +Artur Troian: But yeah, we need to fix that and we actually need to have a test through this particular use cases as well. So I will pull that Aspire it's kind of important. + +Artur Troian: Okay, and what else let me see different reaction. No. and is verification + +Artur Troian: I think + +Artur Troian: yeah, remember about this Conversation. I think there was one of the seek. And the idea is that using teals for the dev environments just doesn't make sense. This is the stage so if you'll be using the + +Artur Troian: current way of the kind that we used to spin up Network as well as the provider simply because this is probably because glucose so for us the development environment is the environment that Is needed for the developers and it's has to be wrong locally and our view of that is you have to know shall make and kind for that. + +Artur Troian: And if there is other type of networks the testnet and the testnet are not meant to be speed up by individuals. So, I believe we had discussion this problem and doesn't access to move always this issues pretty much. I can just close it I think. + +Artur Troian: Alright and then I saw one issues related to documents, but I think there will be up against Scott to discuss hold a second is verification + +Artur Troian: Yeah, one second and I just want to become one not an issues. All right, I think that cars it. Tell her about you. + +Tyler Wright: Thank you Yes. is there anybody here that wants to talk about any specific open issues get more clarity talk about any of the open issues that there may be looking at or might be specifically interested in before we move on with the six support agenda. + +00:15:00 + +Tyler Wright: cool All right during this next phase and I know we have some members of the community here. We usually try to get a pulse of what's going on in the Akash Community. Again. We have a number of folks that are costs insiders and vanguards that are active in Discord and telegram making sure that in existing users have all the help that they need deploying. + +Tyler Wright: Setting up a provider, a huge shout out to for all the work that he does with the community. But again, I just want to pass it back to Scott's maybe Roger and any others if there's anything that's worth talking about or any themes happening currently in the Akash community on the support side. + +Scott Carruthers: Yeah, and really NDS price spent more time in Support over the last couple weeks than I have but definitely I have a pulse on it. But I know that Andy's been working with some specific providers. I don't think there's any issues other than the ones that we've already discussed through archers walk through of open issues. But yes, new issues over the last couple weeks for it's mostly been provider support and a couple of one-off issues not related to any code issues, but just some challenges get in. GPU providers stood up and most of it has been after we + +Scott Carruthers: Upgrade to mean that six and worked through any issues immediately after that upgrade. It's mostly just been assistance with new users and providers coming online. So again, I haven't spent a ton of time and support over the last couple weeks, so rodrian and he might have some thoughts but from my perspective, it's mostly just been Assisting new users with deployments and sdl offering for AI workloads and then in the address individual provider support. + +Tyler Wright: Thank you, Scott Andy Rodrigo's or anything that you have seen that you think is worth mentioning. + +Andrey Arapov: I'll say nothing from my side just usual stuff like nebula block. They need to enable firewall for note boards The Foundry already that works with them or fixed. They have the head basically a firewall issue proxy there forwarding the traffic to their worker nodes. And there are a couple of more things was I think I wrote them down somewhere but they're not that worse. I've mentioning maybe only slightly meant to mention on a bit surprise script for the Nvidia cards you can have different models of a hundreds like 40 gig or 80 gig and I already erased internally this question results, but I think artur's quite booked with the other stuff and so far nobody's really pushing this just to highlight that it's in works and + +Tyler Wright: Person, thank you again, Rodrigo North there's anything that you want to know I don't feel obliged but I just do want to shut you out for all the work that you do in Discord and elsewhere just like making sure everyone has updated up to date accurate information Etc. + +Tyler Wright: All I'll go ahead Roger. + +Rodrigo Rochin: Okay. + +Rodrigo Rochin: Like that. So besides what Scotty and Andrey said nothing of the ordinary precise providerable only In quite a bit of scams or scammers trying to support tickets which aren't really support tickets there. We are talking inside his channel trying to figure out a way to stop both, trying to delete it on accident and others are doing the same. + +Tyler Wright: Thank you I think that's a great call out. One thing that we want to make sure that people pass around in Discord. I know that the Insiders and vanguards are doing a great job of that Discord channels are designed for public + +Tyler Wright: public discussion and communication there will be some instances where members of the core team will have private conversation with folks that are doing providers or maybe deploying specifically but there was no other ticketing tool that will require you to go into any other Discord. Everything will be happening in side the Akash Network, Inside of direct messages and again, you can look at the tags for people that your direct message messaging to make sure that their members of the core team in the end in the admin area or the members of vanguards are insiders. And again, none of those people will ever ask you for, very specific information or private information. + +00:20:00 + +Tyler Wright: And again, there's no other Discord that is needed for support tickets. Everything happens in this Discord or inside of GitHub. So please make sure to pass that message along if you see anybody trying to use that scam of trying to get folks to join another Discord, but again much appreciate rojri and everybody else for other efforts in trying to maintain as much order inside of Discord as possible and make sure that everyone gets a kind of support that they need. Great. So we've talked about open issues related to the core products on Artur and the team gave us an update and Retreat as we've triage those issues. We've given people the floor if they have any questions on any specific issues that they want to tackle or have any more questions on + +Tyler Wright: we've given an update on everything related to support in Discord and other channels where we're insiders vanguards another members of the community or actively connecting with folks that are new in existing users and they cost Network. Right. Now I do again Naman was here two weeks ago to give a short demo on nodops, but because it's so closely aligned in my opinion with support, again, no docs is an organization that's trying to make it easier for developers to build on top of tools or to build on top of projects that could cost Network. I know that they're working closely with Archway as well as a couple of other projects in and out of the cosmos ecosystem. + +Tyler Wright: But I did want to have Naman come here. Just again give a 30 second high level view of what nodops is and specifically how we see the Akash of nodops adding value to supporting the ecosystem and then maybe spend a couple of minutes talking about the future plans so that again this group which is very technical can kind of hear firsthand Naman from you. What nodeops is thinking about building in the future so we can make sure that we're all aligned. So unless anybody has any other questions I will hand over to Naman to just give us a short again demo of what nodops is today and then talk a little bit about what the plan is for the future. + +Naman Kabra: Hey Tyler, Thanks again for inviting me glad to connect and super excited to show you guys what we've built so far for nodeops on also talk about what's in the pipeline and where we see bringing the huge value Edition for Akash here as well. Right? So just a very quick overview about what nodeops does, nodals provides and simplified infrastructure for developers and no operators looking to get started with particular with three protocol. Right at nodeops are mission is to provide the most simplistic environment, which is + +Naman Kabra: driven and governed by AI unabled infra to wherein it provides an onion incentivization layer that encourages more developers and node operators to join on businesses to be onboarded to a particular protocol by eliminating all the initial friction that developers or node operators generally go throughout their development life cycle, right? So I'll quickly share my screen walk you through a couple of features, which we have already in place. And also what's in the pipeline as well, right? So we'll just quickly show you the roadmap as well. But yeah just + +Naman Kabra: Still quick overview about what does node Ops are simplified powered playground consider this a single stop for developers or no operators in terms of any activities. They would like to do be it deploying their own sdls be it spinning up their own violator notes be it creating an own chain governance proposal or be it creating their own tap onto a particular chain. + +Naman Kabra: Write all of this process. We would be providing the already established preset playground for them. So developers now just have to focus on their business logic application. Let rest all in terms of infrastructure level initial configuration has been taking care by us. Right? So the way we do that is while leveraging containerization and talk Rising the entire environment, So the entire backend is set in such a way that every time a new chain release or every time a new upgrade. It's been pushed. There is an automated pipeline triggered which activates all the components be it a custom chat interface, So for example, if I open up the version for a cashier, I just walk you through the components as well. Which exist + +00:25:00 + +Naman Kabra: Yeah, so be it a custom chart interface, which you see here, the way we have set this up is, pre processing the entire data, fine tuning it and keeping it purely developer focused and letting all the philosophy go away from here, So that developers cannot just copy paste this particular code snippet, but there is also and mechanism wherein you can try out this code Snippets as well right now. The support is life for bash JavaScript golang wherein anything in terms of binaries, it's already set in the background, So all developers have to do is either come on the platform and very certain things if they have the right set of parameters in place be running up and interacting with binaries or CLI or consuming the templates, which we have this templates right now are all AI driven, but + +Naman Kabra: we always take care of testing this out at scale securing it ensuring that there is no flaws in terms of keys exposure at all. Right, no operators can be free from all the security side of issues which might be prone to attack in certain cases as well. Right one thing which we + +Naman Kabra: Going to do next here. All this templates right now are taking the end user created developer or no operator to this playground, but very soon this templates would be interactive wherein if let's say you want to set up a governance proposal this tool would provide you a simple front-end for it where if it's a parametric change governance proposal. It would ask you for all the basic details it would generate a Json you can deploy that Jason on testnet to test out and play around with it as well. Right so all in all the objective remains to just enable the most interactive interface for developers and operators for looking to get started. Next Step, which you see right now on this version of the playground is nothing but a preconfigured ID for you. + +Naman Kabra: So consider it a simple vs code, but the only difference here is everything is already set for you in the backend. So you can create your own set of repositories. Close it back come back again. The data would be preserved for This is an interactive AI driven playground for developers. So any kind of hackathon activities any kind of workshops, which foundations or Community would like to playground become so one stop solution for them to get rid of all the initial setups and challenges associated with it. + +Naman Kabra: So that they can now focus on the application letter while the infrastructure layer has been taken care by us. So this is an overall, product pipeline. I'm skipping the contribute and earn section here, which is basically an onion incentivization LED that would encourage more developers to come in. They would be rewarded for any kind of contributions be it solving bounties weight solving any issues or be submitting any templates which might be useful for ingesting into our AI model right now. What are the next things which we are going to do all of this templates, which you see right now, once the deployment layer is active for any new chain that node of supports we would be leveraging Akash as the deployment layer for be it running a smart contract on Archway or axillar all deploying your own set of CLI base interactions all of this transactions and any kind of deployment. + +Naman Kabra: That comes it we would be leveraging a cash for it. Number two would be the entire infra for all the chains for all the nodes, which is currently been supported by. + +00:30:00 + +Naman Kabra: no Ops all of this would be, powered by So the entire infra for nodeops specifically for Akash and as well beyond other white labeled version as well. Everything would be powered by Akash right on top of it. We would be also enabling a cosmosome simulator as well here which would developers from evm side to make their contracts more compatible towards, solidity side of things. So we're collaborating with orichen on this. They already have some cause and was some ID in place so we would be working very closely with them to make it part of our workspace. So that anyone can come on board in. + +Naman Kabra: simulator as well if they want to work on cosmosome. But if they would just like to focus on developers slash node operator side of activities, they can definitely use templates and playgrounds. That is one next would be all the components which you see here. we are making it very modular enough for any kind of, new developers to come in and interact with the documentation itself, right? So we are currently testing it out with Archway. We're in + +Naman Kabra: The ground button here which will redirect users to a direct access to an interactive environment for them to get started and on top of it the tried functionality along with the chat interface, which you saw here. We are trying to integrate it with all the code Snippets which exist in these documents as well. Right? So this becomes easy to follow interactive documentation for developers. rather than just copying and pasting it and interacting it local they can actually interact with the documentation right here. So we have yesterday it out at a very small scale again dockerizing this entire code Snippets which exist here and enabling a template for it. But yeah, that is under + +Naman Kabra: Still work in progress to make it integratable with any kind of documentation that exist as well. Right? So that's just a quick overview. And would be happy to have some feedback here your thoughts on this and if there is any particular that you think might be interesting for the ecosystem would be happy to consider and bring it part of our next release. + +Tyler Wright: Thank you Go ahead Scott. + +Scott Carruthers: So a couple of questions there's obviously to main parts of the Akash code base. You have the blockchain. And also have providers on the Akash Network what you're very sounds like you're very familiar with based on. Using a cost appointments in the future first spinning up other chains, so I know you're familiar with all this my question. Is this simulation is in the vision of this to not only Spin up a localized Akash blockchain for developers to interact with… + +Naman Kabra: Yeah. + +Scott Carruthers: but also to spin up. The cost providers site as well or… + +Naman Kabra: + +Scott Carruthers: is this only focused on the blockchain portion? + +Naman Kabra: It would be for both,… + +Naman Kabra: right We are starting with providers initially. We are starting with blockchain Centric interaction with the network first, but as you can see the + +Naman Kabra: The entire in infrastructure is set in such a way that anyone can comment, deploy their own set of applications and versions on it. All we need to do is containerize this basic base layer and the base skeleton of it after that, any Community member it's going to be open source. Any Community member can just come in plug in their version of it make it modular enough for the testing as well. So from the deployment perspective. We are working closely with other partners as well on to put this templates to put this node layer on to their platform as well their Marketplace as well for more exposure. + +Scott Carruthers: Okay, my second question Archer I say that you have your hand up. So it's probably perfect. Segue, so obviously we have some of our own internal tooling and have written documentation for developers to be able to easily spin up test environments. We're rather easily and arturia. I guess I'm just wondering from you the concept of nodeops. I'm doing this in the future spending up on base blockchain instances and potentially a provider in the future. I'm just curious to your thoughts and where you possibly see challenges here. + +00:35:00 + +Naman Kabra: No, so we can do that. I got the link yesterday from Tyler about this more from the documentations and internal toolings as well. we can definitely integrate that leverage it for better visibility and ease for anyone to get started. So any kind of internal toolings that exist, we can put it in form of templates here also integrated with the playground that's definitely doable + +Artur Troian: Yeah, thanks. Question though. Yeah, that looks amazing. I like to have some clarification on all the few things. So the first question is. + +Artur Troian: What use? So how? my net cash mind that is involved in that. What features let's say blockchain provider? Are going to be in use for that. + +Naman Kabra: So you repeat the last line? + +Artur Troian: what current features? + +Naman Kabra: right + +Artur Troian: from a car site will be used in that. + +Naman Kabra: So, if you look at the chart interface, which we have created here right creating an sdl for postgres or any kind of other use cases as well. What we are going to do is right here give a deployment layer as well. Right? So, once the AI interface response gives the response back with the right end to end template or rent-to-end quote snippet or a file here at the end once user clicks on try After that there would also be an option for deploy on a cash right so that + +Artur Troian: + +Naman Kabra: Is one second one would be let's say if anyone comes in and writes here to orders because one of the component of node Ops is also to have node as a service provider. Right? So that one of the template is also going to be to spin up your own notes be it on Akash test net weight on minute, right? So anyone can come in you would provide the templates They can try it out in our test infra if they like it there would be an option for them to deploy and that deployment layer would again be on a cashier right? So in that way + +Artur Troian: Yeah, okay. just real quick. Let me recap on the first part. So. Let's just correct me from wrong the first part. + +Naman Kabra: Yeah. + +Artur Troian: So you are pretty much planning to deploy to have a tool that allows to deploy on a car, right? + +Naman Kabra: Yeah. + +Artur Troian: I said did you there's a console and Cloud most for that? + +Naman Kabra: I did check that out. Yes. + +Artur Troian: Okay, so what features does not always bring? apart from the + +Naman Kabra: Yeah, so from no laws perspective, right the templates which exist here. They are going to be very unique as compared to Cloud Moss being the more cold deployment let right the templates here are more focused towards new developers to comment right be it towards AI side of things be it towards interacting with the blockchain. It towards provider side of things or be towards node operators side of things, right? The temps would be templates and the playground here would be the core component which actually won't be existing anywhere. + +Artur Troian: What was yeah, what does template mean? Is it? pretty much this some pre-field sdl. + +Naman Kabra: Yeah, so not just But any kind of walkthroughs any kind of tutorials any kind of transactions, all of those things, for example, we've just set up a couple of them here right be towards transactions way towards no operator side of things be towards governance side of things. Right? So templates would be an easy to follow step by step walkthrough, but also try it out in the interactive version So that would be the more focus of templates to differentiate it playground is more focused towards building out apps and application layer and deployment templates is more focused towards CLI side of interaction and making it more simplified directly by providing a friend and interface. + +00:40:00 + +Artur Troian: So I say it's pretty nice to just try it out, right if you talk about let's say I saw there run a validator. So there are lots of things related for the validators security. so + +Naman Kabra: Yeah. + +Artur Troian: Do you plan to have like you mentioned testnets, the running testnet on a car is kind of sophisticated process and… + +Naman Kabra: Yeah. + +Artur Troian: It needs lots of understanding not only from the blockchain prospective about how actually provider works and how to set it up. So if you for example want to run the validate or to try it out where this validator going to be running. Are you going to plan the spin the testnet for that? Or is going to be on how it's gonna be simulated. + +Naman Kabra: So the simulation here would be any active test net which already exists right? we would be utilizing that and leveraging it here, the objective for Yeah. + +Artur Troian: so, okay, but my question is For validator on the testnet to be inactive sad the test not owners have to give tokens for that. Right and… + +Naman Kabra: Yes, yes. + +Artur Troian: I just give you prospective of why I don't think that's a great idea. So mainly testnet are managed by the natural that's not core Developers simply because that allows them to React quickly if you happens fix it and move on. + +Naman Kabra: right + +Artur Troian: And adding more validators to the active set. really complicates often the + +Artur Troian: Process of Greek network of grades within the testnet. So sometimes that never progress. For example, we have times like 10 minutes. + +Naman Kabra: Yes. Yeah. + +Artur Troian: yeah, I would say the emphasis on the cosmo was anyways, that's you guys decide whatever you want to do. Is that what I'm just saying is in terms of Akash. + +Artur Troian: It's really good that you guys can use the gosh mind that and Akash this centralized Cloud for whatever things that needed but frankly said, I don't think it's a great idea to recreate another console or Cloud. Most just gonna be simply I would say I would highly encourage to build something on top of that. this number one number two is I don't think running testnet. So the consider the testnet as the bareborn of the network and I don't think making templates for ease is a great idea. either simply because the testnet + +Artur Troian: the owners of the network they are supposed to know what they doing and… + +Naman Kabra: right + +Artur Troian: often templates create the layer of Blindness for that's not owners. They don't understand they don't know so they have extra layer of configurations that they need to be aware of. And it just High often hides issues. so at least for a cash, I don't think There will be interest in that because we tend to spin test Nets manually for Big number of reasons. + +Naman Kabra: right + +Artur Troian: I don't think we're gonna change that for the near future. but once again, if you guys have a use for my net Cloud that's amazing. Yeah, I think I covered it. + +Naman Kabra: Yeah, so just to answer on this friend as And thanks for all the inputs really appreciate the feedback. So, definitely the objective for us is not to have creation of testnet and unnecessary node creation for these testnets at all. But an exposure of the test net for testing out things as well right and not just stick in restricting it to test Nets the playground as well as the templates both supports. I mean it's as well here. + +Artur Troian: Yeah, okay. + +Tyler Wright: Thank One thing I appreciate again Naman dear clarification Archer Scott your feedback. If anybody else has any questions comments, feel free to leave them in the chat one thing. I just want some clarification on which is why I wanted Naman you to be here is I know that you've talked about the playground and yesterday I gave you some of the engineering documentation that Scott has been working on for a long time, which is a little bit again more technical but As it pertains to the playground. I know there is a Sandbox environment that's currently in the documentation, which is something that the core team. + +00:45:00 + +Tyler Wright: Connects with people in the community and so the insides of vanguards for people that are maybe not ready for mainnet, but want to test out some things where again there are some providers that are managed those validators on this sandbox. So it's an entire environment that mimics mainnet is your playground idea something and I think Scott was alluding to this is your playground environment have Not have the providers on it similar to The Sandbox and it's just like a coding environment or is it designed to mirror all the features and functionality of the cost Network mainnet and get people access to try things out. + +Naman Kabra: + +Naman Kabra: so I would think of it as option for mean that users to also try out things and… + +Tyler Wright: similar to sandbox + +Naman Kabra: give them an environment wherein they can also, interact and have an pre-configured setup for the right. So all the steps which you see here in terms of installing the CLI creating an account funding those account. Everything is already been set in the back end here, right so they can now just start with the creation side of things rather than installation side of things if I can put it in simple terms. + +Tyler Wright: Okay, that makes sense. Thank you very much. + +Artur Troian: I mean to me honestly so it's good thing for developers to try it out, but my biggest worry on that prospective is What Developers? Are the you guys trying to Target that three or web 2 because if that's about three getting them. So the first of all do you guys have integration for example leap wallet or Kepler? Because that's important number two is + +Naman Kabra: Yes. + +Artur Troian: Yeah, that's number one number two is. then once again, there's a console so I'm trying to assess the differences and I'm trying to see because the cloud Moore's has been acquired by overclock labs and was completely open source, right that everyone can participate in development and use of it? So there's no commercial interest from the prospective. My point is if that doesn't create some, frustration for developers. what we can use why there's okay. There's called MOS and there is a node Ops and what we can use for that. That's what I'm saying. I maybe + +Artur Troian: You may want to consider thinking on building something on top of that just gonna be improving the user experience for developers. another point is once again,… + +Naman Kabra: Yep. + +Artur Troian: that's my humble opinion of that. Was what kind of developers if you still talk about three developers if you talk about Cosmos based chains. + +Artur Troian: Without Smart contracts for example in my opinion developers should know what they doing. Honestly, right just… + +Naman Kabra: Yep. + +Artur Troian: because simply what happens is as soon as they move out. Of the ecosystem and trying to do something real and trying to spin all of the things or set them up manually that becomes really complicated and let's say so okay, we're gonna try it out or not the Ops and then use called most to deploy permanently. That's gonna be a friction point. As well as deploy then maybe manually. another point is + +Artur Troian: I would say building another you are yet. Another UI is probably okay, but I would rather say having the clients for different languages that allows users to emphasize using the API and then use that API as the entry point to try things out would be probably by Northern official. do you guys plan to ask for finding from Akashi Ninja for that? + +00:50:00 + +Naman Kabra: Yeah, so we'll answer from the first question in terms of what developers we are targeting here. I think I started with the same that we're looking to onboard more developers here. So definitely the target would be web to Centric devs and anything and everything that is associated with onboarding them weird hackathon where it Workshop speed anything where we can provide a simplistic environment for them, which is very familiar with what they are already a custom So that's our target audience when it comes to acquiring the devs and we did test it out with Archway got a decent traction as well right to answer in terms of funding site. Yes, we requesting for a grand or + +Naman Kabra: Any form of incentives via delegation program anything that works best. I think Tyler is going to get back to us on that front. + +Artur Troian: I say okay. Yeah, so yeah, we can discuss that on the + +Artur Troian: Solitary, I forgot our top meeting for that incoming. + +Tyler Wright: Steering committee yet. + +Artur Troian: Yeah. Yeah. The question is pretty much no one just to you on that is before the question is how Akash Community is going to benefit from that So this is the biggest question, right? This is good that you guys being things for other chains to do that. But the main question is okay how Akash mean she can benefit from it and honestly saying at least for now I kind of like questioning. There are really nice benefits for cash Community from the prospective. I would say before asking for funding that to explore. + +Artur Troian: what Akash Community are in a contraction Network as my source of the grounds needs and then probably thinking what you can change in not also the akashion network benefits from that because the purpose of the grant is solely to taking Bennett to give a benefit in form of some service to Akash users. Not the other chains come as + +Artur Troian: A side thing. So it's other change benefit from that. That's okay. But the main benefit has to be a customer support users and honestly saying I don't see Akash users to be having benefits. At least from what I saw that but I can be wrong once again, feel free to put that on the discussion and ask questions of what you could extend in node Ops to cash users to benefit. terrible back to you. + +Tyler Wright: Thank I want to I know that naman's on the other side of the world. He's been again joining a couple of meetings. He joined the six support recently. He joined State Community as well recently and gave a demo and then this has been the hands of insiders for some time for them to test. If anybody has any difficult comments. Feel free to drop them in six support then again, we even having some discussions with them on offline about some next steps and books just continue to have those discussions but much appreciate everybody's feedback. I know that I have a hard stop and about three minutes because I have to jump over to Sig providers if anybody wants to join that conversation looking at some of you here again, please feel free to join that conversation. And then it's Artur mentioned steering committee is happening tomorrow. + +Tyler Wright: There's a number of discussions that will be discussed then as well as again Naman we can talk about creating a discussion or next steps as it pertains to no dots. But Naman much appreciate you join the conversation Artur. Thank you for leading us through the typical structuring of the triaging of support issues. If anybody here has any questions about any specific issues that they again are looking at or any issues that are affecting them and they want to get some more feedback on please drop those in six support and we'll meet again in about two weeks and I'll make the recording transcript and notes available for this meeting soon. But I hope everyone has a great day. And again, I'm hoping over to Sig providers. So feel free to join me. There'll be some conversation about content moderation and potentially auditing as hope to see all there. + +00:55:00 + +Tyler Wright: Thank you everybody for our Lively six support meeting. Hope everyone has a great day. We'll talk soon. All right. + +Artur Troian: thanks, everyone just + +Scott Carruthers: That's good. + +Meeting ended after 00:56:07 👋 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/sig-support/meetings/023-2023-12-06.md b/sig-support/meetings/023-2023-12-06.md new file mode 100644 index 00000000..9d375c8b --- /dev/null +++ b/sig-support/meetings/023-2023-12-06.md @@ -0,0 +1,237 @@ +# Akash Network - Support Special Interest Group (SIG) - Meeting #23 + +## 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, December 6th, 2023 +- Time: 07:00 AM PT (Pacific Time) +- [Recording](https://hzvr27yxq5skbo2dwiw6yums3dd4ujzhibdn44zpod5ebxslfinq.arweave.net/PmsdfxeHZKC7Q7It7FGS2MfKJydARt5zL3D6QN5LKhs) +- [Transcript](#transcript) + +# Participants + +- Abiola Oyeniyi +- Alani Kuye +- Andrey Arapov +- Artur Troian +- Max +- Scott Carruthers +- Tyler Wright + + +# Notes + +- Artur talked about Mainnet 9. The upgraded happenned successfully. +- Artur talked about issue 152. Artur asked if this happens after deployment update. Andrey said it does and he will update the ticket. +- Sometime after the new year, there will be discussion of SDL v3. +- Artur talked about issue 132. +- Artur looked at issue 156. This was marked as "needs verification" for now. +- Need to add some labels for items that are coming in the future, or items that need more discussion. +- Artur talked about AMD Support issue 142. There are a couple of things in SDL process or provider that prevents deployments for non NVIDIA GPUs. This does NOT require network upgrade. +- Mainnet Upgrades will be smaller. There are 3 planned for the first quarter of 2024. +- Artur is working on list on ADR records that will describe each upgrade. Look out in support repo for more details. +- Artur talked about Testing environment for Akash Upgrades. Scott is going through all of the end to end testing. SDLs for Testing will be moved into signal repo under Akash API. + + + +## Support + +- Alani highlighted how much he liked the open meetings. Helps to know what is on the project roadmap. +- Support has been steady in Discord and beyond. No out of the ordinary issues. + + +## Action Items + +- Discussion next week with Labels for new features. +- Discuss issue 156 in more detail, to determine solution. + + +# **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, again, welcome everybody to six support biweekly meeting number 23 during these Sig biweekly meetings. The group comes together to look at support issues in the support repo anything that needs triage gets triage,… + +Alani Kuye: It's good. + +Tyler Wright: but led by Archer and the rest of the team we go over any open issues and again assign them put importance on them. Just a General triage at the last six support meeting. We were getting ready for mainnet nine that may not nine has Upgrade has happened successfully. + +Tyler Wright: I'm sure Archer will talk about some future plans. We also outlined some of the future plans for Network upgrades happening in 2024 q1. I think we have three plan for right now obviously subject to change but again had a successful maintenance nine upgrade. I know that out of the last meeting we were talking about some work to the cloud most team is going to be doing with the pretor team in terms of endpoints and I believe that the praise the most team have been able to link in come to an agreement on what the most team can provide and then again there was another issue that will be looked I believe issue 148 that we talked about as an action item. + +Tyler Wright: So again with that being said, I'll hand it over to Archer to have a triage any issues. And then from there I will even though andrey's been away and Scott has been helping to cover. We'll talk about anything that we see in the support channels and then we can open it up to questions comments or if anybody wants has any technical questions for the core team. So without further Ado, I'll hand it over to our turn and I'll take notes in the background. + +Artur Troian: That's not hi everyone. I apologize for my voice today, ultimate of gold. right here first screen, so Yeah, the total number one to discuss is. my net nine that we have successful performance on Tuesday, what was that 28 of November in so that was weeks of + +Artur Troian: carry over issues that was introduced in my net a minute 8 and + +Artur Troian: there was a slight mishap validation of the bit attributes so pretty much what was happening that I need deployment that has multiple Services they should have. equal amount of replica otherwise provide a significant building And we had to pretty much the best way as always to fix. That is the natural great. So anyway, it was really quick to class. Probably I Quantum minutes to apply it. So I think that includes the network of rates for this year. + +Artur Troian: I just closed this issue that we pretty much. + +Artur Troian: Yeah, that's let me see quickly what we have right now waiting for triage. And then talk about some other things. + +Artur Troian: that + +Artur Troian: let's see. What is that about? + +Artur Troian: And you just regression does it happen on deployment update or on deployment create? + +Andrey Arapov: It's when you send Manifesto. + +Artur Troian: No, is it some manifest after deployment rate or after the point of daily? + +Andrey Arapov: After deployment has been updated not create. + +Artur Troian: So that's the point of that. + +Andrey Arapov: I never seen it on after create. + +Artur Troian: Can Update the description of the issues that happens on deployment of date and… + +Andrey Arapov: Yeah, okay. + +Artur Troian: we can move on. Is that Thank you. All Awesome the triage. So that is one actually. + +00:05:00 + +Artur Troian: okay. Thank you. I'm gonna + +Artur Troian: Put it out. What else do you have? + +Artur Troian: They are going to find deployment Trace period what is that? + +Artur Troian: I think yes, so. we're gonna leave it in the triage simply because it's + +Artur Troian: it's much broader topic to discuss honestly. We have plans to plastic changes to the STL and the Manifest next year So sometime after you start discussion about sdlb 3. And an idea is that so the sdl itself is not definitely here. it's dirty with you, but Over this years we realized that people rely on sdl inscription What kind of feature supported on the network? So what you're gonna do is we're gonna introduce Asia three. This big changes of the layout and the format for marketing Etc and kind of pictures. + +Artur Troian: and that you then Define the things manifest and provider Behavior, and that idea of the review three years. + +Artur Troian: To have it by more easily expanded with new features. because current format implementation is kind of a little bit hard to extend for number of reasons. It serves a purpose for sure. But as the natural grows up the demand for features grows up we have to move on. So yeah, let's + +Artur Troian: Let's have it American for jazz. Tell her let's have a discussion maybe sometime next week. So we need to put a few levels. I don't want to call them sdlb 3 but that's kind of like API changes or new future. Milestones anyway, yeah, you're gonna discuss that we're gonna leave it in the right Andreas, but hopefully some kind of thing. We are gonna have discussion on things. sorry. I open that issues in the new window and you guys didn't say sorry about that. Anyways, yeah, that will be for the next year. All right moving on the last. + +Artur Troian: Yeah, I think that's the bug. I'm gonna give it a check what's going on here? So then + +Artur Troian: yeah, we're gonna say, they're not here and if you make things this year for that. All right, Come on, seven. + +Artur Troian: Okay. + +Artur Troian: Right and what else was sees I have onion label issues. + +Artur Troian: through the blue + +Artur Troian: are you pretty much want to increase the + +Artur Troian: yeah, because it's an image + +Artur Troian: Yeah, once again, it's slightly broader discussion about that simply because you need to see how Goal, not require is gonna handle that. But yeah, that's a good discussion. Okay. Let's see. + +Artur Troian: to so that's the thing to talk for the next year. See what the best option. For that. Okay, I'm gonna pull this verification. And if you need to introduce some new levels for this kind of thing, so that's probably a good question actually. Any from this? time and + +00:10:00 + +Artur Troian: all right. and that is + +Artur Troian: FBI and provider All So a thing we don't have any unlibal issues. Just one moment. yeah, so the energy support. + +Artur Troian: When we introduced gpus area this year. The intention was to support pretty much impossible Wonder initially were focused on the Nvidia support and it's not kind of the thing that it means also called to introduce the mdv. The code base is intention to these and you support all there are a couple things in the sdl parsers as well as in the provider building process that runs actually deployments. This end with any GPU and we get GPU to be created. We're going to be removing that safely this week and it doesn't require nothing break. We're just gonna be right binary version. + +Artur Troian: And that will be completely compatible with the existing Network. So we will try to release it sometime this week maybe over the next week. okay, everyone already from that and + +Artur Troian: This is Academy behind on them. Right and anyone. + +Artur Troian: And there was a longer issues to talk about. Don't Buccaneers. yeah, I think I asked him to reform out the HDL. I don't think + +Artur Troian: we're gonna close it. It's not an issues. And let's close it. There is nothing we can do about that. All right, so that concludes the reaction process. Let's double check if we have anything unable. Nope. And anything already Josh? Yeah, that' actually doesn't. All right, so we don't have any more issues to talk about from the support reboot a couple things anybody have any questions about that. + +Artur Troian: All right, so just to wrap up this year. I think you're gonna have one more six support but I started mentioned. We have quite a few Network upgrades plan for next year. And as always we are trying to release them. + +Artur Troian: Teacher practitioner. So for example, we will try to put as little as possible in each Network grade simply to prevent issues during the upgrade and something goes wrong. Sometimes hard to guess what's going on? There's multiple features included our multiple migrations. + +Artur Troian: We are working on the list of AGR records that gonna describe what does upgrades about and we're going to post them by end of this month. But to go ahead on that. There are three at least Network Embrace plant or you want 2024. The first one is changes to governance that allow us to have different War periods for different governance proposals as well as introducing feature called proposals so to put in the perspective right now every government proposal regardless of his type has seven day walking period which is + +Artur Troian: most of the time is good. But sometimes we need to first of all to make a proposal quite expedited. For example, if Network operating goes wrong of the bark. We need to carry over the fix for that and we have to wait seven days. So a year of expedited proposal is that says something goes wrong we should fix and if we issues expedited governance proposal upgrade. We have 24 hours to reach consensus on that. So right now that I'll get things. It's just holding power if that's reached the great can be applied. Within 24 hours after the issues up on the network and it applies not only upgrades itself. But parameter changes are a community span, whatever. + +00:15:00 + +Artur Troian: As well as we will have different default volume areas when you proposal types, I think. For social great itself. We're gonna cut it down from Southern basically before once again, it's debatable and it's gonna be able to change it through the parameters and then for rest, we're gonna just keep it seven days. Anyways, that's gonna be again a good point of discussion in the form. another upgrade will be related to Marketplace. if you want to have + +Artur Troian: So right now when this is being closed by the provider or the network? the only reason to see that is overall deployment overdrawn escrow on And often happens usually damn, my list was closed and it's hard for them to see why and that's actually quite a good question. So what we are going to do is we're going to introduce some sort of status in the lease And once lease is being closed by the provider or actually by anyone my client by Talent by provided by the network. We're going to be dedicated reasons and overdrawn or deploy one of the services was unresponsive. Or wider is going down for whatever reason. + +Artur Troian: So yeah, that's gonna give way more visibility for everyone starting from UI client console and down to CLI and anyone imagining that there's gonna be a great number two upgrade number three is Packet forwarding this is the feature that is kind of important for title payments because that allows us to use 19 years to see we have been kind of implemented but it needs so testing and we decided not to pull The trigger on that one by Under the year issues doesn't make sense. Everyone is going to be in the rush and people start to actually disembark work locations. So we will plan it once again for you on 2024 and obviously the cosmos SDK + +Artur Troian: We are still on the Zero 45 which is quite old and it's been deprecated. So the target for us is after governance. Changes, which is the number one upgrade. Not a new year. We'll start working on migration migrating to the ecosystem Decay or seven or even probably 50 that's gonna be long task as there are so many Breaking changes we have to do race or testing and that's the topic. I want to talk about today as well. But I don't know when but hopefully sometime next year we're gonna update to a currently supportive mainstream version of the vehicles any questions to that? + +Artur Troian: Okay, and last but not least is. Testing so pretty much all over the Sierra years and build quite that's the environment. And the probably biggest hiccup we have is we have this fastest scenarios and sdls cut it around multiple repository. So right now Scott is doing tremendous job pretty much going through all of the the unit test and to understand and documenting what kind of edge cases we actually cover then we're gonna take all the sdls. We're gonna move. them into + +Artur Troian: a single repositories is going to be under Akash API and that will be reference is the health for all of the testing that allows different implementations. for example, go is your partner. Yes, and so forth to use them As well as we are going to try to put some good. + +00:20:00 + +Artur Troian: Probably schema. We still need to figure out what was right to do that but some kind of schema that's gonna describe actual sdl structure and the template against which it can be validated. or age numbers like the mean marks for the CPU and so on so forth. We want to have that the single place to check if implementation of the specification is actually about it. so once again right now we are in the process of just collecting and documented all of the places where the sdls are okay that we're gonna then move them all in single place reformat them. Make sure we use up-to-date images and so force and after that some documentation changes coming up, I think that covers it for today. + +Artur Troian: Dollar back to you. + +Tyler Wright: Thank you Archer. yeah, I just want to send out all the work that Artur in Scott are doing with the end-to-end testing and again, that'll be made available soon. I also want to just shout out in 2024 as we did in 2023 when there was a new. + +Tyler Wright: Network upgrade we put a new issue inside of the support repo that had a Sig chain as a classifier and then put that specific Network upgrade as the main title. What we're going to be doing in 2024 is keeping with that same practice but adding again a temple ties version which will be a checklist of all the various steps that go into Network upgrades so that again folks in the community can track what's going on where we are in the process where the core team is in the process and where the folks and from the community can get involved potentially with testing and Beyond. + +Tyler Wright: And again just want to shout out all the validators that have been really stepping up to the plate over the past month or so with these various upgrades. So we'll continue to stay in close communication with all the validators as we Implement new structures and get their opinions on that and as we continue to make feature improvements and continue improve the Akash Network. Does anyone have any questions about any issues that were triage today or any issues that are open in the support repo that anybody wants to discuss in further detail? + +Tyler Wright: One thing I want to remind folks and again folks in this call. Especially insiders can let folk other folks in the community know we are always looking for more people that can contribute to issues in the support repo. + +Tyler Wright: Obviously there is a deep technical understanding that is required to contribute to the core code base. There is time being allotted during these meetings during the six support biweeklys where anybody with go experience wants to tackle. Any open issues. They can describe their skill set describe the kind of issues that they want to ask any specific questions and then take these meetings that happen every two weeks to get some feedback again get some technical support for members of the core team ask any technical questions. And again, there will be bounties available for folks that want to contribute to solving issues in the support repo because I know that we have a very small core team that's doing a combination of keeping the network up and running. + +Tyler Wright: looking at issues solving issues tree housing issues building new features. So again, really hoping to rely more on folks in the community that have technical understanding as we move into 2024. So there will be time allotted at the end of these six support meetings for folks that have any questions again Scott and we just had a meeting about this prior Scott Carruthers have done a great job of developing engineering documentation for folks that want to dive a little bit more into the weeds of what a cost network is and how the Akash network works. So obviously we have developer documentation for folks that want to use the Akash network. But again with the website revamp, there will be engineering documentation. That'll be a little bit significantly more Technical. And so again as we move into 2024, please look out for folks that want to be contributors to the core product through push them my way or push them towards + +00:25:00 + +Tyler Wright: support and then we can again assess their skill set and hope to get more folks involved working more closely with Scott Archer Andre and the rest of the team. + +Tyler Wright: Cool, if there's no issues that anybody wants to talk about in the support repo that are open at this part of the agenda. We usually hand it over to members of the Insiders entree to discuss anything that they've seen over the last couple of weeks in Discord or in other channels as pertains to issues from the community. This gives us the ability in close to real time understand what's going on with the community whether we have to update documentation whether there some folks are having the same kind of issues and maybe this is something that should be turned into a feature request, but I know there's a couple of members. I know that Andrey was on vacation. So usually I would ask him but again, he's just catching up himself Scott was helping to cover while he was gone. But I want to see abiola or Max. Have you all seen anything in the community? That's + +Tyler Wright: worth discussing on the support side with the core team + +Tyler Wright: You don't feel like you have to talk, but I just want to see if there's anything that you saw out there. That might be worth sharing. + +Max: It does for me. + +Tyler Wright: Great segue in Max talking again Cloud notes is a preferred deployment tool. I think that's very clear at this point. And there is a specific repo for most related issues. There's a specific channel in Discord ecosystem Cloud most and I know that the cloud most Team Max here as a representative does a great job of keeping track of issues that are reported in that repo and then he and the rest of the cloud most team work to solve those issues has those issues so if anybody has any issues Cloud most specific again, there is a repo where you can drop those issues in there and they get seen in very quickly and saw very quickly. So I just want to shout out Max again for all the work that he does with the cloud most tool. + +Tyler Wright: Anyone else have any issues or anything that they've seen on the community front that might be worth talking about? + +Tyler Wright: If not, no worries. + +Tyler Wright: So, it's Artur mentioned. We'll have one more six support meeting before the holidays really kick off where again triage any issues after that. We will probably take it two week break. So we'll have a month between that next meeting and I'll just update the calendar as such again. There will be some discussions happening over a next couple of weeks that pertains to a potential governance proposals happening or potential upgrades happening in the new year and various processes. And again, look out for any updates happening to the support repo on any specific issues. We'll be updating some of the templates as well as we get ready for 2024. + +Tyler Wright: Much appreciated everyone's participation again. Is there anything that anybody has any questions on the technical standpoint that Archer Scott's or anybody else could answer here today? + +Alani Kuye: Very quickly. It's not so much a question. Just want to thank you guys for Sharing all this information. It's nice to see what's ahead. It's also always nice to at least have a good idea from a roadmap perspective updates and areas for participation community members. So just want to say thanks Art And Drake Scott next Ty yourself. I mean, I think you guys have been phenomenal and it's nice to just jump in once in a while and catch up. + +Tyler Wright: much appreciate that. I'm on that note Alani I do and we'll talk about this again quick. Shout out to the steering committee, which again has been moved to this Thursday. + +Tyler Wright: In terms of roadmap. We are starting to use project forwards and you've seen that in the last steering committee where again a number of the items that Archer and the rest of Team talked about today, whether it be around AMD support or some of the other items that are being worked on by the engineering core team are in that project board, which is completely public and you can kind of see again all the work that's happening across a number of different engineering efforts by many members of the team so you can kind of see what's in the backlog what's up next again, and I know I don't want to jump the gun, but I know that Archer and the rest of the core team have been thinking about secret management and private repos and have been thinking about, implementations there. So again, + +00:30:00 + +Tyler Wright: There's a number of things happening and you can kind of track all the things that are going on using that roadmap, but much appreciate everyone's time today again as Alani said really enjoy these meetings really enjoy working and connecting with all of you. If there's nothing else and I hope everybody has a great rest of their day and steering committee tomorrow. I believe there's Sig economics happening later today. So a lot on the agenda and we'll just continue to work together online one more shout out to or call out sink clients is going to be happening next week where there'll be a number of folks Max will be there representing the cloud most team and there'll be other representatives of clients on Akash and we'll just do a year-end review and then look ahead to what some folks have on there project roadmaps for 2024. So let's look out for that in Discord. + +Tyler Wright: I hope everyone has a great rest of the day. Thank you all again for participation today. Thank you Archer for leading us through. the support repo + +Tyler Wright: Talk to you all soon. Have a great day. + +Scott Carruthers: Thanks, everyone. + +Tyler Wright: All right. + +Andrey Arapov: Thank you. + +Meeting ended after 00:31:57 👋 + diff --git a/sig-support/meetings/024-2023-12-20.md b/sig-support/meetings/024-2023-12-20.md new file mode 100644 index 00000000..7d1b3643 --- /dev/null +++ b/sig-support/meetings/024-2023-12-20.md @@ -0,0 +1,292 @@ +# Akash Network - Support Special Interest Group (SIG) - Meeting #24 + +## Agenda + +- Participants will look at issues in [Akash Support Repo](https://github.com/akash-network/support/issues). +- Scott Carruthers will lead triaging issues, and discussion of implementation for issue fixes. +- Scott will discuss Support from the community and ask for any community feedback. +- Participants can have an open discussion of any other issues or support related items on Akash Network. + +## Meeting Details + +- Date: Wednesday, December 20, 2023 +- Time: 07:00 AM PT (Pacific Time) +- [Recording](https://kesic5sqastbfceerxf7d5zcqcumbjpipfw45q6oxxmcguazpotq.arweave.net/USSBdlAEphKIhI3L8fcigKjApeh5bc7Dzr3YI1AZe6c) +- [Transcript](#transcript) + +## Participants +- Andrey Arapov +- Max +- Rodrigo Rochin +- Scott Carruthers +- Tyler Wright + +# Meeting Notes +#### Tyler Wright +- Mention of bounties available for those contributing to solving issues in the support repo. +- Discussed desire for increased community contributions on open support issues in 2024. +- Biweekly meetings will continue, providing an opportunity for participants to ask questions to the core team and refer to Scott's engineering notes for deeper understanding. +- Participants urged to review Scott's engineering notes for a better understanding of Akash Network's technical aspects. +- Recognition of Scott Carruthers' work on testing, especially for those building on top or setting up their environments. +- Anticipation of increased testing opportunities in early 2024 for local environment setup, simulating core team work. +- Confirmation of three planned network upgrades in the first quarter of 2024. +- Mention of action items related to labeling in the support repo. +- Reminder of further investigation needed for issue #156, to be discussed in the January 10th meeting. + +### Issues Triage Session +- Andrey Arapov explains the [issue #166](https://github.com/akash-network/support/issues/166) related to Wild Card use and GPU models in bid prices. +- Issue arises from bid price script selecting the highest value without knowing GPU availability on the cluster. +- Andrey proposes a solution involving Akash provider recognizing the scheduler's deployment allocation for unspecified GPUs. +- Scott Carruthers assigns the issue to Arthur for further review and possibly assigns subtasks to Andrey. +- Discusses the second unassigned issue created by Arthur related to migrating client go code away from the node repository, planning for work in 2024. +- Mentions a third simple issue about HTTP options in go code with a proposal to change from uint32 to uint64. +- Decision to assign the second issue (client go code migration) to Arthur for clarity +#### GPU Reporting, Issue #137 +- Max raises a concern about a GPU reporting issue causing a crash when indexing providers and their resources. +- Scott acknowledges the existence of an issue related to wrong GPU reporting with an extremely high value. +- Andrey Arapov provides details on how the issue can be reproduced by restarting the device plugin and suggests a potential solution involving a simple check in the Akash provider to handle wrong or incomplete information. +- Confirmation from Andrey Arapov that the count returns to normal after a while. +- Andrey Arapov suggests testing scenarios with multiple worker nodes, some with GPUs and some without, to observe how the device plugin handles this configuration. +- Scott Carruthers recalls past testing scenarios and agrees to revisit and conduct further testing to understand how the device plugin operates in different node configurations. + +### Support +- Tyler Wright emphasizes the importance of the Discord channel for technical conversations and support within the community. +- Acknowledges the efforts of insiders and vanguards who make themselves available 24/7 for user queries. +- Tyler Wright gives a shout-out to Max for his responsiveness in addressing Cloudmos-related issues and encourages users to post such issues in the Cloudmos repo. + +#### Other matters discuused +##### Kernel Version Issue in Providers +- Andrey Arapov shares information about a potential issue related to providers losing leases, pods terminating, and worker nodes falling off. +- Mentions that the issue may be caused by running a newer kernel (above 5.15 ) on the host, leading to CPU performance problems. +- Recommends downgrading the kernel to 5.15 or adjusting liveness probe timings as workarounds. +- Highlights the importance of not over-provisioning resources and suggests managing resources dynamically. +- Tyler Wright expresses gratitude for the information and suggests posting a written format or announcement in the providers' announcements channel. +### Action Items +- Further investigation of issue #156 to be discussed in the January 10th meeting. +- Group to do more investigation to understand the persistence of the high count in GPU reporting, Issue #137. +- Andrey Arapov to create a written document or announcement regarding the kernel version issue and share it in the providers announcements channel. + +# **Transcript** + +_This editable transcript was computer generated and might contain errors. People can also change the text after it was created._ + +Tyler Wright: All right, welcome everybody to six support biweekly meeting number 24. The special interest group for support meets every two weeks to go over triashing any issues in the support repo where all issues related to core product live on the Akash Network. In addition to triashing any open issues or any issues waiting triage on the group goes over and goes over any open issues that need for their discussion further insights Etc. And looks for folks that want to be assigned those specific issues. Again, anything related to the cash core product? Goes inside the support repo inside the Akash organization. + +Tyler Wright: One thing I also want to call out is we move into 2024 is the desire for this is something we've talked about more Community contributions on open support issues over the last year Scott Carruthers from the core engineering team has been putting together documentation that is more engineering focused. So again, I know that this is the last six support biweekly of 2023. We'll take the next couple of weeks off. + +Tyler Wright: Certainly, there are bounties available for those that want to contribute to solving issues and support repo again. There will be these biweekly meetings. We're folks that want to take on solving issues can ask any specific questions to members of the core team as well as again have a chance to take a look at these costs engineering notes that Scott has put together as reference points as reading materials to dive deeper and into the technicals of the Akash Network and how it works. + +Tyler Wright: So that's something that will be more of an action item for 2024 for folks that are joining these six support meetings. The goal is to have more participation from technical go developers in the community that can help with again support issues and can participate more in the development of the core covids. + +Tyler Wright: part of me cool out of the last six support biweekly meeting number 23 the group went over Maine at nine Archer led the group and talked about some of the issues waiting Triads as well as described the network mainnet upgrade schedule. For 2024 again to reiterate there's a three-planned network upgrades happening in the first quarter of 2024. But the goal is whether there's more or less to have smaller Network upgrades so that again testing can be much more efficient and faster. one thing I want to call out on the + +Tyler Wright: project board is the work that Scott Carruthers who's on this call has been doing around and testing again for those that are looking to build on top or looking to set up their own environment or against solve some of these support issues in the support repo. There's going to be a lot more and testing in early 2024 for folks to set up on their local environments. It's kind of simulates a lot of the work that the core team is doing so look out for that as well. I know that there are some action items that have last ly. With the holidays here. And again, we'll be skipping. I believe the next couple of six support time slots. So the next six support biweekly meeting is planned for January 10th. + +Tyler Wright: part of me with that being said there's a couple of action items from last session around labeling and adding some more labels to support repo as well as further investigation of 156 that we'll talk about We'll talk about January 10th. + +Tyler Wright: I know archers out of office this week, but again another key member of the core team is here to lead us through triaging of issues all hand over to Scott Carruthers to lead us through the triashing of any issues of waiting for us. + +00:05:00 + +Scott Carruthers: All right. Thanks Tyler. Let me share my screen. + +Scott Carruthers: All right, so I was doing a review of the open issues and unassigned prior to the call. So I think we might have three to go through so probably will be pretty brief. So the first one and as a issues that you opened a couple days ago regarding Wild Card use and a GPU model and in the bit price that we're responding with do you want to In your own words go through this issue. + +Andrey Arapov: Yeah, so basically when someone requests GPU and a bit price script basically takes the highest view from the list but not the one that is available on the cluster because bit price script cannot know this information prior and bit price script and provider doesn't receive the information about which the appear available it is going to Allocate the deployment for so because of this some providers they will be basically bidding for lower and with the highest end GPU pricing. It's because of the workaround specified there you can click this automatically sets underlying under underscore. + +Andrey Arapov: Yeah, this one is the issues. I was creating prior and this is a consistency. This one is So on the partial workaround had to be done well because of similar issues but vice versa so basically to prevent someone when someone requests and deployment without the particular GPU set + +Andrey Arapov: so the trolls back to some value which is the value of the highest usual about it because for instance provider can have several worker in Authority in a single worker note and can have low end and high-end gpus and providers will want to make sure that they beat on the deployment request that record do not specify the individual GPU if they don't know what they want to see it, but the problem with that, the recently implemented on the cloud most the availability of the GPU in bid itself so we can see which the few but it happens after it's like the + +Andrey Arapov: positive events action. So the core issues that it's impossible to know which the cash provider will be allocating for particular requests, which doesn't specify the GPU explicitly basically, so it's something that should be done on the cash provider level itself or on the bit price script Which is less likely because then it would take probably longer time to respond and would probably require more permission to query the cluster which is Not probably the best decision. I would say Arthur would be the best person to decide here. But my take is that + +Andrey Arapov: provider should be able to recognize to which this scheduler is going to deployment to when the GPU is not explicitly specified in the islipment request. So even that's clear. + +Scott Carruthers: Yeah, no, it's clear. And yeah, it was clear to me. I'm even just reading through the description. But yeah, I wanted to let you go through the issues as well. So yeah, that's even more thorough description see a couple it makes sense that we need to have that information before the bid. So I'm just going to assign the starter and possibly. He'll want me to take a look at it as well. But I'll just sign it to Archer current + +Andrey Arapov: Yeah, yeah because the whole thing it happens the way that it creates. a bit + +Andrey Arapov: and reserves the space but doesn't know which exact GPU is there maybe it knows post action, but I think it's possible To know beforehand at the same time because when provider issues the beat and when broadcasting the network there is information about which GPU so it's possible. I think it's already kind of does it but somehow it needs to pass this information to the bit price script and what it currently passes is everything but this I think so. I think that maybe it's not even difficult to implement. It just needs to specify this information for the big price screen, basically. + +00:10:00 + +Scott Carruthers: And if he wants me to take a look at it, we can make that decision took the away in treehouse are off and set it as sub to Andy. Are you okay with sub 2 designation? + +Andrey Arapov: Yeah, definitely. It doesn't really break things much just offers the lower end GPS in some particular cases for the price of the highest and GPU, but it's not It's suboptimal, but it's definitely not so one but something like have to be fine. + +Scott Carruthers: Yeah, okay. Yeah, I definitely definitely understand the issue providers with multiple GPU models, maybe bidding very high prices when essentially a lower end GPU this extended so yeah, definitely. understand the severity + +Scott Carruthers: Okay, so we now have assignment for that issues so that leaves us two more another one that was unassigned is one that er. created to migrate the client go code away from the notary pository and into the Akash API Repository. Not entirely sure why he didn't assign this when? He created this issues. So this is just obviously some additional item and they roadmap in the backlog that we will be working on the engineering team. I'm probably in the very part of 2024. So not exactly sure why Archer didn't Assign this I think I might show you going to leave. This is on a sign just so that when we go through these issues. I'm gonna assign us Archer just because he created the issue. + +Tyler Wright: Yeah, I think we should have signed to Archer might just be oversight and I'm sure he'll do it sometime very soon. + +Scott Carruthers: Yeah. + +Scott Carruthers: and then again, I was kind of reading through some of these unassigned before our call and then next one is a pretty simple issue at least from their request perspective. I haven't reviewed. + +Scott Carruthers: possible impact or so essentially the issues here is in the go code for HTTP options. They + +Scott Carruthers: Variables are set to un32 so that prohibits. Change the HTTP options Max body size when this user is trying to go above the maximum lineup limit for a un32 So He suggests. I know we changed it from un32 and the go code to un64 so obviously pretty simple change within the go code Might need some further investigation to make sure that there's no issues with that, but theoretically should be for other reason. So something right Repository? I'm just going to assign both Archer and myself to this one. + +Scott Carruthers: type + +Scott Carruthers: Any thoughts are? comments on this issue + +Andrey Arapov: Yep. + +Scott Carruthers: that completes any of the issues that were created in the last two weeks since we last meant that had not been assigned. So obviously we can go into additional conversation about ones that I just went through are issues that have been assigned but we just want to devote some additional conversation live here together. I guess I'll kind of open it up to the floor any. For their conversation needed on the ones that we just covered or any of the issues that were assigned prior that we haven't covered this morning. + +00:15:00 + +Scott Carruthers: I heard a hand raise. I'm just looking at the issues So whoever Rings their hand, please go ahead. + +Tyler Wright: Go ahead Max. + +Max: Hey Scott, I'll show if you talked about it, but I wanted to raise the issues about the GPU. Account that is a huge number and the one that we talked about on this card. + +Scott Carruthers: Yeah. There is a current issues for that. + +Max: Is there an issues good for this? + +Scott Carruthers: What would that I'm trying to think of the title for it definitely does have a issue. + +Scott Carruthers: but yeah this short answer to your question is they're definitely is a issue that's assigned to the issue that we've always had with this and this continued after + +Scott Carruthers: the latest experience last Friday is I not been able to reproduce the issue. Open but we don't know what causes the issues that when this initially came up. They provider that encountered it had recently. moments before this issue happened. They removed a GPU card from a running server and there was some faucet possibly that could have caused the issues. I don't have a physical server with a GPU card that I can test that but yeah, there are definitely as a issues for it. And now we're trying to determine how we can reproduce the issue. + +Max: Okay, cool. I think I see it at the bottom there wrong GP reporting extremely high value. + +Max: The one just below that the highlighted one. 137 + +Scott Carruthers: 137 okay. + +Tyler Wright: Okay. I said yeah. + +Max: because yeah Andrew, I don't know if you talk to him the privately that he was having that issues and it made it so that when we + +Max: when we index the providers and their resources it crashes because the numbers too big and makes it so that his provider is a displayed as offline on cloud moves and + +Max: And obviously Butters in because you can't get bids from others. + +Andrey Arapov: Yeah, I was able to reproduce it. + +Scott Carruthers: Yes. + +Andrey Arapov: I recommended it before. + +Scott Carruthers: I'm sorry Did you say you were able to reproduce it? And did you make a comment in the session? + +Andrey Arapov: Yeah, yeah, that's correct. There is a comment in the bottom of it. + +Scott Carruthers: Are you talking about this or maybe could you just review? So how are you able to reproduce the issue? + +Andrey Arapov: So basically if you bump the common delete pods all for NVIDIA device plugin namespace, it makes them restart and while they're restarting the cash provider, it fits based on the information from this plugin that gets this having for about how many available dupus it has and probably when doesn't get the proper information, I believe it falls back or maybe in video device plug-in gives this wrong number or not even digit at all. And so a cash provider it's the wrong information. That's my presentation. And when you query status endpoint, it's for three slash status from the cash provider you get this very high years number as you can see in the GPU column. So, I think it's a matter of some simple check in the car provider just if you + +Andrey Arapov: Get some wrong number don't display it or convert it into something maybe wait in the device plugin to initialize for fully something like this. So it's kind of issues quite clear for me. + +Scott Carruthers: Yeah, so all that makes sense. so when you were doing your testing there and Max I believe in our conversation on Friday. We talked about this as well. So there we have definitely seeing an issue when they device plug-in is restarting that it represents that very high count, so I think it would do that 100% of the time but in Normal Practice or the normal experience it would then normalize after the device plugin at normal operation. + +Andrey Arapov: Yeah. + +Scott Carruthers: So in your testing did that number eventually return to normal or did it stick at the + +Andrey Arapov: Yeah. Yeah, it returns always as you can see on the screen the very same screenshot the second time around the provider info which queries the states and point. It returns back to the normal value. So it doesn't get stuck in this High number and large numbers. + +00:20:00 + +Scott Carruthers: yeah, yeah and so possibly they're related one known until we dig into the issue more but The issues with that we've experienced now twice one with inter Milos provider and then the original DC Norse experience with this is the number never returns to normal so last week when enter mellow was experiencing this issues that very high count persisted. So we do know that we can reproduce the issues by restarting the device plug-in, but they think that we're not able to reproduce as the circumstance where for some reason that very high count persist. + +Scott Carruthers: Does that make sense? + +Andrey Arapov: Yeah, so there is another issues probably wanted to proceed when this High count number persistent. It's something else probably yeah. + +Scott Carruthers: Right. Yeah. + +Scott Carruthers: Okay, so yeah, Max are definitely as an issue. and yeah, that's basically we're trying to come up. So we do know that we can reproduce the temporary high count and that probably needs to be addressed as well or unable to reproduce the issue where for some reason that I count persists. Andrew Miller was actually able to resolve the issue and he believed that it was attributable to mislabeling. of his nodes, but it's kind of strange because the inventory operator if a node is mislabeled It seems very strange that that would manifest itself into a very high count. I don't know why miscellane the node would have that issue and IFA tested this when DC Norse originally had the issues as well and Miss labeling, no definitely did not reproduce So that obviously would be a very + +Scott Carruthers: severe issues something that's very easily reproducible by line. a node, but that's certainly didn't reproduce the issues for me. But Andrew Melo claimed that when he adjusted the labels at somehow rectified the issues. Yeah. I heard another hand go up. + +Andrey Arapov: Yeah, I a guess there are two ways to two types of labels one label where you just specify which capability which kind of GPU or you're working on has our range of the peers and the other ways relatively new one type of label where you can say Hey, listen media device plugin run only on this particular working nose and the GPU it's a selector know it's a recent one. And with this you can have actually the device plug-in running, but I mean, it won't actually run on the specific notes maybe relation or correlation of related to this kind of label was causing another trouble,… + +Scott Carruthers: Yeah. + +Andrey Arapov: but It All Leads to basically I think the way how because in the end of the day the provider it's the information from the plugin I believe or from something in between from the conversation. And then it presents this High count value. I think it's still on the provider side where it needs to filter this information and either present zero when it cannot read it or when there is super high count which is not thermal and wait until slices and then once it's initialized then display normal account, which is about want to 10 20 something like that my opinion + +Scott Carruthers: Yeah, I definitely makes sense of the account should be represented as 0 as the plugin is initialized so I'm definitely familiar with the label that you're referring to so that we can control the device plugin only. Spawning on worker knows that have GPU resources and we can control that. I thought that Andrew Melo was insinuating that it wasn't that labeling, but it was actually they per worker no labeling of specific GPU models not the device plugin label. But I have to go back and review the conversation. + +Andrey Arapov: Yeah, I think it's good point and another Point like we think have never tested having more than one working out and having a video device plugin running on those notes that do not have GPU and so that to have the mixed in the configuration where you have health or part of the working also with GPU and media plugin running and half of the notes or one of three doesn't matter these without GPU. But with the India the best plugin, I'm not sure how it handles. This thing could have maybe someone tried it. I don't know. It's another good point to test probably + +00:25:00 + +Scott Carruthers: Yeah, we definitely could do some additional testing on that. I think I had that scenario that you're talking about before we introduce the label for the device plugin. So in other words and just simple provider testing where you have + +Scott Carruthers: A master and a worker node, and the master is also a worker node. So before we introduced that label, the device plugin would have run both on the master worker node, and the worker note with the GPU and in that scenario. I don't believe we encounter issues. But yeah, definitely worth testing again possibly that could be related. + +Andrey Arapov: That don't remember the phone with the device plugin actually runs on the control plane node alone because control play No, the usually have the special condition and tolerance I think is for system plugins only and I don't remember if in this kind of configuration that would be actually running on the control plane. But yeah something that we could test along with. + +Scott Carruthers: Yeah. Yeah, I'm in a control plane node. That was also a worker node. So in + +Andrey Arapov: Yeah. Yeah in this case you need to do ok. + +Scott Carruthers: yeah, so we would just say the Envy DP pod spawn on the master node again, which is also a worker node. I'm and it wouldn't start properly because there's no GPU resources. So yeah under that scenario I tested but yeah, we can definitely go back and Tessa further. + +Scott Carruthers: Okay, I'm going to stop sharing my screen. Do I hear another? And up as well. No, I'm good after the screen once over good. + +Tyler Wright: No. + +Scott Carruthers: Okay, so yeah, a loss anyone else has so max. Thanks for bringing up that issue. Definitely an issue is created and again we're trying to reproduce our Pinpoint where that issue is. So if there's no other questions or comments about any other issues, I'm Tyler. I think we can move to the next stage. + +Tyler Wright: Scott. Thank you Andre and Max for participation. Cool, next up on the agenda is a check-in on support channels again Discord telegram, but mostly Discord for technical conversation is a channel that's used by the community. There are a number of insiders and vanguards that make themselves available 24 hours a day by seven. So there's always somebody ideally online to answer any questions from users that are trying to either deploy or become a provider or just have general questions across Network so much appreciate the inside and vanguards. But I want to see. + +Tyler Wright: If rodri Max or maybe Andre who are again quite active in Discord have seen anything of note. And before I get my ticket off and hand it over to that group to see if there's anything of note. I also want to shout out Max. I know that if there's any issues related to Cloud most again, if you go inside the cloud most repo in the cock organization and the issues area, you can feel free to drop any Cod most specific issues in that repo and I know that Max and the rest of the cloud most team are very responsive and again also very responsive inside the ecosystem So again any Cloud most related feel free to drop in the cloud most repo go ahead Andre. + +Andrey Arapov: Yeah, I just wanted to highlight one thing. It's probably not related much for six support, but maybe partially it's about providers. There's less provider owner contacted me yesterday. They've been digging some issues. Basically there is a possibility of issues where it could be that provider is losing some pleases or some general issues or provide report running or not starting or some posts are terminating too long or some of the worker notes like falling off because they'll say literally Calico mode deployment which creates the internal Network on the conversation can be calling off and people don't know what's going on. mean, there is a responsibility like only one instance of this issues. But if you ever see this make sure you'd like to check what Colonel are they running because some people are deciding to go with the greatest kernel and they have a great let's say the + +00:30:00 + +Andrey Arapov: Kernel 515 in Ubuntu 22 up to 6.2. And in this case, what happens is that when your more core CPU gets 100% visualized. + +Andrey Arapov: One of the VMS on that host and in the VM itself there it doesn't matter. What kind of Kernel it can be 515 but on the first it's important if it's 6.2 newer kernel and then what happens is essentially it doesn't really share the CPU Cycles properly and when you're running Calico node, which creates this internal Network and the kubernetes it normally requests 150 Milli cores, like 4.15 and up to 300 mini course and what happens is that this is not enough for it to pass the liveness broke threshold. So there are two ways to fix it. Basically the best one which we did initially is let him downgrade the kernel back to 5:15 on the first not only Williams doesn't matter again. + +Andrey Arapov: It's halted and the other workaround there is lightness probe. You can double it up. So it normally Waits 70 seconds for the Calico note both the up and running but you can double it up up to 140 seconds and then it will be running but still it's not a perfect solution because then other deployments which requesting normally a thousand minute course CPU we should or one week or CPU. They don't want the Performing as good as they supposed to because of this kind of weird conditional kernel there's a thread open also in the proxmox Forum, but this is just for awareness if you ever see any + +Andrey Arapov: Weather or anyone running on the new of the provider some of their deployments complaining about the CPU performance, number one reason is usually over provisioning. It's when people who use VMware or proxmox virtual machine, they say that hey VMS have more CPUs than they should so whenever it's getting really busy then there is because of the CPU cycle of sharing and interrupts They will receive less cycles for the CPU and it will perform much less while they're seeing the same number. So it's number one or provisioning provided should not over provision anything ideally another thing kind of manager dynamically, which is another case. Second thing is make sure that they don't run to new kernel or if they are sure that it's part of this issue. The best is to use the default official Colonel, which is 5:15 or even 20 to 4. So just for information something I wanted to share but + +Andrey Arapov: Just remember that? + +Andrey Arapov: You… + +Tyler Wright: much appreciated + +Andrey Arapov: worries guys. If you forget what I said, you can always ping me. I will try to put it in a rapid into a written format. I think I already wrote it in my notes, but just in case. + +Tyler Wright: Yeah, maybe that's something I know that Andrey do a great job of. What you see things in Breaking time you throw announcements in the providers announcements Channel and pin those items so that people can kind of track on their own but that might be a good place to put it and then again we can make sure that the Insiders are up to date and anybody else that's like providing support. + +Andrey Arapov: Yeah, good point. I'll put some reminder for myself because I'm now signing off and I'll try to remember to do it tomorrow. + +Tyler Wright: rodri max. Is there anything that you all have seen in terms of support that you think is worth sharing or discussing that? + +Rodrigo Rochin: I'm on this part all good. Nothing out of the ordinary just people asking about deployments and Issues with providers but like you said everyone's been answering there. + +Tyler Wright: excellent + +Tyler Wright: excellent All Is there anything else worth anybody wants to discuss right now? + +Tyler Wright: Cool was actually items will continue to track issue number 137 and I believe number issues number one 60 and again, our next support biweekly will be in the new year January 10th 2024. If anybody has any questions in between this meeting in our next meeting, feel free to drop those in the six support Discord Channel or feel free to use and GitHub support repo to leave comments and specific issues or create new issues. And then again we can talk about those once we come back in the new year. + +00:35:00 + +Tyler Wright: thank you Scott for leading us through triaging of open issues and issues awaiting three hours or issues that haven't been assigned notes will be following up shortly much appreciate everybody's time and efforts including all the Insiders at vanguards that are again active in. obviously shoutout Andrey for all the work that he does in Discord helping providers, but helping everybody that Again support babe will be a little bit lighter over the next couple of weeks. I'm sure inside of vanguards and members of the core team will be taking some time with families. But again folks like myself and others will be available just to monitor Discord and be around and again if anything needs escalation, Again, we can make sure it gets escalated to the right parties. + +Tyler Wright: Hope everyone has a great holiday season very happy New Year. And again if anybody wants to look into the Project board to see what's going on the product and Engineering side as well as the marketing Community boards. There will be some bounties that'll be available to the community over the break for folks that we're looking to build onto the top of the cost Network solve some issues and support repo and Beyond so look after those bounties that live in the community and marketing project board in the Akash organization. Again, hope everyone has a great holiday season the happy New Year, and we will talk January 10th 2024. appreciate you + +Andrey Arapov: Thank everyone. Have a good one. + +Tyler Wright: All right. + +Scott Carruthers: Thanks, everyone. + +Rodrigo Rochin: the business + +Meeting ended after 00:37:00 👋 + diff --git a/wg-akash-website/README.md b/wg-akash-website/README.md index b530ae33..8fd15ebe 100644 --- a/wg-akash-website/README.md +++ b/wg-akash-website/README.md @@ -16,23 +16,21 @@ This working group is responsible for managing and improving the Akash Network W | #4 | April 18, 2023 08:30 AM PT (Pacific Time)|[Link](https://github.com/akash-network/community/blob/main/wg-akash-website/meetings/004-2023-04-18.md) |[Link](https://github.com/akash-network/community/blob/main/wg-akash-website/meetings/004-2023-04-18.md#transcript) | [Link](https://3lwm6hsjp3oegyqavdltmteedm5byrrbxhmno5tl3o4arp7roqzq.arweave.net/2uzPHkl-3ENiAKjXNkyEGzocRiG52Nd2a9u4CL_xdDM) | #5 | Tuesday, May 16, 2023 08:30 AM PT (Pacific Time)|[Link](https://github.com/akash-network/community/blob/main/wg-akash-website/meetings/004-2023-05-16.md) |[Link](https://github.com/akash-network/community/blob/main/wg-akash-website/meetings/005-2023-05-16.md#transcript) | [Link](https://5u5wsfaozhazriqhpayhplg44zbxgqo5nv3qdyfpeimwxwxbsghq.arweave.net/7TtpFA7JwZiiB3gwd6zc5kNzQd1tdwHgryIZa9rhkY8) | #6 | Thursday, June 13, 2023 08:30 AM PT (Pacific Time)|[Link](https://github.com/akash-network/community/blob/main/wg-akash-website/meetings/006-2023-06-13.md) |[Link](https://github.com/akash-network/community/blob/main/wg-akash-website/meetings/006-2023-06-13.md#transcript) | [Link](https://bud2d33f4pwvvrxcsfyfo227gfhq3pldl5isjs5ld6c362kcakaa.arweave.net/DQeh72Xj7VrG4pFwV2tfMU8NvWNfUSTLqx-Fv2lCAoA) -| #7 | Tuesday, June 27, 2023 08:30 AM PT (Pacific Time)| Coming Soon | Coming Soon | [Link](https://p77yiz5lalar6mgma6moiew6zcw2hpcpz7tvc2oa3q4kr7e3zxda.arweave.net/f_-EZ6sCwR8wzAeY5BLeyK2jvE_P51FpwNw4qPybzcY) -| #8 | Thursday, August 10, 2023 06:30 AM PT (Pacific Time)| Coming Soon | Coming Soon | [Link](https://s4xeygkmhljsn4hntjfy3iwouyso2x5doxxvvlhvyjfraudrv4aa.arweave.net/ly5MGUw60ybw7ZpLjaLOpiTtX6N171qs9cJLEFBxrwA) -| #9 | Thursday, August 17, 2023 06:30 AM PT (Pacific Time)|Coming Soon | Coming Soon | [Link](https://uqbnueeye424hiv7umqeebeow3umxvbi2beve2moiuelabowtcqq.arweave.net/pALaEJgnNcOiv6MgQgSOtujL1CjQSVJpjkUIsAXWmKE) -| #10 | Thursday, August 24, 2023 07:30 AM PT (Pacific Time)| Coming Soon | Coming Soon |[Link](https://fn5tkawv3bu7oostaqau53jaz55vpz54mm3r7auowlxtxxfmlwga.arweave.net/K3s1AtXYafc6UwQBTu0gz3tX57xjNx-CjrLvO9ysXYw) -| #11 | Thursday, August 31, 2023 06:30 AM PT (Pacific Time)| || -| #12 | Thursday, September 07, 2023 06:30 AM PT (Pacific Time)| || -| #13 | Thursday, September 14, 2023 06:30 AM PT (Pacific Time)| || -| #14 | Thursday, September 21, 2023 06:30 AM PT (Pacific Time)| || -| #15 | Thursday, September 28, 2023 06:30 AM PT (Pacific Time)| || -| #16 | Thursday, October 05, 2023 06:30 AM PT (Pacific Time)| || -| #17 | Thursday, October 12, 2023 06:30 AM PT (Pacific Time)| || -| #18 | Thursday, October 19, 2023 06:30 AM PT (Pacific Time)| || -| #19 | Thursday, October 26, 2023 06:30 AM PT (Pacific Time)| || -| #20 | Thursday, November 02, 2023 06:30 AM PT (Pacific Time)| || - - - +| #7 | Tuesday, June 27, 2023 08:30 AM PT (Pacific Time)| [Link](https://github.com/akash-network/community/blob/main/wg-akash-website/meetings/007-2023-06-27.md) | [Link](https://github.com/akash-network/community/blob/main/wg-akash-website/meetings/007-2023-06-27.md#Transcript) | [Link](https://p77yiz5lalar6mgma6moiew6zcw2hpcpz7tvc2oa3q4kr7e3zxda.arweave.net/f_-EZ6sCwR8wzAeY5BLeyK2jvE_P51FpwNw4qPybzcY) +| #8 | Thursday, August 10, 2023 06:30 AM PT (Pacific Time)| [Link](https://github.com/akash-network/community/blob/main/wg-akash-website/meetings/008-2023-08-10.md) | [Link](https://github.com/akash-network/community/blob/main/wg-akash-website/meetings/008-2023-08-10.md#Transcript) | [Link](https://s4xeygkmhljsn4hntjfy3iwouyso2x5doxxvvlhvyjfraudrv4aa.arweave.net/ly5MGUw60ybw7ZpLjaLOpiTtX6N171qs9cJLEFBxrwA) +| #9 | Thursday, August 17, 2023 06:30 AM PT (Pacific Time)|[Link](https://github.com/akash-network/community/blob/main/wg-akash-website/meetings/009-2023-08-17.md) | [Link](https://github.com/akash-network/community/blob/main/wg-akash-website/meetings/009-2023-08-17.md#Transcript) | [Link](https://uqbnueeye424hiv7umqeebeow3umxvbi2beve2moiuelabowtcqq.arweave.net/pALaEJgnNcOiv6MgQgSOtujL1CjQSVJpjkUIsAXWmKE) +| #10 | Thursday, August 24, 2023 07:30 AM PT (Pacific Time)| [Link](https://github.com/akash-network/community/blob/main/wg-akash-website/meetings/010-2023-08-24.md) | [Link](https://github.com/akash-network/community/blob/main/wg-akash-website/meetings/010-2023-08-24.md#Transcript) |[Link](https://fn5tkawv3bu7oostaqau53jaz55vpz54mm3r7auowlxtxxfmlwga.arweave.net/K3s1AtXYafc6UwQBTu0gz3tX57xjNx-CjrLvO9ysXYw) +| #11 | Thursday, September 14, 2023 06:30 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/wg-akash-website/meetings/011-2023-09-14.md) | [Link](https://github.com/akash-network/community/blob/main/wg-akash-website/meetings/011-2023-09-14.md#Transcript) |[Link](https://s7n2e2tfghnhjtwc3wse3vnami7vmza7npbr65i4orqb3mfmrpba.arweave.net/l9uiamUx2nTOwt2kTdWgYj9WZB9rwx91HHRgHbCsi8I) +| #12 | Thursday, October 12, 2023 06:30 AM PT (Pacific Time)| [Link](https://github.com/akash-network/community/blob/main/wg-akash-website/meetings/012-2023-10-12.md) |[Link](https://github.com/akash-network/community/blob/main/wg-akash-website/meetings/012-2023-10-12.md#Transcript) | [Link](https://5gn7dg3s3faifxnf6w5uqoabieslbqre2ywps2nyhotoc54tvsiq.arweave.net/6Zvxm3LZQILdpfW7SDgBQSSwwiTWLPlpuDum4XeTrJE) +| #13 | Thursday, October 19, 2023 06:30 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/wg-akash-website/meetings/013-2023-10-19.md) | [Link](https://github.com/akash-network/community/blob/main/wg-akash-website/meetings/013-2023-10-19.md#Transcript) |[Link](https://s7n2e2tfghnhjtwc3wse3vnami7vmza7npbr65i4orqb3mfmrpba.arweave.net/l9uiamUx2nTOwt2kTdWgYj9WZB9rwx91HHRgHbCsi8I) +| #14 | Thursday, October 26, 2023 06:30 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/wg-akash-website/meetings/014-2023-10-26.md) | [Link](https://github.com/akash-network/community/blob/main/wg-akash-website/meetings/014-2023-10-26.md#Transcript) |[Link](https://z5ffy5w2liqufhaktycxtjmyyfbrpe5ewae72o7kviwi4eigwrna.arweave.net/z0pcdtpaIUKcCp4FeaWYwUMXk6SwCf076qosjhEGtFo) +| #15 | Thursday, November 02, 2023 06:30 AM PT (Pacific Time)| [Link](https://github.com/akash-network/community/blob/main/wg-akash-website/meetings/015-2023-11-02.md)| [Link](https://github.com/akash-network/community/blob/main/wg-akash-website/meetings/015-2023-11-02.md#Transcript) | [Link](https://5yiuwpekrvtf2cbtg7nlfoox2nccndvl5iydxvqzbv2ppfyomvia.arweave.net/7hFLPIqNZl0IMzfasrnX00QmjqvqMDvWGQ1095cOZVA) +| #16 | Thursday, November 09, 2023 06:30 AM PT (Pacific Time)| Coming soon | Coming soon| Coming Soon +| #17 | Thursday, November 16, 2023 06:30 AM PT (Pacific Time)| [Link](https://github.com/akash-network/community/blob/main/wg-akash-website/meetings/017-2023-11-16.md) | [Link](https://github.com/akash-network/community/blob/main/wg-akash-website/meetings/017-2023-11-16.md#Transcript) | [Link](https://yn2ux6akmd2wog533saw3cl66agmv37r364jgx3n3u5envp6m2iq.arweave.net/w3VL-Apg9Wcbu9yBbYl-8AzK7_HfuJNfbd06RtX-ZpE) +| #18 | Thursday, November 27, 2023 06:30 AM PT (Pacific Time)| [Link](https://github.com/akash-network/community/blob/main/wg-akash-website/meetings/018-2023-11-27.md) | [Link](https://github.com/akash-network/community/blob/main/wg-akash-website/meetings/018-2023-11-27.md#Transcript) | [Link](https://svuqqu3fnqzburnqmdfrvy6bsku3fef2uzsbmspouj5mo2r4gjmq.arweave.net/lWkIU2VsMhpFsGDLGuPBkqmykLqmZBZJ7qJ6x2o8Mlk) +| #19 | Thursday, November 30, 2023 06:30 AM PT (Pacific Time)| [Link](https://github.com/akash-network/community/blob/main/wg-akash-website/meetings/019-2023-11-30.md) | [Link](https://github.com/akash-network/community/blob/main/wg-akash-website/meetings/019-2023-11-30.md#Transcript) | [Link](https://ljuj3z4qnrttv4kg3z5owik37rofcpakeuwvmpqbiesastrh2coq.arweave.net/Wmid55BsZzrxRt566yFb_FxRPAolLVY-AUEkCU4n0J0) +| #20 | Thursday, December 07, 2023 06:30 AM PT (Pacific Time)| [Link](https://github.com/akash-network/community/blob/main/wg-akash-website/meetings/020-2023-12-07.md)|[Link](https://github.com/akash-network/community/blob/main/wg-akash-website/meetings/020-2023-12-07.md#Transcript)| [Link](https://bmafqxmmyqqxc65uxwkpgetv4r6yzlx6g3wsfzqqahumvzo4hrmq.arweave.net/CwBYXYzEIXF7tL2U8xJ15H2Mrv427SLmEAHoyuXcPFk) +| #21 | Thursday, December 14, 2023 06:30 AM PT (Pacific Time)| Coming soon | Coming soon| Coming Soon ## Leads @@ -41,6 +39,7 @@ This working group is responsible for managing and improving the Akash Network W - Tyler Wright - Zach Horn + ## Contacts - [Discord](https://discord.com/channels/747885925232672829/1111762354242338876/1144276254699298826) diff --git a/wg-akash-website/meetings/011-2023-09-14.md b/wg-akash-website/meetings/011-2023-09-14.md new file mode 100644 index 00000000..257443e7 --- /dev/null +++ b/wg-akash-website/meetings/011-2023-09-14.md @@ -0,0 +1,414 @@ +# Akash Network - Akash Website Working Group (WG) - Meeting #11 + +## Agenda +- Token Page Updates +- Update on "Get Started" Page +- Discussions on Content of the "Get Started" Page + +## Meeting Details +- Date: Thursday, October 19, 2023 +- Time: 6:00 AM PT (Pacific Time) +- [Recording](https://s7n2e2tfghnhjtwc3wse3vnami7vmza7npbr65i4orqb3mfmrpba.arweave.net/l9uiamUx2nTOwt2kTdWgYj9WZB9rwx91HHRgHbCsi8I) +- [Transcript](#Transcript) + +## Participants + +- Denis Lelic +- Emmanuel Arthur +- Piyush Choudhary +- Robert Del Rey +- Tyler Wright +- Zach Horn + + +# Meeting Notes + +### Token Page Update +- Denis Lelic: Discussed the Token page and its content updates. +- Denis Lelic: Shared a Figma file with Piyush and his team for updated content and asked if it would also impact the design. +- Zach Horn: Suggested focusing on copy updates for now, with the possibility of a comprehensive redesign later. +- Denis Lelic: Agreed with Zach's approach. +- Piyush asked if this was related to implementing the token page on the existing site or a new website, to which Denis clarified it's an update of copy on the existing site. + +### Update on "Get Started" Page +- Denis discussed the "get started" page, mentioning that Arthur is already working on it +- Denis expressed a need to address the current issue with the "get started" page, which directs users to the console and the desire to present more options. +- Arthur shared that he had completed the design in Figma and was waiting for additional content to be added. +- Arthur shared his screen and displayed the "get started" page design with placeholders for buttons and links. +- Denis suggested defining the essential content for the page, including placeholders for the console, Cloudmos, and Praetor Pages. +- Denis also mentioned adding links for Praetor app and provider calculator, and asked if Arthur could deploy the Get Started page for review. +- Arthur mentioned that the deployment was done but needed to be checked. +- Denis asked Zach for his opinion on the content for the "Get Started" page. +- Zach Horn expressed that the content on the "get started" page looked good so far and suggested they could handle it themselves for at least version one. + +#### Content on "Get Started" Page +- Zach Horn proposed working on basic copy for the Akash console and suggested running it by Max for feedback. +- Zach asked about the location of YouTube videos on the page and the need to structure them effectively. +- Denis and Zach discussed the idea of producing YouTube videos to demonstrate deployments. +- Tyler emphasized the importance of creating video content and suggested using bounties to involve the community. +- Zach and Tyler agreed on the high priority of producing video content. +- Denis mentioned the timeline for the stage and said they needed to define the content and make some fine-tuning for mobile. +- Zach Horn suggested involving the Overclock team and the community to work on YouTube video content and discussed the possibility of Del Rey leading the effort. +- Zach proposed doing a bounty for video content creation and forming a small team to move quickly on this initiative. + +#### Discussions on Video Content +- Tyler mentioned Scott's video for the DoraHacks Akash Hackathon and supported Zach's idea of combining internal and community efforts for the next steps. +- Tyler suggested creating a structured story or narrative for video production. +- Zach proposed involving Dimokus to do a video(deploy a node through Cloudmos), highlighting its Web3 experience, and asking Jigar to do a video(deploy an AI model through the console) +- Denis pointed out that Jigar had done a demo during a live stream on the mainnet and suggested extracting that content. +- Denis acknowledged that the demo video was quite long and suggested trimming out the empty spaces. +- Robert Del Rey expressed his readiness to work on the video production and inquired about where the videos would be hosted. +- Denis recommended creating classic YouTube videos for Akash's channel, with links from the website. +- Tyler Wright proposed having Dimokus create videos for both the console and Cloudmos due to Scott's bandwidth limitations. +- Denis agreed with Tyler's proposal and mentioned the possibility of using AI voiceovers for all videos. +- Robert asked about the timeline for receiving the video recordings. +- Tyler confirmed he was reaching out to Dimokus and aimed to provide the videos by Friday +- Zach recommended beginning the iteration process for the Praetor video and discussing progress on Discord. + +#### Selecting template for Video Content +- Denis Lelic and Zach Horn discussed the choice of a template or model for the videos. +- Denis mentioned the possibility of asking Jigar for input and pointed out that "automatic 111" is a popular choice but was unsure if they should go with it. +- Zach expressed his preference for using "automatic 1111 with SDL" for several reasons, primarily its visual appeal, as it allows viewers to see real-time image generation, making it suitable for video content. +- Denis agreed with Zach's choice. +- Tyler raised a question about marketing and creating frontends, suggesting the possibility of setting up "automatic 111" on Akash and using it for marketing content and video production. +- Zach confirmed the feasibility of having Dimokus record the setup process, which could serve both marketing and video purposes. +- Tyler inquired about the suitability of "automatic 111" as a choice for showcasing on the marketing front, and Zach hinted at a more detailed discussion offline but confirmed that it was a good choice. + + +### Other Matters discussed +#### AI deploying tool +- Piyush Choudhary inquired about AI models in Cloudmos. +- Tyler Wright explained that Cloudmos and Console have similar capabilities but are planning to segment their products by audience. +- Cloudmos will be more focused on web applications and Web3, while Console will have a future plan for a more streamlined experience for AI/ML and non-crypto users. +- Piyush discussed building a tool for deployment, particularly for AI, with the process starting from a GitHub repo and including AI assistance for seamless deployment. +- Piyush mentioned integrating AI power to simplify Docker image creation and deployment for users. +- Denis Lelic expressed interest in Piyush's tool and suggested adding it to the system after testing and the hackathon. +- Tyler Wright agreed, saying it could be added as another deployment option for users who want to use a tool like the one Piyush is developing. + + +## Action Items +- Tyler Wright to contact Dimokus to create videos for Console and Cloudmos. +- Zack to connect with Robert Del Rey to work on video production. +- Participants to Collaborate on video production efforts, coordinating through Discord for efficient communication. +- Zach Horn to initiate a bounty program for video content creation. +- Denis to work on mobile version of Get started page with Arthur. + + +## Transcript + +# **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 is October. 19th 2023. During these working group sessions, the group talks about the current website to network, as well as the website revamp, that huge and the human HQ team. I'll put a proposal on and successfully received community pool funding for revamped website. Piyush and his team are. about something days into the process and have been giving weekly updates to folks in the community have been sharing links for people to view the website, So much appreciate piyush and the team, I get During these sessions, the group talks about figma designs for new web pages content, transferring modules, from the old website, To the new. + +Tyler Wright: And As it returns to the Akash Network website. Arm want to shout out piyush? There was a change that was made to the Akash website this week. + +Tyler Wright: Prior to yesterday, there was a Go to Console button. That button has been changed. And as a Deploy, button on the front page of the website, As you can see here, that button now takes you to cloud most, I think there's been announcements and I've been made in several channels. Talking about Cloud. Most is going to be the Preferred Deployment tool console which was a product of Overclock labs for some time. is going to not be updated. It's still an open source tool so anybody can make a adjustments can fork it are they but again because cloudmosis now under overclock and now open source cloud most which has been used by many people in the community is going to be the preferred deployment tool and so again, the website has been updated to reflect that so thank you very much to piyush. + +Tyler Wright: And his team. In addition to that I know that piyusha gives us an update on all things related to again, the revamped work that they're doing and I know Denis also who leads these calls has maybe a couple of agenda items. So maybe I'll hand it over to Piyush, to give us an updates on the work that they've been doing over the last week and then I can hand it over from there to Dennis, for any outstanding items that haven't been discussed. The Psu, want to give us an update on all the work that you've been doing. + +Piyush Choudhary: So Good Morning Everyone. So I'm Piyush. Everything networking website which has also been funded by the Community pool of Akash and we are very grateful for this opportunity and continuously giving the dates or weekly updates regarding the Current development of how it's going and how we upload this. So today I have you things that I will be giving updates on new pages, as well as there. Are you two directions or you ask from the leaders about the content and needs to be updated on the official pages of this website, + +Piyush Choudhary: So till now we have worked on the home page in the last week, I was not presentation's, but I did pasted the dates in the discord group. So today till then be completed on to the home page, then the token Page block page, and we were also working on the ecosystem page. So today's new updates are the ecosystem page has been completed under person, and we have also imported the schools into this website. So as you can see, if I go to deployed on Akash, We got all the projects that are currently illustrated on the ecosyst Akash Dot network with the designing directions from Dennis. We also have a search so if I search let's say search at cluster. + +Piyush Choudhary: And gives us that let's talk and it takes us to the website of that last time. So we also have the search icon as well as filtering functionalities as well. And also, the exciting thing about this is this all is coming from the mouth down so it will be easier to push the To the applied, the new projects, the content writer bloggers or any project who wants to add their project to this page. We'll just have to write a markdown file and push it to the repository that we will soon. Make it public and open source. + +00:05:00 + +Piyush Choudhary: We also have got the filtering functionalities on the right hand side. So if we click on the projects that are tagged as gaming, in their magnum file will appear like this, filtering functionality. So this is the date about the ecosystem page and we have the cost tools where we have listed the cloud most and better and we will list more tools. As the direction of the leaders of this group. + +Piyush Choudhary: And secondly, there is a new updates on the development page, so this is how the development page is looking on. The left hand side, we have the mount on files links. And in the middle, we have the content of the Markdown file. That is basically coming from the Markdown file, and anyone can update it. and on the right hand side is basically the headings or you can see the links of this content. See if I play content, it is also down to the content. + +Piyush Choudhary: Section of this file, we click on Comment, subheading, It's causes down to the dummy cell. So it's kind of is a tool to school and we also have got the change buttons etc, as the lanes and all. And also, we have also implemented the custom all down parts of functionality. So, if you go across the current website, that live on official domain or cost of network, will not have a functionality of Explain something like this. + +Piyush Choudhary: From the markdown but we have implemented, the custom code that can do that. So we just something mention a little bit of additional things, while writing the markdown file, and it will be displayed like this as you can see. So this is what right now, there are only two magnolia that have been added, and the content that you are seeing on this case, also a dummy content or it's not a fine nice content. We will update the content for all these files. Once we will Or The finalized content on this Sigma file by Denis and Jam. And then we will continue working on the community page which is also kind of similar to the development page. We mostly have resist copy paste, the code and update the content as for the direction of the signal file. So, Yeah, this is what the dates are. So + +Piyush Choudhary: in short, we have done the home page get started page and ecosystem token page, blog, page and development page. And once the contents are being finalized and we will just work on the community page and we will have this up. I think, within the next 10 days and for the docs we have to figure out how to handle this because we haven't received the source called yet, and we are not sure if we should use the existing source code made by the other team that has been handled previously in the past months. So once we receive the source code, we will look into ways on how to implement the docs. if we find it visible to implement the existing source code that has already been done by the team, we will implement that, it's not. Then we will create a custom + +Piyush Choudhary: We will create lock switch from scratch again and this might need some additional efforts. So We will plan things for this dog's page accordingly for now, I think everything is doing very great and there are no major issues that we are the same. And I think within next, 10 to 14 days, we will have a website ready to be life on the official domain. Thank you. + +Tyler Wright: Thank you piyush. in terms of the docs, I know that's on me. One of the things I'm having trouble is one of our team members, that would be able to get you access to that specific repo has been out, so that will be back today and then I should be able to get you access that repo again. I shared the repo in the chapter. I believe it's private and… + +Piyush Choudhary: We get. + +Tyler Wright: for you, so you can see it. I know why it's private because In the Akash network, organizations will be public. But again, I will get that to you as soon as I possibly can, probably apologize for that. Real quick on the community page and this might involve you having to get access to the community repo. Are you going to be able to drop in the + +Tyler Wright: kind of like github action so that when notes get updated, it's updating the website and kind of real time because I think what's been happening in the past and this no notes will get updated but the page hasn't been built in a long time so the notes are very much out of date,… + +00:10:00 + +Piyush Choudhary: so basically,… + +Tyler Wright: so just + +Piyush Choudhary: Yeah, so basically all the content stereos seeing on the screen is coming from the markdown file. So, whatever the date is being made to the markdown 5 will be a bit here on I don't think whatever we are. Structuring is very efficient, and transparent whatever the content even on the homepage. These titles that you are saying, the get started titles, etc are coming from the markdown file. So, whatever is updated on the knockdown file that's created on content speed. So, everything will be so transparent and easier to use even called Jack who You can just update few contexts in the files and it will be updated on the content website, the backend, or you can say that + +Piyush Choudhary: The complex part of tech is being well maintained, so the code in a separate folders and for the content, the content folder is Update which don't have any technicals, or you can see the codes, you just have the content that needs to be updated any of the pages or the content files. + +Tyler Wright: Does anyone have any questions for piyush again? If anybody is watching this recording later, please feel free to drop any comments or feedback in the working group of cosh website, discord channel. But Denis, do you have any comments concerns? at this time that you want to address, + +Denis Lelic: No, not. At this time. I was just looking through the update. Yeah, I do like this. instant update with the markdown file and so we're kind of up to date on the website and I'm just going to share. So if anyone is going to watch the recording, Some action items from Piyush. He sent us today, + +Denis Lelic: I've posted them here In the Chat section. Yeah, as we talked previously, I'm gonna make sure I do my part. I'm gonna have a look at the Graphics stuff like that and I'll update the figma file. + +Denis Lelic: Yeah, but I like the progress you're making and there's still some UI tweaks. I would recommend later on but far so good. + +Piyush Choudhary: Yeah, we are open to the conditions and we will a great course as for your recommendations about + +Denis Lelic: Cool. + +Denis Lelic: one thing we discussed in the previous session was, and we were just questioning if there's a possibility to add a calendar and for example, in the development page, we would add extra page For overview,… + +Tyler Wright: + +Denis Lelic: where users could see What kind of meanings are happening today and in the upcoming to days, the thing that it's possible to somehow embed + +Piyush Choudhary: Something like this, right? + +Denis Lelic: Actually a proper calendar. if you Google Google calendar, + +Piyush Choudhary: Yeah. Okay. You mean Google calendars, something. So you want to integrate the Google go into, right? + +Denis Lelic: Yeah, there's a calendar. I think Tyler is managing it where all of the meetings and everything that's happening, are in there. And we were just wondering if it's possible to Embed, that calendar here in one of these pages. + +Piyush Choudhary: Yes, it's possible. You can just share me what calendar you are using and this is embed that this + +Denis Lelic: I googled and researched a little bit, and I found this one styled calendar where you can basically drop your I've added Link here in the Chat section,… + +Piyush Choudhary: When you? + +Denis Lelic: you can actually design your own calendar and I think you just have to connect it with Google Calendar and it becomes kind of like a customizable custom thing. but if it's too much effort, we could just go for the default thing from + +Piyush Choudhary: Yeah, yeah, no worries. I will just research this calendar. it's going to be very straightforward, so I will see if we can integrated + +00:15:00 + +Denis Lelic: Cool, Cool. + +Piyush Choudhary: Right now, what calendar are you guys using for the official ones? Okay. + +Tyler Wright: I just sent you a link H to your email that my connects you to the Google calendar. And then again, obviously there's customizing options and betting options there. So if you have questions about accessing those let me know but it's called the Akash Community Group calendar. + +Piyush Choudhary: So yeah, we will need to get that calendar into this file, just Give me a little directions on how you want it to be done. Should I create a calendar headline? Product Strategy and for example, There are Want to see five lines. So, I can just create another calendar pipeline and then just under here. + +Tyler Wright: Yes. + +Denis Lelic: I think Zach's idea was to add an overview page. It would be like the first one… + +Piyush Choudhary: Really. + +Denis Lelic: where we would. Talk in general about the meetings and projects, and we would just add the calendar right away there. So if anyone is interested,… + +Piyush Choudhary: Also. Just so at the top,… + +Denis Lelic: they're gonna see it right away. They don't have to dig deeper + +Piyush Choudhary: we could have only real page and in that we could just start, content to knock down price, including calendar. + +Denis Lelic: Yep. + +Piyush Choudhary: Yeah, We'll update that it's not a big deal. So Yes. And also for the token page, it's possible to implement the real-time data in here. So I just want the API endpoints which the sources. So should I use COIN vehicle API or something? + +Denis Lelic: Yeah, previously we had coin geckos so either that or the coin market cap. But we would,… + +Piyush Choudhary: Okay. + +Denis Lelic: I don't know. I would just suggest we stick to the same one. So everyone is understanding + +Tyler Wright: Yeah, this is something that I've been asking this internally to a couple of people that fin apps department and haven't gotten the firm answer back yet which is why I haven't give you an answer. I think, as Dennis has mentioned that we can leave it like it is for right now. Then as soon as I can answer, a firm answer and what we want to do well what we want to preferred source to be, then I'll make sure you have everything you need API keys, but this is something I've actively been asking and have not done again a confirmation. Yeah. + +Piyush Choudhary: And also i forward to mentioned we also need the FAQ or data. I will just mention it in the + +Denis Lelic: I think there were just updated there in the token page the FAQs, but there are a bunch of them, still in the making, so one when they're ready, I'll just insert them in the figma file. + +Piyush Choudhary: Yeah, sure. + +Denis Lelic: Let you know. + +Piyush Choudhary: So yeah, I think things are progressing very well, if we get the plates and the contents that we are asking sooner, we will have the radical website within 10 to 14 days, to live, on the official on it. + +Tyler Wright: Excellent. All… + +Denis Lelic: Sounds good. + +Tyler Wright: I'll make some time for you to give an update during steering committee… + +Piyush Choudhary: And I, + +Tyler Wright: If you're around it might be too late for you. + +Piyush Choudhary: So when is the steering committing company? + +Tyler Wright: it's happening Thursday which probably your next Friday because it's next Thursday at I think 1 pm Pacific. + +Piyush Choudhary: Yeah, So yeah, I'll be there this time I think I will be available on just take with nothing is important concept. + +Tyler Wright: Okay. + +Piyush Choudhary: and also what is the general feedback about the user experience of this website and how this is progressing of both of you and also I was + +Piyush Choudhary: I think. + +Denis Lelic: for me, It's fast. I know that's something Greg was always interested in keeping it fast. + +Denis Lelic: With this functionality of MD's just updating and making it easy to use for any one. Basically, they don't have to be technical. Maybe we just add a small paragraph somewhere. How to make that update on the website and… + +Piyush Choudhary: Yes. + +Denis Lelic: it's going to be super easy for everyone. + +00:20:00 + +Tyler Wright: Yeah, I mean the feedback that I've got from other folks is the same thing. It's fast, it looks clean. So again, when you share this updates, I try to share them to appropriate people to internal team. So there's much appreciate all the efforts and all the work from you and your team. + +Piyush Choudhary: And also I have a questions as we are focusing initially on the cloud nose. So, we have a deploy page as we all know, Should we just keep the cloud most here and… + +Tyler Wright: Yes. + +Piyush Choudhary: remove the GARCH console, which should be keyboard or… + +Tyler Wright: Yes. I think we should. + +Piyush Choudhary: sponsor lenses? + +Tyler Wright: Remove console. + +Piyush Choudhary: Of course. + +Denis Lelic: yeah, then we have Where we had a dedicated page for one product. + +Piyush Choudhary: You, I think. + +Denis Lelic: That we might. Bring back. + +Tyler Wright: Go Back from the dead,… + +Piyush Choudhary: Yeah. Yeah. + +Denis Lelic: No. Yeah,… + +Tyler Wright: ? + +Denis Lelic: I know I see you're looking at it. So we would just kick out this one and we would have one photo and a couple of points there. about the product and that's it. I know we just updated it, but then we heard the news. + +Denis Lelic: And now we're back to the one page. + +Tyler Wright: Gee. + +Piyush Choudhary: Yes, So I think this is, I think already ready. So we just implement this and remove this current design from here. Also, + +Denis Lelic: cool. if you want to talk to us or me, earlier next week, if you have anything to discuss unavailable, + +Denis Lelic: Even in your let's… + +Piyush Choudhary: He? + +Denis Lelic: I don't know. 12 am for you or 11, 10. I'm not really sure what are time differences but Yeah, I'm here. If you need anything and Happy to help. + +Piyush Choudhary: Yeah I think we should schedule a private mate before next Thursday to discuss on how we are progressing. And also the design recommendations you might have on the current design so we can align Ourselfs in the directions or the passionate + +Denis Lelic: Sounds good. + +Piyush Choudhary: And also this content is also coming from the markdown file. What we just have to do is we just have to update the image of Let's say the author, the username that we want to display and the content we just want to display in the meltdown file and it just display or adds the new card here. So any number of cards can be added here. We just have to update a three. Three things, the image, the name, and the content in the markdown file. + +Denis Lelic: Yeah, that's cool. That's cool. + +Piyush Choudhary: And also I forgot to mention we also implemented the archive feature. So what happens is if we don't want this log will be deleted. And also we don't want this block to be land anywhere else In other pages. We just can say archive through in the markdown file and it will get shown to the All Type section and this archives sections blocks Anywhere else will not be ranked anyway else on the website and we'll just stay in their private sections and we'll only be accessed through Archives section. + +Denis Lelic: Yeah, that's cool. + +Piyush Choudhary: So that's all I think. + +Denis Lelic: I think there's plenty of content there, that could be like, Someone should have a look at it, but you know what's relevant or not, but it's good to have that functionality. Thanks. + +Piyush Choudhary: If in some notifications, if we want to relate the blogs we can delete, but in some cases, we don't want them to rank. And also, we don't want them to delete. We can just archive those blocks and in future. If someone wants to access that blocks can just go to the archives section and we'll be able to access all kind of + +Denis Lelic: Hi, you're having anything else. + +Tyler Wright: No, this has been very good, very informative, much appreciated. + +Denis Lelic: Okay So I guess we know We have a bunch of action items. for the next week. and tomorrow, basically and it's time to get back to work. I've been working on a couple of different things, but + +00:25:00 + +Denis Lelic: Thank you for being patient. And I know I haven't updated the figma file. For the last couple of weeks, but yeah, I'll get together with Zach and make sure we have the latest content. There in Figma and + +Denis Lelic: Yeah, I'll tag you in figma when any content is ready and You guys can implement it. + +Piyush Choudhary: So yeah I think by next week we will have mostly all the pieces ready. + +Denis Lelic: Cool. + +Piyush Choudhary: We will be waiting for the content so we can also take the content. So I think the only piece that will be remaining by next week is docs. So we have to look how we should plan for the dogs when we see the source code and for the pages, I think it will be mostly completed as far as and for our current schedule, + +Denis Lelic: Sounds good. + +Piyush Choudhary: so, Yeah, that's all. So. Can I stop using my screen? + +Denis Lelic: Thank you for your time, thanks for the updates. + +Tyler Wright: Yes. + +Denis Lelic: Thank you, Ty as well for the intro and retrospective, I'm not sure if it's called that way, but anyway, + +Denis Lelic: we'll talk in discord for Otherwise. In next week, Thursday. + +Tyler Wright: Yeah. Piyush Pierce just a reminder,… + +Piyush Choudhary: it + +Tyler Wright: much appreciate I know that you are working a number of things. that I'm thinking about if it can come to steering committee because you can not only talk about the website revamp, but you could talk about the potential work that you are going to be doing alongside Cloud most. So that would be great to have Arthur's here. + +Piyush Choudhary: Yeah, So I will also update submit the proposal by tomorrow as for A guidance. I got from an index of + +Tyler Wright: Okay, Hey, Arthur. We were just actually about to wrap up, we went through the agenda. We added action items inside of the discord, working group Akash, website and again, the notes will be updated very soon. I believe that there were specific feedback. + +Tyler Wright: For you. Piyush, right? But that Arthur, had to update some stuff. + +Tyler Wright: Or am I just reading That Arthur have to update some links. + +Piyush Choudhary: So, we just updated the Home Page button as you can see in the Hero section. So, in Video Section, Right, previously was going to console and right now it's tipped right now that is taking the users to the cloud nose. And it was officially announced by the pastrami yesterday that from Non-warts are the whole airport. So they put into developing and enhancing the cloud, most employment, and the development of concert will be stopped development and support of console board will be stopped completely from non-words, but it will be applicable to be used by those numbers, but the support and development of the stock from now onwards, + +Tyler Wright: Absolutely. are you saying that? Do you think? And this is a question for everybody here? Do we need to update? If I can share my screen. Do we need to actively update this page right now that points to both? Or do we want to leave it? Because Piyush is gonna have the revamp website and that's week and a half two weeks. + +Piyush Choudhary: I think we can keep it as it is right now because it's not a big deal and we will soon have a new website ready. So I think it's not a big deal to keep it like this is not + +Tyler Wright: I would agree with that. Denis, you have any issue with that? + +Denis Lelic: No, no sounds good to me. + +Tyler Wright: Okay, Is there anything that you want to talk about? While we're all alive. I know that you do a good job. Arthur of chatting and discourse, anything that you want to talk about live while we're here. + +Emmanuel Arthur: no, really, no really + +Piyush Choudhary: and I also Arthur… + +Tyler Wright: Okay, excellent. + +Piyush Choudhary: if you have any feedbacks for the new website and shared In the group artists thought anywhere else. + +00:30:00 + +Emmanuel Arthur: + +Emmanuel Arthur: + +Tyler Wright: All right, again there's nothing else and we'll meet up next week and we'll continue to work together between meetings. I know there's gonna be some sessions that are going to be set up for folks, to talk about design. Zach will be back in office early next week and again, I know it's a priority for me to get the docs work handed over to Piyush and this team as soon as possible. So I'll be working on that today. + +Denis Lelic: Thank you. + +Tyler Wright: Thank… + +Piyush Choudhary: Thank you. + +Denis Lelic: Thank you guys. + +Tyler Wright: Everybody has a great day. We'll talk online. + +Denis Lelic: Thank you. + +Piyush Choudhary: Or by take care. + +Meeting ended after 00:31:02 👋 + 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/013-2023-10-19.md b/wg-akash-website/meetings/013-2023-10-19.md new file mode 100644 index 00000000..415db0ce --- /dev/null +++ b/wg-akash-website/meetings/013-2023-10-19.md @@ -0,0 +1,380 @@ +# Akash Network - Akash Website Working Group (WG) - Meeting #13 +## Agenda +- Website Revamp Progress +- Calendar Integration Discussion +## Meeting Details +- Date: Thursday, October 19, 2023 +- Time: 6:00 AM PT (Pacific Time) +- [Recording](https://s7n2e2tfghnhjtwc3wse3vnami7vmza7npbr65i4orqb3mfmrpba.arweave.net/l9uiamUx2nTOwt2kTdWgYj9WZB9rwx91HHRgHbCsi8I) +- [Transcript](#Transcript) +## Participants +- Denis Lelic +- Emmanuel Arthur +- Piyush Choudhary +- Tyler Wright +## Meeting Notes +- Tyler noted that a significant change was made to the Akash website this week: the "Go to Console" button was replaced with a "Deploy" button, leading to Cloudmos. +- Tyler explained that Cloudmos would be the preferred deployment tool going forward, and Console would no longer receive updates. +Tyler expressed gratitude to Piyush and his team for updating the website to reflect this change. +### Website Revamp Progress Updates +#### Piyush Updates: +- Mentioned the completion of work on the home page, token page, blog page, and ongoing work on the ecosystem page. +- Explained the features of the ecosystem page, including the ability to filter and search projects, and the use of markdown files for easy project additions. +- Discussed the Akash tools section and plans to add more tools based on leadership guidance. +- Showed the development page with markdown file links, content, and custom markdown functionality. +- Mentioned plans for the community page, similar to the development page. +- Shared the timeline for completing all the pages within the next 10 days. +- He mentioned the implementation of an archive feature, allowing blocks to be archived rather than deleted, making it accessible in the archives section. +- Discussed challenges related to the docs page due to source code issues, indicating they would explore implementing existing source code or creating a custom doc page. +- Piyush inquired about implementing real-time data on the token page. +#### Tyler Wright +- Mentioned challenges with providing access to the docs repo due to a team member being unavailable. +- Tyler stated that he would share the repo in the chat and ensure Piyush has access to it as soon as possible. +- Tyler inquired about real-time updates for the community page, potentially using GitHub actions to ensure the page reflects updated notes promptly. +- Piyush emphasized the separation of technical code and content, making it easier for content updates. +- Tyler explained that he had been seeking internal input on the preferred source for real-time data and API endpoints. +- He acknowledged not having received a firm answer yet and indicated that they could continue with the current setup until a decision is made. +#### Denis Lelic +- Denis mentioned that he appreciates the instant updates with markdown files, ensuring the website is up to date. +- Denis mentioned that they previously used Coingecko or CoinMarketCap APIs for real-time data, suggesting that they stick to the same one for consistency. +- Shared action items from Piyush in the chat. +- Mentioned plans to look into graphics and update the Figma file.. +- Mentioned the need for some UI tweaks later. +- Denis indicated that some FAQs had been updated on the token page, with more in progress, and he would insert them into the figma file when they are ready. +### Calendar Integration Discussion +- Denis brought up the idea discussed in the previous session about adding a calendar. +- He suggested creating a separate page where users could easily see upcoming meetings. +- Denis mentioned that they were considering embedding a proper calendar, possibly Google Calendar. +- Piyush confirmed that it is possible to embed a calendar and asked Denis to share details about the specific calendar they were using. +- Denis expressed willingness to use a default calendar if it's easier, but Piyush assured that the integration would be straightforward. +- Tyler Mentioned customization and embedding options available, and offered to help if needed. +### Other matters Discussed +- Tyler expressed his readiness to make time for Piyush to provide an update during the steering committee meeting and informed Piyush of the meeting's date and time. +- Piyush confirmed his availability for the steering committee meeting and that he would be around for it. +- Piyush raised a question about whether to keep Cloudmos on the deploy page and remove the Akash Console. +- Tyler and Denis agreed to remove the Akash Console and maintain Cloudmos as the primary option. +## Action items +- Piyush to research and integrate a calendar onto the website for tracking meetings and events. +- Tyler will provide Piyush access to the specific repository for handling the docs page. +- Denis to add FAQs to the website and update the figma file when ready. +- Denis will consider the possibility of implementing a one-page product overview. +- Piyush and Denis to schedule a private meeting to discuss progress, design recommendations, and alignment of directions. +- Piyush to prepare for the upcoming steering committee meeting + + +# **Transcript** + +_This editable transcript was computer generated and might contain errors. People can also change the text after it was created._ + +Tyler Wright: All right, welcome everybody. To this week's edition of the working group for the Akash website. It is October. 19th 2023. During these working group sessions, the group talks about the current website to network, as well as the website revamp, that huge and the human HQ team. I'll put a proposal on and successfully received community pool funding for revamped website. Piyush and his team are. about something days into the process and have been giving weekly updates to folks in the community have been sharing links for people to view the website, So much appreciate piyush and the team, I get During these sessions, the group talks about figma designs for new web pages content, transferring modules, from the old website, To the new. + +Tyler Wright: And As it returns to the Akash Network website. Arm want to shout out piyush? There was a change that was made to the Akash website this week. + +Tyler Wright: Prior to yesterday, there was a Go to Console button. That button has been changed. And as a Deploy, button on the front page of the website, As you can see here, that button now takes you to cloud most, I think there's been announcements and I've been made in several channels. Talking about Cloud. Most is going to be the Preferred Deployment tool console which was a product of Overclock labs for some time. is going to not be updated. It's still an open source tool so anybody can make a adjustments can fork it are they but again because cloudmosis now under overclock and now open source cloud most which has been used by many people in the community is going to be the preferred deployment tool and so again, the website has been updated to reflect that so thank you very much to piyush. + +Tyler Wright: And his team. In addition to that I know that piyusha gives us an update on all things related to again, the revamped work that they're doing and I know Denis also who leads these calls has maybe a couple of agenda items. So maybe I'll hand it over to Piyush, to give us an updates on the work that they've been doing over the last week and then I can hand it over from there to Dennis, for any outstanding items that haven't been discussed. The Psu, want to give us an update on all the work that you've been doing. + +Piyush Choudhary: So Good Morning Everyone. So I'm Piyush. Everything networking website which has also been funded by the Community pool of Akash and we are very grateful for this opportunity and continuously giving the dates or weekly updates regarding the Current development of how it's going and how we upload this. So today I have you things that I will be giving updates on new pages, as well as there. Are you two directions or you ask from the leaders about the content and needs to be updated on the official pages of this website, + +Piyush Choudhary: So till now we have worked on the home page in the last week, I was not presentation's, but I did pasted the dates in the discord group. So today till then be completed on to the home page, then the token Page block page, and we were also working on the ecosystem page. So today's new updates are the ecosystem page has been completed under person, and we have also imported the schools into this website. So as you can see, if I go to deployed on Akash, We got all the projects that are currently illustrated on the ecosyst Akash Dot network with the designing directions from Dennis. We also have a search so if I search let's say search at cluster. + +Piyush Choudhary: And gives us that let's talk and it takes us to the website of that last time. So we also have the search icon as well as filtering functionalities as well. And also, the exciting thing about this is this all is coming from the mouth down so it will be easier to push the To the applied, the new projects, the content writer bloggers or any project who wants to add their project to this page. We'll just have to write a markdown file and push it to the repository that we will soon. Make it public and open source. + +00:05:00 + +Piyush Choudhary: We also have got the filtering functionalities on the right hand side. So if we click on the projects that are tagged as gaming, in their magnum file will appear like this, filtering functionality. So this is the date about the ecosystem page and we have the cost tools where we have listed the cloud most and better and we will list more tools. As the direction of the leaders of this group. + +Piyush Choudhary: And secondly, there is a new updates on the development page, so this is how the development page is looking on. The left hand side, we have the mount on files links. And in the middle, we have the content of the Markdown file. That is basically coming from the Markdown file, and anyone can update it. and on the right hand side is basically the headings or you can see the links of this content. See if I play content, it is also down to the content. + +Piyush Choudhary: Section of this file, we click on Comment, subheading, It's causes down to the dummy cell. So it's kind of is a tool to school and we also have got the change buttons etc, as the lanes and all. And also, we have also implemented the custom all down parts of functionality. So, if you go across the current website, that live on official domain or cost of network, will not have a functionality of Explain something like this. + +Piyush Choudhary: From the markdown but we have implemented, the custom code that can do that. So we just something mention a little bit of additional things, while writing the markdown file, and it will be displayed like this as you can see. So this is what right now, there are only two magnolia that have been added, and the content that you are seeing on this case, also a dummy content or it's not a fine nice content. We will update the content for all these files. Once we will Or The finalized content on this Sigma file by Denis and Jam. And then we will continue working on the community page which is also kind of similar to the development page. We mostly have resist copy paste, the code and update the content as for the direction of the signal file. So, Yeah, this is what the dates are. So + +Piyush Choudhary: in short, we have done the home page get started page and ecosystem token page, blog, page and development page. And once the contents are being finalized and we will just work on the community page and we will have this up. I think, within the next 10 days and for the docs we have to figure out how to handle this because we haven't received the source called yet, and we are not sure if we should use the existing source code made by the other team that has been handled previously in the past months. So once we receive the source code, we will look into ways on how to implement the docs. if we find it visible to implement the existing source code that has already been done by the team, we will implement that, it's not. Then we will create a custom + +Piyush Choudhary: We will create lock switch from scratch again and this might need some additional efforts. So We will plan things for this dog's page accordingly for now, I think everything is doing very great and there are no major issues that we are the same. And I think within next, 10 to 14 days, we will have a website ready to be life on the official domain. Thank you. + +Tyler Wright: Thank you piyush. in terms of the docs, I know that's on me. One of the things I'm having trouble is one of our team members, that would be able to get you access to that specific repo has been out, so that will be back today and then I should be able to get you access that repo again. I shared the repo in the chapter. I believe it's private and… + +Piyush Choudhary: We get. + +Tyler Wright: for you, so you can see it. I know why it's private because In the Akash network, organizations will be public. But again, I will get that to you as soon as I possibly can, probably apologize for that. Real quick on the community page and this might involve you having to get access to the community repo. Are you going to be able to drop in the + +Tyler Wright: kind of like github action so that when notes get updated, it's updating the website and kind of real time because I think what's been happening in the past and this no notes will get updated but the page hasn't been built in a long time so the notes are very much out of date,… + +00:10:00 + +Piyush Choudhary: so basically,… + +Tyler Wright: so just + +Piyush Choudhary: Yeah, so basically all the content stereos seeing on the screen is coming from the markdown file. So, whatever the date is being made to the markdown 5 will be a bit here on I don't think whatever we are. Structuring is very efficient, and transparent whatever the content even on the homepage. These titles that you are saying, the get started titles, etc are coming from the markdown file. So, whatever is updated on the knockdown file that's created on content speed. So, everything will be so transparent and easier to use even called Jack who You can just update few contexts in the files and it will be updated on the content website, the backend, or you can say that + +Piyush Choudhary: The complex part of tech is being well maintained, so the code in a separate folders and for the content, the content folder is Update which don't have any technicals, or you can see the codes, you just have the content that needs to be updated any of the pages or the content files. + +Tyler Wright: Does anyone have any questions for piyush again? If anybody is watching this recording later, please feel free to drop any comments or feedback in the working group of cosh website, discord channel. But Denis, do you have any comments concerns? at this time that you want to address, + +Denis Lelic: No, not. At this time. I was just looking through the update. Yeah, I do like this. instant update with the markdown file and so we're kind of up to date on the website and I'm just going to share. So if anyone is going to watch the recording, Some action items from Piyush. He sent us today, + +Denis Lelic: I've posted them here In the Chat section. Yeah, as we talked previously, I'm gonna make sure I do my part. I'm gonna have a look at the Graphics stuff like that and I'll update the figma file. + +Denis Lelic: Yeah, but I like the progress you're making and there's still some UI tweaks. I would recommend later on but far so good. + +Piyush Choudhary: Yeah, we are open to the conditions and we will a great course as for your recommendations about + +Denis Lelic: Cool. + +Denis Lelic: one thing we discussed in the previous session was, and we were just questioning if there's a possibility to add a calendar and for example, in the development page, we would add extra page For overview,… + +Tyler Wright: + +Denis Lelic: where users could see What kind of meanings are happening today and in the upcoming to days, the thing that it's possible to somehow embed + +Piyush Choudhary: Something like this, right? + +Denis Lelic: Actually a proper calendar. if you Google Google calendar, + +Piyush Choudhary: Yeah. Okay. You mean Google calendars, something. So you want to integrate the Google go into, right? + +Denis Lelic: Yeah, there's a calendar. I think Tyler is managing it where all of the meetings and everything that's happening, are in there. And we were just wondering if it's possible to Embed, that calendar here in one of these pages. + +Piyush Choudhary: Yes, it's possible. You can just share me what calendar you are using and this is embed that this + +Denis Lelic: I googled and researched a little bit, and I found this one styled calendar where you can basically drop your I've added Link here in the Chat section,… + +Piyush Choudhary: When you? + +Denis Lelic: you can actually design your own calendar and I think you just have to connect it with Google Calendar and it becomes kind of like a customizable custom thing. but if it's too much effort, we could just go for the default thing from + +Piyush Choudhary: Yeah, yeah, no worries. I will just research this calendar. it's going to be very straightforward, so I will see if we can integrated + +00:15:00 + +Denis Lelic: Cool, Cool. + +Piyush Choudhary: Right now, what calendar are you guys using for the official ones? Okay. + +Tyler Wright: I just sent you a link H to your email that my connects you to the Google calendar. And then again, obviously there's customizing options and betting options there. So if you have questions about accessing those let me know but it's called the Akash Community Group calendar. + +Piyush Choudhary: So yeah, we will need to get that calendar into this file, just Give me a little directions on how you want it to be done. Should I create a calendar headline? Product Strategy and for example, There are Want to see five lines. So, I can just create another calendar pipeline and then just under here. + +Tyler Wright: Yes. + +Denis Lelic: I think Zach's idea was to add an overview page. It would be like the first one… + +Piyush Choudhary: Really. + +Denis Lelic: where we would. Talk in general about the meetings and projects, and we would just add the calendar right away there. So if anyone is interested,… + +Piyush Choudhary: Also. Just so at the top,… + +Denis Lelic: they're gonna see it right away. They don't have to dig deeper + +Piyush Choudhary: we could have only real page and in that we could just start, content to knock down price, including calendar. + +Denis Lelic: Yep. + +Piyush Choudhary: Yeah, We'll update that it's not a big deal. So Yes. And also for the token page, it's possible to implement the real-time data in here. So I just want the API endpoints which the sources. So should I use COIN vehicle API or something? + +Denis Lelic: Yeah, previously we had coin geckos so either that or the coin market cap. But we would,… + +Piyush Choudhary: Okay. + +Denis Lelic: I don't know. I would just suggest we stick to the same one. So everyone is understanding + +Tyler Wright: Yeah, this is something that I've been asking this internally to a couple of people that fin apps department and haven't gotten the firm answer back yet which is why I haven't give you an answer. I think, as Dennis has mentioned that we can leave it like it is for right now. Then as soon as I can answer, a firm answer and what we want to do well what we want to preferred source to be, then I'll make sure you have everything you need API keys, but this is something I've actively been asking and have not done again a confirmation. Yeah. + +Piyush Choudhary: And also i forward to mentioned we also need the FAQ or data. I will just mention it in the + +Denis Lelic: I think there were just updated there in the token page the FAQs, but there are a bunch of them, still in the making, so one when they're ready, I'll just insert them in the figma file. + +Piyush Choudhary: Yeah, sure. + +Denis Lelic: Let you know. + +Piyush Choudhary: So yeah, I think things are progressing very well, if we get the plates and the contents that we are asking sooner, we will have the radical website within 10 to 14 days, to live, on the official on it. + +Tyler Wright: Excellent. All… + +Denis Lelic: Sounds good. + +Tyler Wright: I'll make some time for you to give an update during steering committee… + +Piyush Choudhary: And I, + +Tyler Wright: If you're around it might be too late for you. + +Piyush Choudhary: So when is the steering committing company? + +Tyler Wright: it's happening Thursday which probably your next Friday because it's next Thursday at I think 1 pm Pacific. + +Piyush Choudhary: Yeah, So yeah, I'll be there this time I think I will be available on just take with nothing is important concept. + +Tyler Wright: Okay. + +Piyush Choudhary: and also what is the general feedback about the user experience of this website and how this is progressing of both of you and also I was + +Piyush Choudhary: I think. + +Denis Lelic: for me, It's fast. I know that's something Greg was always interested in keeping it fast. + +Denis Lelic: With this functionality of MD's just updating and making it easy to use for any one. Basically, they don't have to be technical. Maybe we just add a small paragraph somewhere. How to make that update on the website and… + +Piyush Choudhary: Yes. + +Denis Lelic: it's going to be super easy for everyone. + +00:20:00 + +Tyler Wright: Yeah, I mean the feedback that I've got from other folks is the same thing. It's fast, it looks clean. So again, when you share this updates, I try to share them to appropriate people to internal team. So there's much appreciate all the efforts and all the work from you and your team. + +Piyush Choudhary: And also I have a questions as we are focusing initially on the cloud nose. So, we have a deploy page as we all know, Should we just keep the cloud most here and… + +Tyler Wright: Yes. + +Piyush Choudhary: remove the GARCH console, which should be keyboard or… + +Tyler Wright: Yes. I think we should. + +Piyush Choudhary: sponsor lenses? + +Tyler Wright: Remove console. + +Piyush Choudhary: Of course. + +Denis Lelic: yeah, then we have Where we had a dedicated page for one product. + +Piyush Choudhary: You, I think. + +Denis Lelic: That we might. Bring back. + +Tyler Wright: Go Back from the dead,… + +Piyush Choudhary: Yeah. Yeah. + +Denis Lelic: No. Yeah,… + +Tyler Wright: ? + +Denis Lelic: I know I see you're looking at it. So we would just kick out this one and we would have one photo and a couple of points there. about the product and that's it. I know we just updated it, but then we heard the news. + +Denis Lelic: And now we're back to the one page. + +Tyler Wright: Gee. + +Piyush Choudhary: Yes, So I think this is, I think already ready. So we just implement this and remove this current design from here. Also, + +Denis Lelic: cool. if you want to talk to us or me, earlier next week, if you have anything to discuss unavailable, + +Denis Lelic: Even in your let's… + +Piyush Choudhary: He? + +Denis Lelic: I don't know. 12 am for you or 11, 10. I'm not really sure what are time differences but Yeah, I'm here. If you need anything and Happy to help. + +Piyush Choudhary: Yeah I think we should schedule a private mate before next Thursday to discuss on how we are progressing. And also the design recommendations you might have on the current design so we can align Ourselfs in the directions or the passionate + +Denis Lelic: Sounds good. + +Piyush Choudhary: And also this content is also coming from the markdown file. What we just have to do is we just have to update the image of Let's say the author, the username that we want to display and the content we just want to display in the meltdown file and it just display or adds the new card here. So any number of cards can be added here. We just have to update a three. Three things, the image, the name, and the content in the markdown file. + +Denis Lelic: Yeah, that's cool. That's cool. + +Piyush Choudhary: And also I forgot to mention we also implemented the archive feature. So what happens is if we don't want this log will be deleted. And also we don't want this block to be land anywhere else In other pages. We just can say archive through in the markdown file and it will get shown to the All Type section and this archives sections blocks Anywhere else will not be ranked anyway else on the website and we'll just stay in their private sections and we'll only be accessed through Archives section. + +Denis Lelic: Yeah, that's cool. + +Piyush Choudhary: So that's all I think. + +Denis Lelic: I think there's plenty of content there, that could be like, Someone should have a look at it, but you know what's relevant or not, but it's good to have that functionality. Thanks. + +Piyush Choudhary: If in some notifications, if we want to relate the blogs we can delete, but in some cases, we don't want them to rank. And also, we don't want them to delete. We can just archive those blocks and in future. If someone wants to access that blocks can just go to the archives section and we'll be able to access all kind of + +Denis Lelic: Hi, you're having anything else. + +Tyler Wright: No, this has been very good, very informative, much appreciated. + +Denis Lelic: Okay So I guess we know We have a bunch of action items. for the next week. and tomorrow, basically and it's time to get back to work. I've been working on a couple of different things, but + +00:25:00 + +Denis Lelic: Thank you for being patient. And I know I haven't updated the figma file. For the last couple of weeks, but yeah, I'll get together with Zach and make sure we have the latest content. There in Figma and + +Denis Lelic: Yeah, I'll tag you in figma when any content is ready and You guys can implement it. + +Piyush Choudhary: So yeah I think by next week we will have mostly all the pieces ready. + +Denis Lelic: Cool. + +Piyush Choudhary: We will be waiting for the content so we can also take the content. So I think the only piece that will be remaining by next week is docs. So we have to look how we should plan for the dogs when we see the source code and for the pages, I think it will be mostly completed as far as and for our current schedule, + +Denis Lelic: Sounds good. + +Piyush Choudhary: so, Yeah, that's all. So. Can I stop using my screen? + +Denis Lelic: Thank you for your time, thanks for the updates. + +Tyler Wright: Yes. + +Denis Lelic: Thank you, Ty as well for the intro and retrospective, I'm not sure if it's called that way, but anyway, + +Denis Lelic: we'll talk in discord for Otherwise. In next week, Thursday. + +Tyler Wright: Yeah. Piyush Pierce just a reminder,… + +Piyush Choudhary: it + +Tyler Wright: much appreciate I know that you are working a number of things. that I'm thinking about if it can come to steering committee because you can not only talk about the website revamp, but you could talk about the potential work that you are going to be doing alongside Cloud most. So that would be great to have Arthur's here. + +Piyush Choudhary: Yeah, So I will also update submit the proposal by tomorrow as for A guidance. I got from an index of + +Tyler Wright: Okay, Hey, Arthur. We were just actually about to wrap up, we went through the agenda. We added action items inside of the discord, working group Akash, website and again, the notes will be updated very soon. I believe that there were specific feedback. + +Tyler Wright: For you. Piyush, right? But that Arthur, had to update some stuff. + +Tyler Wright: Or am I just reading That Arthur have to update some links. + +Piyush Choudhary: So, we just updated the Home Page button as you can see in the Hero section. So, in Video Section, Right, previously was going to console and right now it's tipped right now that is taking the users to the cloud nose. And it was officially announced by the pastrami yesterday that from Non-warts are the whole airport. So they put into developing and enhancing the cloud, most employment, and the development of concert will be stopped development and support of console board will be stopped completely from non-words, but it will be applicable to be used by those numbers, but the support and development of the stock from now onwards, + +Tyler Wright: Absolutely. are you saying that? Do you think? And this is a question for everybody here? Do we need to update? If I can share my screen. Do we need to actively update this page right now that points to both? Or do we want to leave it? Because Piyush is gonna have the revamp website and that's week and a half two weeks. + +Piyush Choudhary: I think we can keep it as it is right now because it's not a big deal and we will soon have a new website ready. So I think it's not a big deal to keep it like this is not + +Tyler Wright: I would agree with that. Denis, you have any issue with that? + +Denis Lelic: No, no sounds good to me. + +Tyler Wright: Okay, Is there anything that you want to talk about? While we're all alive. I know that you do a good job. Arthur of chatting and discourse, anything that you want to talk about live while we're here. + +Emmanuel Arthur: no, really, no really + +Piyush Choudhary: and I also Arthur… + +Tyler Wright: Okay, excellent. + +Piyush Choudhary: if you have any feedbacks for the new website and shared In the group artists thought anywhere else. + +00:30:00 + +Emmanuel Arthur: + +Emmanuel Arthur: + +Tyler Wright: All right, again there's nothing else and we'll meet up next week and we'll continue to work together between meetings. I know there's gonna be some sessions that are going to be set up for folks, to talk about design. Zach will be back in office early next week and again, I know it's a priority for me to get the docs work handed over to Piyush and this team as soon as possible. So I'll be working on that today. + +Denis Lelic: Thank you. + +Tyler Wright: Thank… + +Piyush Choudhary: Thank you. + +Denis Lelic: Thank you guys. + +Tyler Wright: Everybody has a great day. We'll talk online. + +Denis Lelic: Thank you. + +Piyush Choudhary: Or by take care. + +Meeting ended after 00:31:02 👋 + diff --git a/wg-akash-website/meetings/014-2023-10-26.md b/wg-akash-website/meetings/014-2023-10-26.md new file mode 100644 index 00000000..523eb213 --- /dev/null +++ b/wg-akash-website/meetings/014-2023-10-26.md @@ -0,0 +1,1098 @@ +# Akash Network - Akash Website Working Group (WG) - Meeting #14 +## Agenda +- Website Revamp Progress +- Discussion on Website Revamp: + - Docs Integration + - Get Started Page + - Data Sources Discussion + +## Meeting Details +- Date: Thursday, October 26, 2023 +- Time: 6:30 AM PT (Pacific Time) +- [Recording](https://z5ffy5w2liqufhaktycxtjmyyfbrpe5ewae72o7kviwi4eigwrna.arweave.net/z0pcdtpaIUKcCp4FeaWYwUMXk6SwCf076qosjhEGtFo) +- [Transcript](#Transcript) + +## Participants +- Denis Lelic +- Emmanuel Arthur +- Piyush Choudhary +- Scott Hewitson +- Tyler Wright + +## Meeting Notes +### Website Revamp Progress: +- Piyush Choudhary provided an update on the website development progress and structure, mentioning that the foundational structure is almost complete. +- Piyush mentioned that after discussions with Dennis, there will be some changes to the design and content. +- Piyush described the homepage and the upcoming changes to the "get started" page, which will be integrated into Akash documentation. +- Arthur asked about the high number of menu items on the website. +- Piyush Choudhary acknowledged the issue and mentioned that he would discuss it with Denis to reduce the number of menu items. +- Emmanuel suggested the possibility of using dropdown menus to organize related pages. +- Denis explained that in the past, dropdown menus were avoided due to restrictions from the Hugo template, and they preferred direct links to pages. However, they are open to reconsidering this approach if it becomes too crowded. +- Piyush Choudhary mentioned that within ten days, he could make the necessary changes for the new website to be launched. +- He suggested that even if real-time pricing data takes more time to implement, they could make the website live initially and add real-time features later. +#### Docs Integration +- Denis provided clarification regarding the history of the get started page and the Docs and its integration into the website.. +- He mentioned that they initially created a get started page before bringing the docs into the website. +- Now, with Piyush and his team working on bringing the docs and website together, they are considering integrating the get started page into the Akash Docs. +- Denis emphasized the importance of integrating the "get started" page into Akash Docs to create a centralized hub of information for users. +- Denis explained that clicking on topics like "deploy an application" would lead to a page with Cloudmos and additional deployment resources linked to the same environment within the docs. +- Piyush mentioned that he had access to the docs but needed to integrate the to the website from scratch. He wanted everyone to review the content that had been created for the new docs. +- Denis Lelic expressed understanding and asked Piyush to share the content for review. +- Tyler Wright suggested that Piyush post a message in the Akash website working group channel to ensure clear communication, especially involving Scott in the conversation. +#### Website content and data sources discussion +- Piyush highlighted that all content comes from markdown files, making it accessible for non-technical individuals to update. +- Piyush mentioned the token page and price metrics, which will be fetched from Cloudmos APIs. +- Denis Lelic discussed the possibility of extracting network activity data from Cloudmos, particularly for the development section. +- Piyush explained the need for data from Cloudmos providers for three pages: pricing calculators, analytics, and network activity. +- Piyush mentioned that once the APIs are provided, they will implement real-time data on the Akash website, making the content dynamic. +#### AI assistant on the Akash Website 2.0 +- Denis Lelic requested Piyush to access the Akash Web 2.0 Figma file. +- Denis pointed out the support page on the Figma file and discussed the idea of implementing an AI assistant on the support page. +- The AI assistant would allow users to ask questions and provide different resources in response. +- Piyush expressed that it's a good idea and suggested integrating an AI system on the page. It could handle various user queries and technical issues. +#### Tools and Apps to be featured on new website +- Denis discussed the need to replace a console on the website and suggested considering what kind of tool or app could be placed there. +- He mentioned that since they are sunsetting the console, they have the opportunity to feature a different tool. +- Zach Horn discussed the idea of [featuring SDXL](https://sdxl.akash.network/) on the Akash website and how it can serve as a touchpoint for users to experience Akash's computing capabilities. +- Tyler Wrexpressed support for the idea of showcasing SDXL and other AI-related apps on the website. +- Zach Horn expressed the desire to surface SDXL on the Akash website, as it allows users to experience Akash's computing capabilities by providing prompt-based image generation in seconds. +- Zach suggested integrating SDXL into the homepage section or creating a dedicated section for demos, allowing users to try Akash quickly and serving as a call to action for Akash AI/ML and GPU-related deployments. +- Tyler mentioned that he had experimented with these apps and emphasized the value of showing real deployments on Akash. +#### website revamp and pricing information +- Tyler noted that the new website will significantly improve the ability to answer common user questions regarding how to use Akash and the associated costs. +- Zach Horn commended the pricing page views, emphasizing their value and how much it has been needed. +- The group discussed the importance of addressing user questions about the cost of using Akash for various compute needs. +- Denis suggested the idea of having ready-made packages for users, such as general-purpose, GPU-optimized, and memory-optimized, to simplify the process. +- The need to display bids, potentially pulled from the console, was mentioned. +- Tyler noted the need for a team effort to ensure the accuracy and consistency of pricing calculations, as different tools currently yield varying results. +- The collaboration with Cloudmos and core team members was mentioned +#### Discussion on pricing information and the complexities of calculating +- Scott Hewitson emphasized the complexity of pricing in an open marketplace like Akash and compared it to hosting on Airbnb, where earnings depend on various factors. +- Tyler Wright acknowledged the complexity and mentioned the need for some level of standardization. +- He referred to a support tool built by Scott Caruthers for simulating deployments and suggested using real-time pricing data to calculate accurate prices. +- Zach Horn proposed showcasing deployment pricing on the website, allowing users to filter by specific configurations, such as Nvidia A100, and see the current pricing on the network. +- He acknowledged the complexity of implementing this but highlighted the potential value it could provide. +### Deployment Page Task +- Piyush suggested assigning the task of moving a page back to its previous version to Arthur, as he had implemented the code. +- Emmanuel Arthur volunteered to work on this task. +- Denis Lelic and Piyush clarified that the task is to reverse the order of sections on the "deploy" page +- Piyush mentioned that the deploy page needs to be changed to refer to Cloudmos instead of console +- Denis Lelic suggested focusing on removing the console and just having the Cloudmos page initially +- Tyler Wright emphasized the importance of prioritizing the removal of the console and redirecting users to Cloudmos since the console is deprecated. +### Other matters Discussed +#### Homepage Hero Section Concerns +- Tyler Wright raised a question about the homepage hero section, expressing concerns about it being text-heavy compared to other websites. +- He shared a [link to an article](https://bitcoinethereumnews.com/tech/a-deep-dive-into-the-most-promising-projects/) featuring Akash Network, showcasing various website headers. +- Tyler suggested considering the addition of visual assets such as decentralized network or hardware imagery to enhance storytelling. +- Denis Lelic expressed support for the idea, mentioning that the current direction was inherited from the previous website. +- Denis suggested exploring what can be done to improve the hero section and researching current trends in other projects + +## Action Items +- Tyler to coordinate a discussion about pricing, potentially through a working group session or in the Sig Analytics meeting. +- Group to investigate the feasibility of showcasing real-time pricing information. +- Group to develop a strategy for launching the new website. +- Arthur to complete the implementation of the Deploy page. +- Piyush to share the content of the new documentation on Discord with the group for review. +- Piyush to implementing real-time data in the new website +- Denis to explore improving hero section of website. +- Denis to explore adding SDXL to the new website + +# **Transcript** + +_This editable transcript was computer generated and might contain errors. People can also change the text after it was created._ + +Denis Lelic: Welcome everybody to today's working group meeting for Akash website. I hope you're all doing well. so these meetings happen every week on Thursday. I'm not sure it's What Pacific time is that Tyler? Sorry? + +Tyler Wright: You're fine. It's Eastern Time. 6:30 AM Pacific. + +Denis Lelic: Okay, sounds good. So yeah. Maybe we just kick it off and start with the latest of the updates from piyush and his team they've been working on the website revamp for the last couple of weeks. And basically every week we have a look at the progress they made. Later on, we're answering questions. Make sure there's no blockers and we keep this thing moving and progressing. A H they have anything to share. + +Denis Lelic: Any updates from last week? + +Piyush Choudhary: if I'm sharing with + +Denis Lelic: Thanks. + +Piyush Choudhary: Is my screen visible? + +Piyush Choudhary: So I've dropped the link to see it live on your sleep you can check out this link that have talked in the chat Suite Life. So mostly we are almost done with the foundational structure. We have almost worked on all the pages but after discussions with Dennis today privately, so there are some weeks that will be made the design and also the content that has been decided and also I would ask all the quality numbers to talk to the content of all the pages including development community and about sages. So if you look at the overview of the website We have the home page. We have the blog page. We have getting started page. But this getting started page would be moved to the docs as per this plan. So. + +Piyush Choudhary: So they're talking about it later. I've seen discussions and then we have the token page ecosystem page about page lesson branding page across Community page and lastly development page and it comes to the content right? So we have three About page development page and Akash Community page that contains the general contents. And then lastly we have the dogs which contains the overall structure or guidance tutorials or whatever, So if we look at the development page, right, so this is the development page right on the left hand side in the files. + +Piyush Choudhary: Or the content files that we can change and the content will appear here and on this page, but after seeing the recent designs, so we'll be taking it a little bit only this part will remain here and on this space section will be removed and the content will be expended because after being somebody search as I can see in the designs done by many. if we talk about the content of and so these things + +Piyush Choudhary: So this list of projects it has five columns if we keep the only space section which is designed by us. Then it will make Things look very compressed and it will not be good. So for three pages development community so these three pages are not kind of tutorial but be basically a kind of location the general details about what's happening because the recent development proposal is a job. So we'll be removing this section and will be extending this middle content to the whole page. here incidentally + +Denis Lelic: Yeah, Regarding this menu on the right side. It's called on this page. I think that's something we're just inherited from the previous page and who go template. + +Denis Lelic: So my suggestion would be like to kick it out if in case we don't need it. That's something that's often used in the docs. + +00:05:00 + +Piyush Choudhary: reading this + +Denis Lelic: but If the content is shorter, there's not So Much Information going on and I think there is no need for that and we could expand the main content. and just there's gonna be much more real estate for the main content and the focus of users could be centered around the main content + +Piyush Choudhary: yeah, it shows so. + +Piyush Choudhary: so there are three pages basically in the whole website related to subscribe so that would be Affected by the state one is a development which as you can see one is a community contributions with and when it's about page for this key pages will be affected and this on this space sections will be out and on this space actually will be kept in the docks because it's usually captained at all because we have the bigger contents and on this space section such as the navigate to the full contents, so we will just take it out and well as for the middle text will be expand into the right completely on the left part of the cap as it is that you are seeing on the screen. + +Piyush Choudhary: this is the homepage that you are looking so we have get started page and get started H. We have two pages to plan applications to become a provider. And this all will also be kicked out and customize your account should experience in the product and people start from here this stage. So we implemented only the cloud notes because Council console support has been discontinued from nonverbs. So this is what the get started which looks like but later as for the new designs the get started page will be made to be a part of a cost talks because documentation still have the home page. I sell the direction by Denis. So this on page helps us is the overview of stocks and accordingly. We will Implement our cost documentation as well. + +Piyush Choudhary: And this is all about get started page. I think it has all been discussed in the past. So there's not much but there are some changes that will be made to the homepage. For example. We talk about joined the terminating so these thoughts so we have two options to make this cards Dynamic one. We subscribes to the Twitter API which costs around thousand USD per month and then implement the API endpoints will be displayed in your time. we can just have the markdown file we bear we just have to Keep on updating only three to four details, for example. the content of the text the username and the image so this three things will be + +Piyush Choudhary: updated in the markdown file and we can call it instead of following pictures. Let's say someone tweaked a good thing or let's say we want to show the Weight on this page, right? We can just implemented with text into the modern file into the display here like this as you see or if we want to keep things Dynamic then we can subscribe. + +Piyush Choudhary: So this is the homepage they were saying on the screen and we have the development page. Yeah. + +Tyler Wright: I know there's some hands up but my vote is certainly for the markdown file approach because I don't think those testimonials are. that big of action but I saw that Arthur had his hand up and then Dennis. + +Piyush Choudhary: Okay. + +Emmanuel Arthur: Can you guys hear me? + +Emmanuel Arthur: Yeah, I want to ask why we have so many. Menu items at the now back. Thank you guys do something about it. + +Piyush Choudhary: Yeah, so I will have a chat with the in to minimize the things because I also personally feel like we are having a lot of menu items in the network, but I always get the direction because the pages has been increased the same place. So I always get the direction to keep things. + +Emmanuel Arthur: Maybe a drop down will help. + +00:10:00 + +Piyush Choudhary: I think we can combine you menu items or… + +Emmanuel Arthur: Keep them. + +Piyush Choudhary: cities and can have a drop-down for example. Let's say development community so these three pages are mostly related to each other so we can have a single headline here. And when we go over it the development community and about section drops down. Or we can keep it like this as well. + +Emmanuel Arthur: + +Piyush Choudhary: This. and it's yeah you + +Denis Lelic: Regarding the menu items. Previously, I don't know why maybe it was because of restrictions from that Hugo template we use but I know Greg was avoiding any dropdowns. He wanted Direct. links to the pages so we kind of Kept that idea and… + +Piyush Choudhary: he + +Denis Lelic: just keep on adding new items up there. But if We have a good argument that not working. It's getting clustered and overcrowded. We can always say here's the solution we discussed that here are the problem. And so on and yeah, we can do something about it for sure and regarding a couple of other things piyush mentioned just to provide some. + +Denis Lelic: clarification around it a while ago I have no idea when that happened, but Luna was also part of this calls and I was also a discussion and working group for Akash documentation where we discussed to get started page around in the Akash Docs. but it took some time to + +Denis Lelic: Develop and bring those dogs into the website. that's why we kind of just a get started page. Before we brought docs page into the website, but now since we have piyush here and his team and they're working on to bring the dogs. And the website together, so we have this experience in. One website we could get started page into the Akash Docs. + +Piyush Choudhary: he + +Denis Lelic: and it would provide + +Denis Lelic: one Hub of information. So anyone who's trying to get started will be served with additional items are in the menu bar. on the left or for example, if you click deploy an application you'll be presented with a page with Cloud nose, but again, we can list additional deployment resources at the bottom and it's going to link to the + +Denis Lelic: Same environment meaning it's gonna stay in the doc's page. so that's something I Changed in the last week. of course. We haven't discussed this until now so I just provided some context context around it for Zach Taylor and… + +Piyush Choudhary: You right. + +Denis Lelic: Arthur and emph was just talking this morning. About it. So if you have any comments any suggestions like I Arthur please let us know we can always Change or adapt the direction. + +Denis Lelic: and one additional thing would be + +Tyler Wright: Yeah. + +Denis Lelic: yeah on the homepage. We had couple of tools to get you started. And a couple of templates listed there. But now we have one space available for consoles and to replace the console. So I was just thinking about what kind of tool or app we could place here. Yeah Thai + +Tyler Wright: A couple cool question. I just threw something this is related to the homepage. So I don't want to cut off what you're talking about with the model section, but on the banner. And this is just an open discussion on the banner section. I just threw a link in the chat that an article came out that features Akash Network and in these Banner image shots, it shows basically I think the header Banner for all the various website. I feel compared to some of the other folks in the space. Our better Banner is a little bit text heavy versus having text and some imagery or maybe some background imagery. I just wanted to open that up to discussion very briefly to see if anybody else had any thoughts comments. + +00:15:00 + +Tyler Wright: questions or Should we just keep it as is and… + +Denis Lelic: Are you talking about the hero section with the headline? + +Tyler Wright: just continue to move forward? + +Tyler Wright: Yeah exactly. I'm not saying that headline should go but I wonder if we want to add any sort of accompanying visual assets that maybe show a decentralized network or some more like Hardware or something, that maybe the increases the storytelling or maybe it's not necessary. I just want to open it up to the group for discussion. + +Denis Lelic: Yeah, I'm totally for it. I think this direction we have at the moment is something again. We inherit it from the previous website. So I think everyone was just trying to be respectful of the previous website and the direction and Greg has set ups so Yeah, just with the dropdowns we can say. Here's an idea. And this is why we think it's It was part of this discussion in this working group, and we can also provide examples how other projects + +Denis Lelic: hero section looks like and when it's listed together, for example, in the link you've provided we can say Hey, we're kind of lacking. We need to step up our game. + +Denis Lelic: Yeah, I'm just gonna add that an action item. for the next week that maybe explore what can be done here and Maybe explore what are the trends at the moment what other projects are doing and so on so on? + +Piyush Choudhary: So I think we are in good pets. So I'm just giving our view again. + +Piyush Choudhary: So we have the homepage then we have superstars that are ready for maintain about which contains the general contain contents. Whatever is meeting such a talk, and then we have the tops that will be kind of percent of the tutorials or Royal. And then we have the ecosystem page which has already been done. And the good thing is everything is coming from the maldon files. So even a non-technical person should be able to implement the new projects at the new projects as well. And lastly we have to open page and doesn't page metrics will be patched from the cloud most apis. Just so that in the new design file there is pricings and some guidelines for example + +Denis Lelic: It might be looking at network activity. It's part of the development. + +Piyush Choudhary: we have so yes. + +Denis Lelic: Yeah. there's some data we could pull from cloud nose. especially around network activity + +Piyush Choudhary: so there are three pages that we need data from the cloud nose providers when it's pricing calculators one is analytics. So I asked for the API and points all the way to fetch the data from all these three pages in your time. So in the Discord the chat of cloud mods already. So once that is provided will be able to implement that on the cash website as well. So we will kind of have a details on the cloud most website as it is and we will also have the details on the official website as well. for example, if I go to about section when I click on the pricing? this presentation will be dynamic and you just be able to scroll up down and presentation expected guys, but + +00:20:00 + +Piyush Choudhary: We need to have some kind of detail salts some guidance. Although I found they play but there are some Arrow sign getting I just need a little guidance from the problem or stream on how to catch the real-time data from the + +Denis Lelic: Yeah, there's one thing. + +Denis Lelic: Tyler mentioned a couple of minutes ago. This price needs to be in the navbar. we could move that and just keep it in the photo section. I'm not really sure how much traffic we get on. discussions + +Denis Lelic: because we already have the GitHub button over there. + +Piyush Choudhary: + +Piyush Choudhary: and I think we can remove this from the navbar as well discussions. + +Denis Lelic: But we do mention discussions in the homepage right away. when we have a call to action join the community and then we have a couple of testimonials there above that. + +Piyush Choudhary: when + +Denis Lelic: There's GitHub discussions I think in your button you're just missing discussions inside so + +Piyush Choudhary: If so, yeah, I will demand the discussion with them. + +Denis Lelic: So we could reduce the amount of items in the navbar just kicking out. press + +Tyler Wright: Real quick on the back of the homepage real fast. just I know that I get the steering committee has been moved to next Wednesday as a part of the steering committee. I was hoping that piyush I think you already talked about this is going to give a short demo of the progress for the website. I think everyone will be excited to see ahead of that. I would just love and I know this is low priority right now, but ahead of that meeting. I know that we made some adjustments to the current website to adjust the language from access gpus to reach out. I would love to keep that consistent so that it doesn't become a point of distraction, turn that demo. + +Piyush Choudhary: yeah, sure. Yeah. + +Denis Lelic: Yeah, maybe you just have a look at the sigma file. I've updated it there. + +Piyush Choudhary: if I + +Denis Lelic: So we have deploy now and additional button to reach out. + +Piyush Choudhary: I serve. So yeah,… + +Denis Lelic: yeah. + +Piyush Choudhary: By first number I think I'll be able to update these days as well by keeping out on this way sections. And yeah, I think by first talk no, but they will be more progress and fixes Final Fix so I think there is one item that we can assign to. + +Piyush Choudhary: Arthur if you guys don't know + +Denis Lelic: Which one? + +Piyush Choudhary: this page moving back to the previous version because I think he implemented the code so it will be possible for him to move back this base to the previous version. + +Emmanuel Arthur: up yeah, I would like to work on this and + +Piyush Choudhary: + +Tyler Wright: Share with that at all. So is that one of the open issues that we talked about a couple days ago that we would just want to hand over to? + +Piyush Choudhary: Yes. + +Tyler Wright: Let's see. I know assistant change. The order has happened done. Let me just + +Tyler Wright: Sorry, I'm talking a lot. So we have a couple of issues. I think one's closed but we have This issue that was opened a couple days ago by myself here. She did something that you also want Arthur to handle. the order of the section that get started as well as that main page. + +Piyush Choudhary: So we definition. + +Denis Lelic: It's just reversing the order. So we start with deploying. + +Piyush Choudhary: Yeah, so basically only there is a change on this deployed page so right now is we can see we have two sections apart on soil and… + +Tyler Wright: Yeah. + +Piyush Choudhary: crowd most we just want to keep the clock Mouse on this page as well the directions so I think that instant Denis… + +Tyler Wright: Yeah. + +Piyush Choudhary: then just share the pigma political also for this page and also can just reward the code base and the implement the previous versions as for what it usually + +Tyler Wright: Yeah, I think that's clear I guess additionally. have you already implemented the saw for issue 279 or is that something you also want Arthur to do? + +00:25:00 + +Piyush Choudhary: With chemical means I didn't check they should presentation. + +Tyler Wright: yeah, no problem. + +Piyush Choudhary: That's myself. + +Piyush Choudhary: can you tell what it is related to? Is it opened recently? + +Denis Lelic: It's part of this. + +Tyler Wright: Yes. Then you could… + +Denis Lelic: Yeah, go ahead. + +Piyush Choudhary: I think + +Tyler Wright: if you can move up to page a little bit to get started if you can click on the get started tab piyush. + +Piyush Choudhary: we have + +Tyler Wright: perfect on this page the leftmost tile is access high performance gpus Basically,… + +Piyush Choudhary: yeah. + +Tyler Wright: the direction is we want to switch these tiles. So the deployed application should be the first tile that you see and then the access high performance GPU should be the second power or… + +Piyush Choudhary: Yep. + +Tyler Wright: we could talk about even moving that down the page a little bit depending on what folks here think and we can move become a provider to the second tile and then basically have this tile last my opinion is that deploy an application become a provider be second documentation should be third and then this should be fourth but That's just my thoughts. + +Piyush Choudhary: So I think I can also update it. + +Tyler Wright: Does anyone else have any? + +Piyush Choudhary: It's not a big deal, but Yeah, I can do it now. It's + +Tyler Wright: Okay, Zach Dennis. So you guys have any preference on the order of operations for these four tiles? + +Denis Lelic: Nope, sounds good to me. + +Zach Horn: Yeah, strong preference. I would say having deployed the first makes a lot of sense, but whatever needs to be done. + +Piyush Choudhary: so yeah,… + +Tyler Wright: Cool, how can we do? + +Piyush Choudhary: so I'm just rewarding the things for the deployment applications by just keeping the cloud notes and I will just Change the order of the tiles under get started on the official domain right now and we'll continue working on the new website. + +Tyler Wright: excellent + +Denis Lelic: There's another item. I wanted to just quickly discuss piyush. If you could please just go to the Akash Web 2.0 figma file. + +Piyush Choudhary: Yes, I want. + +Denis Lelic: And if you go to the support page, it's bottom left. + +Denis Lelic: yeah, I was just thinking about if we could implement. In the future, of course some sort of AI assistant so we could start with a question and it kind of provides different resources. + +Denis Lelic: and below that we could just keep it simple direct users to GitHub issues Discord or discussions. But in general it would serve some sort of I don't know search engine / AI assistant. + +Piyush Choudhary: just + +Piyush Choudhary: yeah, I think it's definitely a good idea. We can integrate AI system and do this page where users will be able to ask any type of questions related to a cost also real time happenings as well integrated. We can also have a train version where the AI agent will be able to answer any type of technical proportions all the issues I think we already did this kind of thing with the Equus AI as well. I think if + +Piyush Choudhary: there's some issues. + +Piyush Choudhary: presentation So I think we already made it this kind of stuff where they got Tuesday is so we can just click that up to be integrated with. + +Piyush Choudhary: presentation of selfish + +Denis Lelic: what about I think we just mentioned it, but we haven't really discussed Akash console on the home page where we have that tile Dedicated for Akash console… + +Piyush Choudhary: he + +Denis Lelic: but now since we're like sun setting it we could replace that with some different tool. + +00:30:00 + +Denis Lelic: I think it's best if you share the figment file. + +Denis Lelic: and a home page right here. + +Denis Lelic: Yeah, so we have a couple of tools listed here. + +Piyush Choudhary: e + +Denis Lelic: The main are Cloud nose and Prater. but we have additional space to Serve some others. Otherwise we could just remove them. And showcase only two. Yeah Zach. + +Zach Horn: I'm just gonna throw out there that I would like to surface xdxl on Akash somewhere on the new website the thing that it does really well that it's already proving out is that it's a touch point that lets people like experience. What compute on Akash feels you can put in a prompt and it returns a finished image and four seconds. So we have all these apps that people can deploy which is obviously we should keep those top of mind and focused on the way they are but I don't know what this section would look like it could + +Zach Horn: I could see it integrated into what you're looking at right now Denis or maybe in its own section that feels a little bit more. This would not be the copy but something like demos, that being the vibe of it where you come to the website. It's like let me just try it out real quick, and you can go to stxl on You can put in a prompt see the images being generated the other thing that it does. Excuse me. Is it serves now as a call to action for some of the things we're doing with Akasha Mel and tailored deployments with gpus the way it's set up with a call to action. So just a little bit, but I could see it either integrated into the section you're looking at now or in its own section that serves as easy to experience demo that then is also a call to action to reach out to us. an thoughts on that? + +Denis Lelic: Yeah. Yeah,… + +Tyler Wright: plus 1000 + +Denis Lelic: I'm just actually putting something together It could be kind of fairly simple. + +Zach Horn: Yeah. + +Zach Horn: mmm + +Denis Lelic: We could start what's possible and we just showcase. couple of I don't know it as the Excel confused, whatever we think. + +Zach Horn: definitely + +Denis Lelic: and that would be like what's possible? For now, I'll just put any just to have a reminder. What's this section about and + +Zach Horn: Yeah. + +Tyler Wright: Zach do you see it I'm just a simple call to action like being built right now and you click on it and you go directly to sdxl or do you see it goes to a case study page to show how Akash is being leveraged and then it goes sdxl. Do you think it's like you prefer to be one click so people can use right away, or do you want to have some supplemental information? + +Zach Horn: I think yeah, if you're asking me for my Grand Vision, here's the Grand Vision is That it has a section the first step like… + +Piyush Choudhary: + +Zach Horn: if we're doing order of operations, I would say the easiest to just have a direct right to xdx on This is some true Alpha, but if we're thinking down the line, I would say I would see it as a section on the website that surfaces the tool directly but then also has supporting information. So it's like case studies on how it was developed, it could be guides and content on how to prompt or how to use it. It could be, other adjacent content around how to develop on Akash more broadly and then a direct CTA on the website to reach out if you want to do something similar you're looking to deploy custom models or all that. That's obviously very down the line and there's a huge amount of work that we're doing right now. So I'd say the easiest first step is just link right to it people can click through and kind of poke around and figure it out for themselves. But if we were thinking down the line definitely a more built-out section that includes supporting content and possibly a direct call to action. + +Tyler Wright: I love that. Yeah, I mean I think sdxl is the best case scenario. I would love to show I think this in kind of over the ecosystem page too, but website's deployed on akash, so the people can To your point just click on things and back. this is actually leveraging the Akash Network right now and… + +Zach Horn: Yeah. + +Tyler Wright: just making mess around with the functionality, but I think sdxl and any other of those kind of AI. + +Tyler Wright: Models are apps that you're working on would be great. I was actually just messing around with these a couple days ago And it's like in that same vein of it being a open source tool for another project. + +00:35:00 + +Zach Horn: Yeah, definitely. I think As DXL is definitely a good one because it's running right now and it's performing and getting great usage come to you as another good one and that's potentially coming soon. definitely stay tuned for that. I'll add more info on that the next week or two, but What the dream is that eventually someone would come to the website they click through to these things. They get a sense of what's possible. but really what we want That at They see it deployed. there's a nice keyword tie-in with a 100s and then they go. I want to run XD Excel. But really what I want to do is run my own custom model, and then they click through on that call to action end up talking to somebody and we can get them deployed. + +Piyush Choudhary: look up just + +Zach Horn: With their own custom model. So yeah. Just reading your comment. Yeah, definitely. + +Piyush Choudhary: and I also think Akash can also invest established in the Strategic partnership with the AI startups or even if some community members are building some AI related startups are fast and consider supporting them in turning them into a startup. So this can also have a great positive impact from the Holocaust system. even the investor will be able to see These are the startups that are in one Akash officially and Akash can have a strategic partnership with such kind of things instead of just keeping them limited to just a simple or just projects. So yeah, that's not + +Zach Horn: Yeah, I love any touch point where we're showcasing other projects being built or leveraging Akash computer. I think that's always really strong for us and it's starting to get picked up by the mainstream we saw yeah, I'm sure you guys saw we had that feature in some before yesterday. But that was the focus of that piece is read the reporter went out and interviewed all these projects either Thumper and Foundry who are leveraging and caution various ways. And that was almost the focus of the story which I think is always very strong because it just shows people like choosing Akash from an entire Market of options. + +Tyler Wright: Yeah, I love that. I think the question I get asked the most I'm sure this is for everybody is how can I use Akash and + +Tyler Wright: How much does it cost how much can I make by providing and I think that this new website revamp is going to do a much better job of answering both of those questions. So + +Zach Horn: Yeah, I'll just jump in and say because you were showing it earlier. The pricing page views that you were showing that's I mean really amazing. I mean that's like something we needed forever. So I'm really excited to see that get built especially with real-time data. the ties Point like Yeah. + +Tyler Wright: Yeah, I'm gonna connect. website + +Zach Horn: and nowhere is that's just the thing that People ask about all the time. how much does it cost for XYZ amount of compute. And then also if you're a provider how much can I make if I provide, x y z resources + +Denis Lelic: Yeah, one thing here. We have to check with. Cloud nose but I try to ideate something for example what user would want but they don't want to go through all of this Hassle and Click and everything and set up these parameters and So what we could do is just have packages ready. So basic general purpose GPU optimized memory optimized so you can just click through and What would happen in the background? We would actually request bids and… + +Piyush Choudhary: he + +Denis Lelic: below this. We would somehow have to display bids. + +Denis Lelic: maybe we could even pull that from console. But that's something we just have to To see if it's possible. + +Tyler Wright: I think this is gonna be a team effort to be honest is something I would say that cloud most I know that their pricing tool is great. But it is incomplete. and I think cute Scott hewitson who's been just voying on. This call is going to be called into action for us to actually understand how some of these calculations are being derived and make sure that this makes sense, because one thing that we've seen is especially the provider side people have used Cloud those people have used a tool by a member of the community people use pray tour and they use those three different tools and put in the same information. They're going to get three separate answers that are not anywhere. + +00:40:00 + +Tyler Wright: The don't even have the same methodology. So I think we need to work with Cloud most but also work with members in the core team. To figure out the calculation first and then we can optimize it. + +Scott Hewitson: Yeah, I'm just on that point. I mean it's kind of like, if you ask hey how much money can I make having an Airbnb like being a host on Airbnb? it depends on the market depends on how big it is depends on so there is no one size fits all it's an Open Marketplace. Yeah, I don't know. I mean I think people have a hard time understanding that when it's like you go to other protocols and it's like okay, I put my minor up and I'm getting that fixed amount because that's what it is. It's a Marketplace. So that's all I gotta say. + +Tyler Wright: yeah, I do I get what you're saying for sure, but there should be a little bit of a standardization or to denis' point. I think that's Scott's Caruthers of the part of a support tool. He built a while back had some sort of replication tool. So it was simulate deployments and see what kind of pricing it would get back and maybe again we can base it upon a real-time pricing, but I think everybody's a good point. I just want to make sure that we just take the time to really hone in on how pricing is being calculated. + +Piyush Choudhary: Really? + +Zach Horn: That's it. I'll just jump in quickly to say that if there's a way that we can pull deployment pricing in some way that we're just showcasing it on the website. that would be great. Because to Huey's Point. Yeah, there's unlimited optionality that influences what the pricing might be. But if you think about the Airbnb example the way you would get a sense of what you could earn with an airbnbs. You probably look for comparables. So if we could figure out a way to Showcase that of let's just choose Nvidia 100. the dream would be that you go to the website. Excuse me. I'm on week four of this cold. So I'm still getting over a cough, but the + +Zach Horn: You go to the website you could filter in some way by a 100s and then see what the current pricing on the network is that would be the dream. I mean that's quite complicated because you'd have to pull live pricing or simulate a bit to ties point on what Scott Carothers was working on but If there's a way to do that, that would be extremely valuable in my opinion. + +Scott Hewitson: Plus 50 to that. + +Piyush Choudhary: So yeah, I think we have three. Dynamic things that you can Implement on the official website and it's the price compare when he's Akash and when it's a providers. so I just want all the 14 numbers to provide us with the + +Piyush Choudhary: apis and points all the directions all the guidance to pets all this details properly and from where to fetch 30 days as soon as we get the UK and points or the proper guidance from the sources where we can get the data which It will be much easier forest and return the official website that you're saying right now you're staying + +Tyler Wright: Okay, that may take a week or so maybe even longer. I guess the different point if we talk about even provider because I just saw you show provider screen. One thing that we're still trying to find tune is. + +Tyler Wright: Pray tour and cloudmose have different statistics on provider. I know that they're taking him a different cadences and over different periods is too, but I just want to make sure That you had the most up-to-date data and then hopefully it could standardize it across those Partners so that everybody's kind of feeding the same data whether it's on Akash Network Cloud, no sort. + +Piyush Choudhary: So this is the tool that we made for the cost of account. + +Tyler Wright: Play tour. + +00:45:00 + +Piyush Choudhary: So I think we can pick this To have an EA assistant on the support page. So we're working on it very soon and also be proposed this Akash deploy tool. To the discussions where you just have to put in the GitHub username guitar producer and password username Docker people stadium and just click on generator still want this tool does this it just pulls out the code created open image push the docker image The Hub here the perfectness required. We all have the option to say my budget is I need this in this operating system. and in just one UI you can have Looks like they still so it's in early stage that we've submitted in that con. so + +Piyush Choudhary: yeah, this area system can be customized integrated on the support page of the Cross. So I will look into it. + +Tyler Wright: excellent All… + +Denis Lelic: Sounds good. + +Tyler Wright: Now we started a little bit late, but we're coming up on time. Is there anything else Dennis that you wanted to cover Zach or anything else that anybody else want to talk about before? We drop off. + +Denis Lelic: No for me. Some action items for next week. I want to explore the Showcase part Zach just having a showcase and case studies and so on. I'm just wondering is that part of the ecosystem or it's a thing on its own? the next action item. Would be homepage and the hero section Tyler mentioned. + +Denis Lelic: I'm just wondering what can I do to help around the pricing page? Yeah, it's Tyler mentioned. We probably have to involve Max's Scott. + +Denis Lelic: It's a tricky one, but I'll keep it in my mind. So. + +Denis Lelic: Yeah. + +Tyler Wright: My talk is either have a working group session that's specifically about pricing or wait till this again analytics meeting and talk about it there. But again, I want to get this done in a week to 10 days to try to figure out because this is a lingering problem and I think now we have A reason to talk about it a little bit more specifically and no figure it out. + +Denis Lelic: cool + +Emmanuel Arthur: Hey page, so. Are you going to work on the issue that Tyler has raised on the top as well as the Detroit? + +Piyush Choudhary: Yeah. + +Piyush Choudhary: so yeah, what you can do is you can work on this Detroit page, So this deployed page. Needs to be worked back to just proudmose. And of course Council needs to be moved. If you can complete this by tomorrow, then you can also just change the tiles it will. This week lines support or else if not tomorrow, then I will just change it within tomorrow. + +Emmanuel Arthur: Okay. + +Denis Lelic: Yeah, me and Arthur actually talked very shortly about this page that we're seeing now. Unfortunately, he doesn't have access to the code. + +Denis Lelic: He has done previously where we had educated page for each of these products also in cloudmouse. So Arthur mentioned he would have to build it again from scratch just for clone of + +Emmanuel Arthur: Yes, yes regarding that page. What I did was when I was implemented this page arm. I deleted everything then rewrite the quote again. And when you check the page, you could see that at the right side the new design that Denis had time for the cloud most Beach you could see that there will be some slider. Implementing that would be a huge challenge. So in fact of the time giving I think if I'm able to work on it. It's going to be like maybe tomorrow evening 8pm you and make it PR on it. Yeah, because I need to make sure that that's like that will fit on all screens. Yeah. + +Piyush Choudhary: Yeah, No. + +Denis Lelic: If the slider is a big issue for you, maybe we can just focus on. removing console and + +00:50:00 + +Denis Lelic: just having the cloud nose page there and later on in an extra PR you could create the slider if you wish. + +Emmanuel Arthur: Okay. + +Denis Lelic: You mean the gallery slider, right? + +Emmanuel Arthur: Yes, yes. Yes. + +Denis Lelic: Okay. + +Denis Lelic: One sec. + +Emmanuel Arthur: But in the teamstone needed to get it done I can work on it, but it's going to take a couple of hours to face it but I got still work on it though. + +Tyler Wright: Thank you I know Arthur this is a higher priority because console has been deprecated. We just want to make sure that people are going to Cloud most and not to try to use console which is not optimized from a user experience standpoint right now. + +Emmanuel Arthur: + +Denis Lelic: Okay, anything else we should mention before we wrap it up? + +Piyush Choudhary: So I have one I was like,… + +Tyler Wright: I think Im + +Piyush Choudhary: I know we call ten days I think will be in good position to make this new website. what should they steering committee meeting? I'll just make the changes. accordingly within this Indus 10 days and then we can make the new website officially provides I think and then with pricing things takes time, we can still make the website live and If there endpoints all the ways to punch the real-time data, we can Implement that later on as well. + +Denis Lelic: Sounds good. + +Tyler Wright: That sounds good to me. we'll talk a little bit next week. + +Piyush Choudhary: or else yeah. + +Tyler Wright: We'll talk a little bit next week after the steering committee about next steps and taking a live strategy, just want to make sure all the links are working. We do have to think about current links that Zach has been putting on Twitter and making sure that we're not just setting ourselves up to have a bunch of broken links. So I think there's a little bit of leg work. We at least have to think about my strategy standpoint, but we'll focus on that next week. + +Piyush Choudhary: It shows we can always give a time for the final touches. but I'll try to make sure that the possible we have the pricing and points Etc. So it will look much better. We can implement this. + +Denis Lelic: cool + +Piyush Choudhary: So I think the direction is pretty solid so far. We are directions that can someone base. cost as well as smooth and we will continue doing the same and hopefully if not 10 days within next to the weeks, the new website will be like we show you on the official + +Tyler Wright: amazing + +Piyush Choudhary: Also I forgot you guys have time. + +Denis Lelic: our piyush if anyone else has Time they can stay in this call. Otherwise if have Did you want to share something else? + +Piyush Choudhary: If so, I just want to say that I got the access to the new docs. But we have to implement a dog space from scratch because the new design has been Contributes including the getting started page, but there is a content for doing the docs. So I just want you guys to take a look at the content that it's been done in the dark's new docs orders or code base. So we're doing cementing that content. So if it is incomplete, just We will not do that. It's complete. just inform us so we can Implement that content as it is and + +Denis Lelic: Okay, cool. + +Tyler Wright: Right. Yeah piyush. Can you throw that message and the Akash website working group channel, so I'll just make sure I'm clear because I might want to make sure that Scott is included on that conversation. So just throw anything related to the docs in working group of class website and then we can talk about async. + +Piyush Choudhary: Sure, always. + +Tyler Wright: All right, if there's nothing else and again, we can just drop off here. Some of us will be in contact with you shortly. + +Meeting ended after 00:55:51 👋 + + +# **MT-7) - Transcript** + + +# **Attendees** + +Denis Lelic, Emmanuel Arthur, Piyush Choudhary, Piyush Choudhary's Presentation, Scott Hewitson, Tyler Wright, Zach Horn + + +# **Transcript** + +_This editable transcript was computer generated and might contain errors. People can also change the text after it was created._ + +Denis Lelic: Welcome everybody to today's working group meeting for Akash website. I hope you're all doing well. so these meetings happen every week on Thursday. I'm not sure it's What Pacific time is that Tyler? Sorry? + +Tyler Wright: You're fine. It's Eastern Time. 6:30 AM Pacific. + +Denis Lelic: Okay, sounds good. So yeah. Maybe we just kick it off and start with the latest of the updates from piyush and his team they've been working on the website revamp for the last couple of weeks. And basically every week we have a look at the progress they made. Later on, we're answering questions. Make sure there's no blockers and we keep this thing moving and progressing. A H they have anything to share. + +Denis Lelic: Any updates from last week? + +Piyush Choudhary: if I'm sharing with + +Denis Lelic: Thanks. + +Piyush Choudhary: Is my screen visible? + +Piyush Choudhary: So I've dropped the link to see it live on your sleep you can check out this link that have talked in the chat Suite Life. So mostly we are almost done with the foundational structure. We have almost worked on all the pages but after discussions with Dennis today privately, so there are some weeks that will be made the design and also the content that has been decided and also I would ask all the quality numbers to talk to the content of all the pages including development community and about sages. So if you look at the overview of the website We have the home page. We have the blog page. We have getting started page. But this getting started page would be moved to the docs as per this plan. So. + +Piyush Choudhary: So they're talking about it later. I've seen discussions and then we have the token page ecosystem page about page lesson branding page across Community page and lastly development page and it comes to the content right? So we have three About page development page and Akash Community page that contains the general contents. And then lastly we have the dogs which contains the overall structure or guidance tutorials or whatever, So if we look at the development page, right, so this is the development page right on the left hand side in the files. + +Piyush Choudhary: Or the content files that we can change and the content will appear here and on this page, but after seeing the recent designs, so we'll be taking it a little bit only this part will remain here and on this space section will be removed and the content will be expended because after being somebody search as I can see in the designs done by many. if we talk about the content of and so these things + +Piyush Choudhary: So this list of projects it has five columns if we keep the only space section which is designed by us. Then it will make Things look very compressed and it will not be good. So for three pages development community so these three pages are not kind of tutorial but be basically a kind of location the general details about what's happening because the recent development proposal is a job. So we'll be removing this section and will be extending this middle content to the whole page. here incidentally + +Denis Lelic: Yeah, Regarding this menu on the right side. It's called on this page. I think that's something we're just inherited from the previous page and who go template. + +Denis Lelic: So my suggestion would be like to kick it out if in case we don't need it. That's something that's often used in the docs. + +00:05:00 + +Piyush Choudhary: reading this + +Denis Lelic: but If the content is shorter, there's not So Much Information going on and I think there is no need for that and we could expand the main content. and just there's gonna be much more real estate for the main content and the focus of users could be centered around the main content + +Piyush Choudhary: yeah, it shows so. + +Piyush Choudhary: so there are three pages basically in the whole website related to subscribe so that would be Affected by the state one is a development which as you can see one is a community contributions with and when it's about page for this key pages will be affected and this on this space sections will be out and on this space actually will be kept in the docks because it's usually captained at all because we have the bigger contents and on this space section such as the navigate to the full contents, so we will just take it out and well as for the middle text will be expand into the right completely on the left part of the cap as it is that you are seeing on the screen. + +Piyush Choudhary: this is the homepage that you are looking so we have get started page and get started H. We have two pages to plan applications to become a provider. And this all will also be kicked out and customize your account should experience in the product and people start from here this stage. So we implemented only the cloud notes because Council console support has been discontinued from nonverbs. So this is what the get started which looks like but later as for the new designs the get started page will be made to be a part of a cost talks because documentation still have the home page. I sell the direction by Denis. So this on page helps us is the overview of stocks and accordingly. We will Implement our cost documentation as well. + +Piyush Choudhary: And this is all about get started page. I think it has all been discussed in the past. So there's not much but there are some changes that will be made to the homepage. For example. We talk about joined the terminating so these thoughts so we have two options to make this cards Dynamic one. We subscribes to the Twitter API which costs around thousand USD per month and then implement the API endpoints will be displayed in your time. we can just have the markdown file we bear we just have to Keep on updating only three to four details, for example. the content of the text the username and the image so this three things will be + +Piyush Choudhary: updated in the markdown file and we can call it instead of following pictures. Let's say someone tweaked a good thing or let's say we want to show the Weight on this page, right? We can just implemented with text into the modern file into the display here like this as you see or if we want to keep things Dynamic then we can subscribe. + +Piyush Choudhary: So this is the homepage they were saying on the screen and we have the development page. Yeah. + +Tyler Wright: I know there's some hands up but my vote is certainly for the markdown file approach because I don't think those testimonials are. that big of action but I saw that Arthur had his hand up and then Dennis. + +Piyush Choudhary: Okay. + +Emmanuel Arthur: Can you guys hear me? + +Emmanuel Arthur: Yeah, I want to ask why we have so many. Menu items at the now back. Thank you guys do something about it. + +Piyush Choudhary: Yeah, so I will have a chat with the in to minimize the things because I also personally feel like we are having a lot of menu items in the network, but I always get the direction because the pages has been increased the same place. So I always get the direction to keep things. + +Emmanuel Arthur: Maybe a drop down will help. + +00:10:00 + +Piyush Choudhary: I think we can combine you menu items or… + +Emmanuel Arthur: Keep them. + +Piyush Choudhary: cities and can have a drop-down for example. Let's say development community so these three pages are mostly related to each other so we can have a single headline here. And when we go over it the development community and about section drops down. Or we can keep it like this as well. + +Emmanuel Arthur: + +Piyush Choudhary: This. and it's yeah you + +Denis Lelic: Regarding the menu items. Previously, I don't know why maybe it was because of restrictions from that Hugo template we use but I know Greg was avoiding any dropdowns. He wanted Direct. links to the pages so we kind of Kept that idea and… + +Piyush Choudhary: he + +Denis Lelic: just keep on adding new items up there. But if We have a good argument that not working. It's getting clustered and overcrowded. We can always say here's the solution we discussed that here are the problem. And so on and yeah, we can do something about it for sure and regarding a couple of other things piyush mentioned just to provide some. + +Denis Lelic: clarification around it a while ago I have no idea when that happened, but Luna was also part of this calls and I was also a discussion and working group for Akash documentation where we discussed to get started page around in the Akash Docs. but it took some time to + +Denis Lelic: Develop and bring those dogs into the website. that's why we kind of just a get started page. Before we brought docs page into the website, but now since we have piyush here and his team and they're working on to bring the dogs. And the website together, so we have this experience in. One website we could get started page into the Akash Docs. + +Piyush Choudhary: he + +Denis Lelic: and it would provide + +Denis Lelic: one Hub of information. So anyone who's trying to get started will be served with additional items are in the menu bar. on the left or for example, if you click deploy an application you'll be presented with a page with Cloud nose, but again, we can list additional deployment resources at the bottom and it's going to link to the + +Denis Lelic: Same environment meaning it's gonna stay in the doc's page. so that's something I Changed in the last week. of course. We haven't discussed this until now so I just provided some context context around it for Zach Taylor and… + +Piyush Choudhary: You right. + +Denis Lelic: Arthur and emph was just talking this morning. About it. So if you have any comments any suggestions like I Arthur please let us know we can always Change or adapt the direction. + +Denis Lelic: and one additional thing would be + +Tyler Wright: Yeah. + +Denis Lelic: yeah on the homepage. We had couple of tools to get you started. And a couple of templates listed there. But now we have one space available for consoles and to replace the console. So I was just thinking about what kind of tool or app we could place here. Yeah Thai + +Tyler Wright: A couple cool question. I just threw something this is related to the homepage. So I don't want to cut off what you're talking about with the model section, but on the banner. And this is just an open discussion on the banner section. I just threw a link in the chat that an article came out that features Akash Network and in these Banner image shots, it shows basically I think the header Banner for all the various website. I feel compared to some of the other folks in the space. Our better Banner is a little bit text heavy versus having text and some imagery or maybe some background imagery. I just wanted to open that up to discussion very briefly to see if anybody else had any thoughts comments. + +00:15:00 + +Tyler Wright: questions or Should we just keep it as is and… + +Denis Lelic: Are you talking about the hero section with the headline? + +Tyler Wright: just continue to move forward? + +Tyler Wright: Yeah exactly. I'm not saying that headline should go but I wonder if we want to add any sort of accompanying visual assets that maybe show a decentralized network or some more like Hardware or something, that maybe the increases the storytelling or maybe it's not necessary. I just want to open it up to the group for discussion. + +Denis Lelic: Yeah, I'm totally for it. I think this direction we have at the moment is something again. We inherit it from the previous website. So I think everyone was just trying to be respectful of the previous website and the direction and Greg has set ups so Yeah, just with the dropdowns we can say. Here's an idea. And this is why we think it's It was part of this discussion in this working group, and we can also provide examples how other projects + +Denis Lelic: hero section looks like and when it's listed together, for example, in the link you've provided we can say Hey, we're kind of lacking. We need to step up our game. + +Denis Lelic: Yeah, I'm just gonna add that an action item. for the next week that maybe explore what can be done here and Maybe explore what are the trends at the moment what other projects are doing and so on so on? + +Piyush Choudhary: So I think we are in good pets. So I'm just giving our view again. + +Piyush Choudhary: So we have the homepage then we have superstars that are ready for maintain about which contains the general contain contents. Whatever is meeting such a talk, and then we have the tops that will be kind of percent of the tutorials or Royal. And then we have the ecosystem page which has already been done. And the good thing is everything is coming from the maldon files. So even a non-technical person should be able to implement the new projects at the new projects as well. And lastly we have to open page and doesn't page metrics will be patched from the cloud most apis. Just so that in the new design file there is pricings and some guidelines for example + +Denis Lelic: It might be looking at network activity. It's part of the development. + +Piyush Choudhary: we have so yes. + +Denis Lelic: Yeah. there's some data we could pull from cloud nose. especially around network activity + +Piyush Choudhary: so there are three pages that we need data from the cloud nose providers when it's pricing calculators one is analytics. So I asked for the API and points all the way to fetch the data from all these three pages in your time. So in the Discord the chat of cloud mods already. So once that is provided will be able to implement that on the cash website as well. So we will kind of have a details on the cloud most website as it is and we will also have the details on the official website as well. for example, if I go to about section when I click on the pricing? this presentation will be dynamic and you just be able to scroll up down and presentation expected guys, but + +00:20:00 + +Piyush Choudhary: We need to have some kind of detail salts some guidance. Although I found they play but there are some Arrow sign getting I just need a little guidance from the problem or stream on how to catch the real-time data from the + +Denis Lelic: Yeah, there's one thing. + +Denis Lelic: Tyler mentioned a couple of minutes ago. This price needs to be in the navbar. we could move that and just keep it in the photo section. I'm not really sure how much traffic we get on. discussions + +Denis Lelic: because we already have the GitHub button over there. + +Piyush Choudhary: + +Piyush Choudhary: and I think we can remove this from the navbar as well discussions. + +Denis Lelic: But we do mention discussions in the homepage right away. when we have a call to action join the community and then we have a couple of testimonials there above that. + +Piyush Choudhary: when + +Denis Lelic: There's GitHub discussions I think in your button you're just missing discussions inside so + +Piyush Choudhary: If so, yeah, I will demand the discussion with them. + +Denis Lelic: So we could reduce the amount of items in the navbar just kicking out. press + +Tyler Wright: Real quick on the back of the homepage real fast. just I know that I get the steering committee has been moved to next Wednesday as a part of the steering committee. I was hoping that piyush I think you already talked about this is going to give a short demo of the progress for the website. I think everyone will be excited to see ahead of that. I would just love and I know this is low priority right now, but ahead of that meeting. I know that we made some adjustments to the current website to adjust the language from access gpus to reach out. I would love to keep that consistent so that it doesn't become a point of distraction, turn that demo. + +Piyush Choudhary: yeah, sure. Yeah. + +Denis Lelic: Yeah, maybe you just have a look at the sigma file. I've updated it there. + +Piyush Choudhary: if I + +Denis Lelic: So we have deploy now and additional button to reach out. + +Piyush Choudhary: I serve. So yeah,… + +Denis Lelic: yeah. + +Piyush Choudhary: By first number I think I'll be able to update these days as well by keeping out on this way sections. And yeah, I think by first talk no, but they will be more progress and fixes Final Fix so I think there is one item that we can assign to. + +Piyush Choudhary: Arthur if you guys don't know + +Denis Lelic: Which one? + +Piyush Choudhary: this page moving back to the previous version because I think he implemented the code so it will be possible for him to move back this base to the previous version. + +Emmanuel Arthur: up yeah, I would like to work on this and + +Piyush Choudhary: + +Tyler Wright: Share with that at all. So is that one of the open issues that we talked about a couple days ago that we would just want to hand over to? + +Piyush Choudhary: Yes. + +Tyler Wright: Let's see. I know assistant change. The order has happened done. Let me just + +Tyler Wright: Sorry, I'm talking a lot. So we have a couple of issues. I think one's closed but we have This issue that was opened a couple days ago by myself here. She did something that you also want Arthur to handle. the order of the section that get started as well as that main page. + +Piyush Choudhary: So we definition. + +Denis Lelic: It's just reversing the order. So we start with deploying. + +Piyush Choudhary: Yeah, so basically only there is a change on this deployed page so right now is we can see we have two sections apart on soil and… + +Tyler Wright: Yeah. + +Piyush Choudhary: crowd most we just want to keep the clock Mouse on this page as well the directions so I think that instant Denis… + +Tyler Wright: Yeah. + +Piyush Choudhary: then just share the pigma political also for this page and also can just reward the code base and the implement the previous versions as for what it usually + +Tyler Wright: Yeah, I think that's clear I guess additionally. have you already implemented the saw for issue 279 or is that something you also want Arthur to do? + +00:25:00 + +Piyush Choudhary: With chemical means I didn't check they should presentation. + +Tyler Wright: yeah, no problem. + +Piyush Choudhary: That's myself. + +Piyush Choudhary: can you tell what it is related to? Is it opened recently? + +Denis Lelic: It's part of this. + +Tyler Wright: Yes. Then you could… + +Denis Lelic: Yeah, go ahead. + +Piyush Choudhary: I think + +Tyler Wright: if you can move up to page a little bit to get started if you can click on the get started tab piyush. + +Piyush Choudhary: we have + +Tyler Wright: perfect on this page the leftmost tile is access high performance gpus Basically,… + +Piyush Choudhary: yeah. + +Tyler Wright: the direction is we want to switch these tiles. So the deployed application should be the first tile that you see and then the access high performance GPU should be the second power or… + +Piyush Choudhary: Yep. + +Tyler Wright: we could talk about even moving that down the page a little bit depending on what folks here think and we can move become a provider to the second tile and then basically have this tile last my opinion is that deploy an application become a provider be second documentation should be third and then this should be fourth but That's just my thoughts. + +Piyush Choudhary: So I think I can also update it. + +Tyler Wright: Does anyone else have any? + +Piyush Choudhary: It's not a big deal, but Yeah, I can do it now. It's + +Tyler Wright: Okay, Zach Dennis. So you guys have any preference on the order of operations for these four tiles? + +Denis Lelic: Nope, sounds good to me. + +Zach Horn: Yeah, strong preference. I would say having deployed the first makes a lot of sense, but whatever needs to be done. + +Piyush Choudhary: so yeah,… + +Tyler Wright: Cool, how can we do? + +Piyush Choudhary: so I'm just rewarding the things for the deployment applications by just keeping the cloud notes and I will just Change the order of the tiles under get started on the official domain right now and we'll continue working on the new website. + +Tyler Wright: excellent + +Denis Lelic: There's another item. I wanted to just quickly discuss piyush. If you could please just go to the Akash Web 2.0 figma file. + +Piyush Choudhary: Yes, I want. + +Denis Lelic: And if you go to the support page, it's bottom left. + +Denis Lelic: yeah, I was just thinking about if we could implement. In the future, of course some sort of AI assistant so we could start with a question and it kind of provides different resources. + +Denis Lelic: and below that we could just keep it simple direct users to GitHub issues Discord or discussions. But in general it would serve some sort of I don't know search engine / AI assistant. + +Piyush Choudhary: just + +Piyush Choudhary: yeah, I think it's definitely a good idea. We can integrate AI system and do this page where users will be able to ask any type of questions related to a cost also real time happenings as well integrated. We can also have a train version where the AI agent will be able to answer any type of technical proportions all the issues I think we already did this kind of thing with the Equus AI as well. I think if + +Piyush Choudhary: there's some issues. + +Piyush Choudhary: presentation So I think we already made it this kind of stuff where they got Tuesday is so we can just click that up to be integrated with. + +Piyush Choudhary: presentation of selfish + +Denis Lelic: what about I think we just mentioned it, but we haven't really discussed Akash console on the home page where we have that tile Dedicated for Akash console… + +Piyush Choudhary: he + +Denis Lelic: but now since we're like sun setting it we could replace that with some different tool. + +00:30:00 + +Denis Lelic: I think it's best if you share the figment file. + +Denis Lelic: and a home page right here. + +Denis Lelic: Yeah, so we have a couple of tools listed here. + +Piyush Choudhary: e + +Denis Lelic: The main are Cloud nose and Prater. but we have additional space to Serve some others. Otherwise we could just remove them. And showcase only two. Yeah Zach. + +Zach Horn: I'm just gonna throw out there that I would like to surface xdxl on Akash somewhere on the new website the thing that it does really well that it's already proving out is that it's a touch point that lets people like experience. What compute on Akash feels you can put in a prompt and it returns a finished image and four seconds. So we have all these apps that people can deploy which is obviously we should keep those top of mind and focused on the way they are but I don't know what this section would look like it could + +Zach Horn: I could see it integrated into what you're looking at right now Denis or maybe in its own section that feels a little bit more. This would not be the copy but something like demos, that being the vibe of it where you come to the website. It's like let me just try it out real quick, and you can go to stxl on You can put in a prompt see the images being generated the other thing that it does. Excuse me. Is it serves now as a call to action for some of the things we're doing with Akasha Mel and tailored deployments with gpus the way it's set up with a call to action. So just a little bit, but I could see it either integrated into the section you're looking at now or in its own section that serves as easy to experience demo that then is also a call to action to reach out to us. an thoughts on that? + +Denis Lelic: Yeah. Yeah,… + +Tyler Wright: plus 1000 + +Denis Lelic: I'm just actually putting something together It could be kind of fairly simple. + +Zach Horn: Yeah. + +Zach Horn: mmm + +Denis Lelic: We could start what's possible and we just showcase. couple of I don't know it as the Excel confused, whatever we think. + +Zach Horn: definitely + +Denis Lelic: and that would be like what's possible? For now, I'll just put any just to have a reminder. What's this section about and + +Zach Horn: Yeah. + +Tyler Wright: Zach do you see it I'm just a simple call to action like being built right now and you click on it and you go directly to sdxl or do you see it goes to a case study page to show how Akash is being leveraged and then it goes sdxl. Do you think it's like you prefer to be one click so people can use right away, or do you want to have some supplemental information? + +Zach Horn: I think yeah, if you're asking me for my Grand Vision, here's the Grand Vision is That it has a section the first step like… + +Piyush Choudhary: + +Zach Horn: if we're doing order of operations, I would say the easiest to just have a direct right to xdx on This is some true Alpha, but if we're thinking down the line, I would say I would see it as a section on the website that surfaces the tool directly but then also has supporting information. So it's like case studies on how it was developed, it could be guides and content on how to prompt or how to use it. It could be, other adjacent content around how to develop on Akash more broadly and then a direct CTA on the website to reach out if you want to do something similar you're looking to deploy custom models or all that. That's obviously very down the line and there's a huge amount of work that we're doing right now. So I'd say the easiest first step is just link right to it people can click through and kind of poke around and figure it out for themselves. But if we were thinking down the line definitely a more built-out section that includes supporting content and possibly a direct call to action. + +Tyler Wright: I love that. Yeah, I mean I think sdxl is the best case scenario. I would love to show I think this in kind of over the ecosystem page too, but website's deployed on akash, so the people can To your point just click on things and back. this is actually leveraging the Akash Network right now and… + +Zach Horn: Yeah. + +Tyler Wright: just making mess around with the functionality, but I think sdxl and any other of those kind of AI. + +Tyler Wright: Models are apps that you're working on would be great. I was actually just messing around with these a couple days ago And it's like in that same vein of it being a open source tool for another project. + +00:35:00 + +Zach Horn: Yeah, definitely. I think As DXL is definitely a good one because it's running right now and it's performing and getting great usage come to you as another good one and that's potentially coming soon. definitely stay tuned for that. I'll add more info on that the next week or two, but What the dream is that eventually someone would come to the website they click through to these things. They get a sense of what's possible. but really what we want That at They see it deployed. there's a nice keyword tie-in with a 100s and then they go. I want to run XD Excel. But really what I want to do is run my own custom model, and then they click through on that call to action end up talking to somebody and we can get them deployed. + +Piyush Choudhary: look up just + +Zach Horn: With their own custom model. So yeah. Just reading your comment. Yeah, definitely. + +Piyush Choudhary: and I also think Akash can also invest established in the Strategic partnership with the AI startups or even if some community members are building some AI related startups are fast and consider supporting them in turning them into a startup. So this can also have a great positive impact from the Holocaust system. even the investor will be able to see These are the startups that are in one Akash officially and Akash can have a strategic partnership with such kind of things instead of just keeping them limited to just a simple or just projects. So yeah, that's not + +Zach Horn: Yeah, I love any touch point where we're showcasing other projects being built or leveraging Akash computer. I think that's always really strong for us and it's starting to get picked up by the mainstream we saw yeah, I'm sure you guys saw we had that feature in some before yesterday. But that was the focus of that piece is read the reporter went out and interviewed all these projects either Thumper and Foundry who are leveraging and caution various ways. And that was almost the focus of the story which I think is always very strong because it just shows people like choosing Akash from an entire Market of options. + +Tyler Wright: Yeah, I love that. I think the question I get asked the most I'm sure this is for everybody is how can I use Akash and + +Tyler Wright: How much does it cost how much can I make by providing and I think that this new website revamp is going to do a much better job of answering both of those questions. So + +Zach Horn: Yeah, I'll just jump in and say because you were showing it earlier. The pricing page views that you were showing that's I mean really amazing. I mean that's like something we needed forever. So I'm really excited to see that get built especially with real-time data. the ties Point like Yeah. + +Tyler Wright: Yeah, I'm gonna connect. website + +Zach Horn: and nowhere is that's just the thing that People ask about all the time. how much does it cost for XYZ amount of compute. And then also if you're a provider how much can I make if I provide, x y z resources + +Denis Lelic: Yeah, one thing here. We have to check with. Cloud nose but I try to ideate something for example what user would want but they don't want to go through all of this Hassle and Click and everything and set up these parameters and So what we could do is just have packages ready. So basic general purpose GPU optimized memory optimized so you can just click through and What would happen in the background? We would actually request bids and… + +Piyush Choudhary: he + +Denis Lelic: below this. We would somehow have to display bids. + +Denis Lelic: maybe we could even pull that from console. But that's something we just have to To see if it's possible. + +Tyler Wright: I think this is gonna be a team effort to be honest is something I would say that cloud most I know that their pricing tool is great. But it is incomplete. and I think cute Scott hewitson who's been just voying on. This call is going to be called into action for us to actually understand how some of these calculations are being derived and make sure that this makes sense, because one thing that we've seen is especially the provider side people have used Cloud those people have used a tool by a member of the community people use pray tour and they use those three different tools and put in the same information. They're going to get three separate answers that are not anywhere. + +00:40:00 + +Tyler Wright: The don't even have the same methodology. So I think we need to work with Cloud most but also work with members in the core team. To figure out the calculation first and then we can optimize it. + +Scott Hewitson: Yeah, I'm just on that point. I mean it's kind of like, if you ask hey how much money can I make having an Airbnb like being a host on Airbnb? it depends on the market depends on how big it is depends on so there is no one size fits all it's an Open Marketplace. Yeah, I don't know. I mean I think people have a hard time understanding that when it's like you go to other protocols and it's like okay, I put my minor up and I'm getting that fixed amount because that's what it is. It's a Marketplace. So that's all I gotta say. + +Tyler Wright: yeah, I do I get what you're saying for sure, but there should be a little bit of a standardization or to denis' point. I think that's Scott's Caruthers of the part of a support tool. He built a while back had some sort of replication tool. So it was simulate deployments and see what kind of pricing it would get back and maybe again we can base it upon a real-time pricing, but I think everybody's a good point. I just want to make sure that we just take the time to really hone in on how pricing is being calculated. + +Piyush Choudhary: Really? + +Zach Horn: That's it. I'll just jump in quickly to say that if there's a way that we can pull deployment pricing in some way that we're just showcasing it on the website. that would be great. Because to Huey's Point. Yeah, there's unlimited optionality that influences what the pricing might be. But if you think about the Airbnb example the way you would get a sense of what you could earn with an airbnbs. You probably look for comparables. So if we could figure out a way to Showcase that of let's just choose Nvidia 100. the dream would be that you go to the website. Excuse me. I'm on week four of this cold. So I'm still getting over a cough, but the + +Zach Horn: You go to the website you could filter in some way by a 100s and then see what the current pricing on the network is that would be the dream. I mean that's quite complicated because you'd have to pull live pricing or simulate a bit to ties point on what Scott Carothers was working on but If there's a way to do that, that would be extremely valuable in my opinion. + +Scott Hewitson: Plus 50 to that. + +Piyush Choudhary: So yeah, I think we have three. Dynamic things that you can Implement on the official website and it's the price compare when he's Akash and when it's a providers. so I just want all the 14 numbers to provide us with the + +Piyush Choudhary: apis and points all the directions all the guidance to pets all this details properly and from where to fetch 30 days as soon as we get the UK and points or the proper guidance from the sources where we can get the data which It will be much easier forest and return the official website that you're saying right now you're staying + +Tyler Wright: Okay, that may take a week or so maybe even longer. I guess the different point if we talk about even provider because I just saw you show provider screen. One thing that we're still trying to find tune is. + +Tyler Wright: Pray tour and cloudmose have different statistics on provider. I know that they're taking him a different cadences and over different periods is too, but I just want to make sure That you had the most up-to-date data and then hopefully it could standardize it across those Partners so that everybody's kind of feeding the same data whether it's on Akash Network Cloud, no sort. + +Piyush Choudhary: So this is the tool that we made for the cost of account. + +Tyler Wright: Play tour. + +00:45:00 + +Piyush Choudhary: So I think we can pick this To have an EA assistant on the support page. So we're working on it very soon and also be proposed this Akash deploy tool. To the discussions where you just have to put in the GitHub username guitar producer and password username Docker people stadium and just click on generator still want this tool does this it just pulls out the code created open image push the docker image The Hub here the perfectness required. We all have the option to say my budget is I need this in this operating system. and in just one UI you can have Looks like they still so it's in early stage that we've submitted in that con. so + +Piyush Choudhary: yeah, this area system can be customized integrated on the support page of the Cross. So I will look into it. + +Tyler Wright: excellent All… + +Denis Lelic: Sounds good. + +Tyler Wright: Now we started a little bit late, but we're coming up on time. Is there anything else Dennis that you wanted to cover Zach or anything else that anybody else want to talk about before? We drop off. + +Denis Lelic: No for me. Some action items for next week. I want to explore the Showcase part Zach just having a showcase and case studies and so on. I'm just wondering is that part of the ecosystem or it's a thing on its own? the next action item. Would be homepage and the hero section Tyler mentioned. + +Denis Lelic: I'm just wondering what can I do to help around the pricing page? Yeah, it's Tyler mentioned. We probably have to involve Max's Scott. + +Denis Lelic: It's a tricky one, but I'll keep it in my mind. So. + +Denis Lelic: Yeah. + +Tyler Wright: My talk is either have a working group session that's specifically about pricing or wait till this again analytics meeting and talk about it there. But again, I want to get this done in a week to 10 days to try to figure out because this is a lingering problem and I think now we have A reason to talk about it a little bit more specifically and no figure it out. + +Denis Lelic: cool + +Emmanuel Arthur: Hey page, so. Are you going to work on the issue that Tyler has raised on the top as well as the Detroit? + +Piyush Choudhary: Yeah. + +Piyush Choudhary: so yeah, what you can do is you can work on this Detroit page, So this deployed page. Needs to be worked back to just proudmose. And of course Council needs to be moved. If you can complete this by tomorrow, then you can also just change the tiles it will. This week lines support or else if not tomorrow, then I will just change it within tomorrow. + +Emmanuel Arthur: Okay. + +Denis Lelic: Yeah, me and Arthur actually talked very shortly about this page that we're seeing now. Unfortunately, he doesn't have access to the code. + +Denis Lelic: He has done previously where we had educated page for each of these products also in cloudmouse. So Arthur mentioned he would have to build it again from scratch just for clone of + +Emmanuel Arthur: Yes, yes regarding that page. What I did was when I was implemented this page arm. I deleted everything then rewrite the quote again. And when you check the page, you could see that at the right side the new design that Denis had time for the cloud most Beach you could see that there will be some slider. Implementing that would be a huge challenge. So in fact of the time giving I think if I'm able to work on it. It's going to be like maybe tomorrow evening 8pm you and make it PR on it. Yeah, because I need to make sure that that's like that will fit on all screens. Yeah. + +Piyush Choudhary: Yeah, No. + +Denis Lelic: If the slider is a big issue for you, maybe we can just focus on. removing console and + +00:50:00 + +Denis Lelic: just having the cloud nose page there and later on in an extra PR you could create the slider if you wish. + +Emmanuel Arthur: Okay. + +Denis Lelic: You mean the gallery slider, right? + +Emmanuel Arthur: Yes, yes. Yes. + +Denis Lelic: Okay. + +Denis Lelic: One sec. + +Emmanuel Arthur: But in the teamstone needed to get it done I can work on it, but it's going to take a couple of hours to face it but I got still work on it though. + +Tyler Wright: Thank you I know Arthur this is a higher priority because console has been deprecated. We just want to make sure that people are going to Cloud most and not to try to use console which is not optimized from a user experience standpoint right now. + +Emmanuel Arthur: + +Denis Lelic: Okay, anything else we should mention before we wrap it up? + +Piyush Choudhary: So I have one I was like,… + +Tyler Wright: I think Im + +Piyush Choudhary: I know we call ten days I think will be in good position to make this new website. what should they steering committee meeting? I'll just make the changes. accordingly within this Indus 10 days and then we can make the new website officially provides I think and then with pricing things takes time, we can still make the website live and If there endpoints all the ways to punch the real-time data, we can Implement that later on as well. + +Denis Lelic: Sounds good. + +Tyler Wright: That sounds good to me. we'll talk a little bit next week. + +Piyush Choudhary: or else yeah. + +Tyler Wright: We'll talk a little bit next week after the steering committee about next steps and taking a live strategy, just want to make sure all the links are working. We do have to think about current links that Zach has been putting on Twitter and making sure that we're not just setting ourselves up to have a bunch of broken links. So I think there's a little bit of leg work. We at least have to think about my strategy standpoint, but we'll focus on that next week. + +Piyush Choudhary: It shows we can always give a time for the final touches. but I'll try to make sure that the possible we have the pricing and points Etc. So it will look much better. We can implement this. + +Denis Lelic: cool + +Piyush Choudhary: So I think the direction is pretty solid so far. We are directions that can someone base. cost as well as smooth and we will continue doing the same and hopefully if not 10 days within next to the weeks, the new website will be like we show you on the official + +Tyler Wright: amazing + +Piyush Choudhary: Also I forgot you guys have time. + +Denis Lelic: our piyush if anyone else has Time they can stay in this call. Otherwise if have Did you want to share something else? + +Piyush Choudhary: If so, I just want to say that I got the access to the new docs. But we have to implement a dog space from scratch because the new design has been Contributes including the getting started page, but there is a content for doing the docs. So I just want you guys to take a look at the content that it's been done in the dark's new docs orders or code base. So we're doing cementing that content. So if it is incomplete, just We will not do that. It's complete. just inform us so we can Implement that content as it is and + +Denis Lelic: Okay, cool. + +Tyler Wright: Right. Yeah piyush. Can you throw that message and the Akash website working group channel, so I'll just make sure I'm clear because I might want to make sure that Scott is included on that conversation. So just throw anything related to the docs in working group of class website and then we can talk about async. + +Piyush Choudhary: Sure, always. + +Tyler Wright: All right, if there's nothing else and again, we can just drop off here. Some of us will be in contact with you shortly. + +Meeting ended after 00:55:51 👋 + + + 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 👋 + diff --git a/wg-akash-website/meetings/017-2023-11-16.md b/wg-akash-website/meetings/017-2023-11-16.md new file mode 100644 index 00000000..82c91fe6 --- /dev/null +++ b/wg-akash-website/meetings/017-2023-11-16.md @@ -0,0 +1,549 @@ +# Akash Network - Akash Website Working Group (WG) - Meeting #17 + + +## Agenda +- Progress Update on Akash Website Revamp +- Discussions on Docs 2.0 integartion + + +## Meeting Details +- Date: Thursday, November 16, 2023 +- Time: 6:30 AM PT (Pacific Time) +- [Recording](https://yn2ux6akmd2wog533saw3cl66agmv37r364jgx3n3u5envp6m2iq.arweave.net/w3VL-Apg9Wcbu9yBbYl-8AzK7_HfuJNfbd06RtX-ZpE) +- [Transcript](#Transcript) + + +## Participants +- Alani Kuye +- Denis Lelic +- Emmanuel Arthur +- George Pro +- Massv +- Tyler Wright +- Zach Horn + + +## Meeting Notes + + +### Previous Discussion Highlights: + + +##### Denis Lelic: +- Discussion on the structure of the navbar for the docs page and Akash documentation. +- Conversation about stats pricing for the website. +- Deliberation on implementing a calendar on the website for community members to have an overview of all meetings. + + +### Akash Website Revamp Progress: + +##### Denis Lelic: +- Mentioned that the focus for the last couple of weeks has been on putting everything together. +- Noted that Piyush and his team, funded through a governance proposal, are actively working on the revamp. +- Emphasized that the website is functional, with pages in place, and is working smoothly. +- Denis shared an update from Piyush, mentioning his team's focus on bringing documentation to the website. +- Stated that the website is operational, and UI refinements are the next steps. +- Encouraged the group to check the Discord chat for Piyush's detailed update. +- Denis Lelic provided an estimated timeline of three weeks for the ongoing work, adding an extra week for potential adjustments. + +##### Tyler Wright +- Mentioned that feedback from the community, especially from the Akash website Discord Channel, is being considered for continued edits. +- Tyler emphasized the close proximity of the website revamp to completion. +- Indicated that Zach wanted to discuss the timing of the website launch, considering the marketing and content aspects. +- Noted that edits will continue even after the website goes live, with ongoing testing and feedback incorporation. +- Tyler raised the issue of spacing and formatting changes due to the revamp, leading to a discussion on how to handle marketing and content placement. +- Mentioned the need to decide whether to add new content to the current website or wait for the revamped version to showcase it. +- Tyler suggested setting a launch date around December 15th, approximately three to four weeks from the current date. +- Proposed considering a transition time in the middle of the night to minimize disruption. +- Agreed to further discuss the launch date and transition plan in the next meeting with Piyush's input. + +##### Zach Horn +- Zach Horn emphasized the priority of addressing documentation. +- Mentioned the ongoing work on a case study involving SDXL on Akash, which includes code sections affecting the website's formatting. +- Expressed a desire to briefly touch on timelines for better planning. +- Zach acknowledged the timeline and mentioned that the case study might be ready before the general website completion. + + +### Discussions on Docs Restructuring +- Tyler addressed the current state of the [Docs page](https://docs.akash.network/) on akash.network. +- Tyler mentioned plans for overhauling the page with more visually appealing tiles and emphasized the need for an improved structure +- Tyler Highlighted the discussion around restructuring the sidebar menu for improved navigation. +- Shared the [updated structure](https://github.com/akash-network/community/blob/main/sig-documentation/documentation-structure.md) implemented through the work of the Docs 2.0 working group and Sig documentation. +- Emphasized the goal of making the structure more accessible and developer-friendly. +- Noted that the restructuring involves organizing existing documentation, not creating new content. + + +### Clarification on Missing Categories in Docs Restructuring: +- Denis Lelic raised concerns about missing categories in the Docs restructuring, specifically mentioning the absence of "Testnets" and "Integrations." +- Tyler Wright clarified that the "Testnets" category will only appear when an active testnet is available. The goal is to prevent confusion and inquiries during periods when a testnet is not active. +- Tyler addressed the concern about "Integrations" being left out, indicating that certain categories, like "Experimental," may encompass integrations in the future. +- Tyler mentioned that the addition of a Sandbox category is planned for those interested in testing deployments. +- Tyler Wright clarified that information about setting up wallets and obtaining developer tokens will be included under the "Getting Started" section. Mentioned that the details will fall under the "Your First Deployment" and "Getting Started" sections, making it easier for users. +- Tyler highlighted the user-friendly approach to navigation, with the intention of providing clear pathways for both deploying applications and becoming a provider. + +### Documentation Transfer Process +- Tyler Wright expressed the hope that the documentation transfer process does not have to be perfect initially. +- Emphasized the plan to transfer documentation with the understanding that optimization can take place in the following week. +- Tyler Highlighted the upcoming SIG Documentation meeting on November 28th. +- Suggested including an agenda item to involve the working group for the Akash website in the SIG Documentation meeting. +- Discussed the potential for optimizing documentation during the SIG Documentation meeting with the input of SIG Documentation members. + +### Plans for Case Studies +- Denis raised a question for Zach regarding the format and placement of case studies on the website. +- Denis inquired about the possibility of having a separate section for case studies, focusing on projects deployed on Akash, including sdxl. +- Zach emphasized the need for three to five comprehensive case studies before considering a dedicated page. +- Zach suggested that a dedicated page would differentiate case studies from blog content, catering to those seeking in-depth understanding of various implementations. +- Zach recommended prioritizing the blog for now until a sufficient number of case studies are produced. + +#### Case Study Section in Akash Ecosystem Page (Website 2.0) +- Denis Lelic proposed the idea of having a dedicated case study section on the Akash ecosystem page. +- Denis suggested connecting case studies and projects deployed on Akash, making case studies clickable for in-depth information. +- Zach agreed with the idea, emphasizing the importance of making the case studies part of the website for seamless navigation. + +### Planning Session for Next Week: + +##### Tyler Wright +- Tyler mentioned the upcoming planning session for next Thursday, even though it is an American holiday. +- The focus will be on planning for the next couple of weeks and months, addressing various aspects of the website. +- Tyler expressed the goal of transferring the docs over by next week, even in a rough state. +- There are questions about where certain content should go, and these will be discussed further. +- The plan is to present the website to the Sig Documentation group on November 28th for additional feedback on the structure. +- After the Sig Documentation meeting, the intention is to share the website with Insiders in the community to gather feedback. +- Tyler highlighted the need for an all-hands week starting from December 4th to focus on optimizing content and filling in any gaps. +- The goal is to define timelines and milestone goals for the website launch, potentially around the week of December 15th. +- There is a focus on reviewing and updating content on the website, addressing any missing or outdated information. +- Tyler suggested creating bounties for specific content updates or optimizations that can be delegated. + + +## Other Matters Discussed + +#### Landing Pages for Specific Campaigns +- Denis proposed the idea of creating dedicated landing pages for different campaigns, focusing on specific target groups. +- Zach expressed interest in the concept but emphasized the need for a solid understanding of the target groups before proceeding. +- Denis suggested the idea of having a universal template for landing pages, with interchangeable graphic content. + +#### Discussion on Visuals for the Hero Section +- George Pro inquired about the decision regarding the visuals for the hero section, noting the absence of visuals in the latest version shared by Piyush. +- Denis Lelic referenced previous discussions about considering more visuals and presented a new concept for the hero section. +- Denis Lelic shared a new hero section concept, featuring an interactive element where buttons pop up on hovering over a specific area. +- Zach Horn expressed enthusiasm for the aesthetic appeal of the interactive elements. +- Raised a concern about potential page load speed impact and suggested discussing implementation details with Piyush. +- Acknowledged the need to balance aesthetics and functionality in the implementation of interactive elements. + +#### Request for Access to Code Base +- Arthur expressed interest in reviewing the code base for the new website to provide feedback. +- Tyler alerted Arthur to post a message in the website working group, asking for access to the code base from Piyush. +- Arthur mentioned that he plans to share feedback once the code is completed and the UI is finalized. +- Tyler emphasized the importance of early access for Arthur to facilitate familiarization with the new website. + + +## Action Items +- Group to consider launching the revamped website around December 15th, with a discussion on the transition plan in the next meeting. +- Tyler to include an agenda item in the upcoming SIG Documentation meeting to involve the Akash website working group in optimizing the documentation. +- Denis to explore the integration of a dedicated case study section on the Akash ecosystem page(Website 2.0) +- Denis to conduct research and propose a layout for the landing page template(Specific Campaigns) +- Deenis to discuss the new hero section concept with Piyush to explore implementation possibilities and considerations + + +# **Transcript** + +_This editable transcript was computer generated and might contain errors. People can also change the text after it was created._ + +Tyler Wright: excellent + +Denis Lelic: For the Akash website we meet on our weekly basis where we discuss everything website related. For the last couple of weeks we've been working on. Akash website revamp There was a Community member gold Panther on this court, but his name is piyush and he was granted. some funds through the governance proposal and he and his team are working on the river and I'm just gonna share the recent update. Appears provided on Discord so you can reach it here in the chat section. if we just go through it quickly. They're mostly working on. + +Denis Lelic: Putting everything together. I know he appear said this and the next week, they're gonna focus on bringing dogs to the website, but we already see the website is functional. So they'll have to do some UI refinements but all of the pages seems to be there and everything is working quite fast smoothly. + +Denis Lelic: I see Tyler you're sharing the screen. I thought I was. one thing from a previous discussion. Where I believe had a productive meeting we talked about. Many different things I'm just gonna go through them. really quickly + +Denis Lelic: So we talked about dogs. There was a discussion around how to structure the navbar. Of the darkspage and the whole Akash documentation. There was a discussion around stats pricing. And of course there was a discussion around community and how to implement calendar where users could have a good overview of all the meetings that are happening. + +Denis Lelic: Today or in the near future. So basically just have a good overview of all the working group and seek meetings. and for today's agenda I was just thinking about Discussing docs a little bit further last time I believe at least from my perspective all of the information was not there. So I think it brought some. + +Denis Lelic: I lost the word confusion for peers and his team like how to the menu bar and how to divide the subcategories or even subcategories and how to + +Denis Lelic: group all of the content so they can work + +Denis Lelic: with markdown files and everything. try I know you have the most information. regarding the docs So I was just thinking. About the structure you provided if you just see if I have it somewhere here. let's respond. + +Denis Lelic: There maybe have it somewhere. Close to you. + +Tyler Wright: Yeah, yeah. + +Denis Lelic: I'm talking about new menu structure. and the GitHub link you've provided. + +Tyler Wright: Absolutely, I'll pull that up right now. Thank you Denis. I know that Zach so we certainly want to talk about documentation and action item. I think Zach also wants to talk about just general timing. I know piyush is not here right now today. but with the rest of this group, I think this revamp is very close to being done with obviously the docs being an outstanding item and then continued testing. I think there's members of The Insider community and other members of the general Akash community that have obviously everybody had access to this link. And so some people have been giving feedback inside of the working group Akash website Discord Channel. I think that that be back is being taken in consideration with continued edits. So I know that there will be some + +00:05:00 + +Tyler Wright: edits and continue edits even after the website is live, but I believe Zach wants to talk about timing because I know there's a number of things on the marketing and content side that we have to talk about whether we're going to be adding it to the current website or if we'll just wait for the website revamp to Showcase some of this content because I know that there is a spacing issues and the way that things are is being formatted is changing. So we'll talk about and… + +Zach Horn: Yeah. I'm all good. + +Tyler Wright: then I think we'll go into the conversation. Go ahead Zach's already cut you off. + +Zach Horn: Yeah docs can take priority. I think just to kick off the call. But yes, there are a few things. In the pipeline the main one being this case study that we have in the works for xdxl on Akash, and there's lots of code sections as part of that and that's gonna change how we format it for the website. If it's going on the the new version. It's a part of my goal for today if we could just touch briefly on timelines just so I can get a sense of where this thing is going to be published. But happy to start with docs just to kick it off. + +Denis Lelic: Yeah from my understanding and based on the information peers provided. I think we have three weeks. I would add a week to that because there's always some. stuff that happens so + +Denis Lelic: if that is that working for you? + +Zach Horn: I think so. I mean obviously it's going to be whatever it's going to be and that's fine. The case study probably will be out before that. So then that's okay. I think it just will have to think through how we're going to migrate from the current A question for you, and we don't have to linger on this. Is there a world in which? I answer my own question. What I was gonna say is our world where the current blog gets published and we start to migrate before the entire website's live, but they're using different providers. So just disregard that. + +Zach Horn: So we're about a month out at this point. + +Tyler Wright: yeah, with testing that I think that's fair. I think three weeks is what Peter's targeting. I think an extra week as a buffer would be great at Maybe something we can start to think about this week but really start to or maybe finalize next week and Pierce is back is and launch date that we can work towards, if we're about three or four weeks out from today. I think that puts it around December 15th. and so we can start to put a date on the calendar or maybe we do the transition in the middle the night at a time when they're less people accessing the website and then we can figure out just announcements after that. So maybe that could be an agenda item + +Tyler Wright: that we further discussed next week with Piers when he's back. But again, if anybody has an ideas if there's any particular events happening in the ecosystem, that we can latch on to or there's an idea when we can kind of showcase this website because again, I think there's a large number of ux and provements. and just should be a better and more inviting experience for all those + +Denis Lelic: Yeah, one question for Zach. + +Tyler Wright: cool + +Denis Lelic: How did you imagine the case Is that a separate thing, just having something similar to the blog and the blog posts, but we could focus it more on just some case studies. So they would probably be like a page called case studies. And we list all of this case studies there. So I mean, maybe we can just I don't know focus on some of the projects that are maybe deployed on they're having front end. running on Akash or something else like validator but of course sdxl as well. + +Zach Horn: Yeah, the dream would be something closer to that. The issue is that we have a bit of a bottleneck on producing case studies at the moment the bottleneck being me. so what I think my plan is that We get xdxl on Akash that case study out the door. We see how that performs and we see what the reach of it is and who's resonating with it? And then we go down the road of deciding if we want to do more case studies and what the topics of those could be and then I would say we should get to let me hedge that a little bit if we go down the road of producing more case studies. I think we need to get somewhere into the range of three to five really built out. these are Somewhere in the range of 3,000 to 5,000 words. So they're quite involved. + +00:10:00 + +Zach Horn: Gets a three to five of those and then start to think about a dedicated page for them. I agree with you that I think a page on the website. if we get to that point would be great just because it differentiates from the blog a little bit and obviously nothing against blog content, but case studies are just a little more focused and built out and they're probably targeted a bit more towards people that want, top to bottom understandings of how different implementations work and deployments and all that. so I would say we prioritize thinking about that for the minute just until we get one to three of these out the door and then if we continue going down the road and get the three to five then maybe we start considering a page, but I would say they stay on the blog for now. just a quick question Who has ever sharing a screen Ty could you go to the blog? I'm a new website really quickly. + +Zach Horn: If you scroll down a little bit and it may be on the individual post page. No, it's not scroll back up. + +Zach Horn: a question for you, Denis, so If we're gonna have this new blog be, a One-Stop shop for case studies and posts and updates and all that. I see the filtering that we have here. Do you have any thoughts around how we can direct people to different content verticals above and beyond just a list of filters? That's been the one thing that I've been thinking about a little bit. + +Denis Lelic: I'm not sure. I understand What's the way to better? shape these categories + +Zach Horn: a good example Yeah, Let me grab a link really quickly. Bear with me. + +Tyler Wright: Sorry, + +Tyler Wright: Maybe + +Zach Horn: So I guess I won't name the name because they're competitor adjacent. But there are other Cloud platforms out there that they split their content out into categories. They're not really filtering posts. It's more like you drop down a section from the navigation and then you can see different high level categories of posts. I know that changes the structure quite a bit and we consider that at all for this website or is that out of scope? + +Denis Lelic: not something I've considered but maybe I'll just make a note and I'll ask ierce. What are the possibilities there? + +Zach Horn: Yeah. + +Tyler Wright: that makes sense to me. I'm gonna go back to the docs page real fast because I know that's what Denis Who has had some questions about can everyone see the current docs page as it lives today and akasha Network. cool So we all know that this area right here will be overhaul. I think it'll have more tiles. I don't be able to be a little bit more visually appealing. But I believe the area of discussion is around this sidebar menu right here. The structure of this is fairly straightforward, but I believe again through the work of the working group for docs 2.0 and Sig documentation. The new structure has been implemented and I'll share right here. It's in. + +Tyler Wright: GitHub as well looks a little bit differently. So I think it's a little bit easier for developers to digest almond fine content. So one of the things that developers have had an issue within the past is actually setting up their environment, especially if they're trying to build tooling on top of So again, it's just about restructuring some of this documentation which lives all this documentation. None of the documentation is new documentation Luna and his team They just took existing documentation that was stored other places. + +00:15:00 + +Tyler Wright: and they just restructured it and read and moved some of it so that it was easier, a lot of the documentation is in other resources, and it's just been moved to specific categories. That you can find again in this spec for what the structure should look like for the sidebar. + +Denis Lelic: Yeah. Yeah. + +Tyler Wright: Then did you have specific question you want to talk about and… + +Denis Lelic: I do. + +Tyler Wright: we can go. + +Denis Lelic: I was just comparing this structure to the existing dark space we have and I see there were some categories left out. For example, let me just pull it up. There was no test Nets anymore. + +Denis Lelic: Is that something? That the working group decided or Sig decided to leave out. + +Tyler Wright: I believe the test Nets will only show up when there is a test net. I think what's been a issue in the past is because it's consistently there people are always asking and disco and Discord. Hey what's going on with the test net even though it's only for specific periods, and they don't read any further. They just see testing the category. I think one thing that's going to be added here that I don't see is a Sandbox. So because of sandbox is now fully functional inside the network features or excuse me inside one of the category. I'm not really sure which category quite yet. There will be a quick link if to those that want to use the sandbox and test out deployments on the network. + +Tyler Wright: But in terms of testnet, that's something that's only going to be available. So on the current documentation, you can see an experimental section the idea in the future is that things that are an experimental will get moved into their own category. Sometimes testnet But again, those categories and sections will be made and then hidden at the test that is over to avoid confusion. + +Denis Lelic: No. I was just wondering about a couple of section being left out. So I know it's like these were planned decisions and the other one would be Integrations. and one more + +Denis Lelic: the basic stuff token and wallets like how to install a wall and how to get developer tokens and stuff like that. Is that something that's still part of the Restructured menu, or is it left out as well? I mean users can get that information somewhere else. they could go to the Kepler or leap or whatever. + +Tyler Wright: Yeah, no, so that will fall under your first deployment and not getting started section. It'll have all the information about setting up your sleep wallet. I think metamask is coming soon it'll have various drop down depending on which path you want to go and then steps all that Depending on which path you go, but as I understand that's all going to fall under that getting started section. + +Denis Lelic: Okay, cool. + +Denis Lelic: And there's no deployment section anymore. There's just basically you have to go to it through your first deployment and you're going to find out. All the information you need there. + +Tyler Wright: Yeah, And there's a deployment section inside the concepts which will kind of showcase. How the network works, and then we'll give you some ins and outs on deploying, give you some routes on how to get to clubhouse and CLI. I think that documentation already exists on the current website. but again, we're trying to traffic people through. One like this getting started section and people understand that their first appointment. We're trying to do that under five minutes and then + +Tyler Wright: Hopefully the tiles will be also a great indicator, as discussed with the new docs where people are trying to deploy should be a couple of clicks from the home page to Cloud most which will be the preferred deployment tool. And then if you're trying to become a provider should be the same processes or a couple clicks here and you're either deploying or she either setting Riders fee of the CLI or setting up a provider be a pro tour. + +00:20:00 + +Denis Lelic: Okay, yeah, those are my questions because I just Compare these two structures and I was just thinking about To some of these categories that are not listed there. So thanks for providing those questions answers. There's yeah,… + +Tyler Wright: That one to call out. + +Denis Lelic: go ahead. + +Tyler Wright: What I would hope would happen is. I would hope that the documentation is transferred. It does not have to be perfect. when we do the transfer and we update the categories we can then we have all next week to optimize it. there's a Sig documentation meeting happening the November 28th. and my goal for that meeting is as a part of the agenda. We just basically take the working group for the Akash website go to the Sig documentation meeting and have an agenda item to optimize any of the documentation. We can just move it from there. everything's in markdown. It would take seconds to move and so we can just get sick documentation's eyes on it. And that should be enough to really hone in on. + +Tyler Wright: Action if you need to change things after that we can as well. + +Denis Lelic: I just remembered Nothing dark related, but just stuff we discussed. A couple of minutes ago with Jack Zach. What do you think about having just a case study section in the akashico system? The way it's structured now. It's like you can just switch between devtools projects deployed and a cash provider. So case studies and projects deployed on Akash could be somehow connected but I have to be because for projects deployed on Akash we can just + +Denis Lelic: have tiles and cards listed With basic information, but for the case studies like each of these. Tiles or cards would be clickable and you can read about it. Get more information like how it's done and get the whole. Story behind it. do you think this could be the part of the akashico system or… + +Zach Horn: Yeah like that a lot. + +Denis Lelic: we can just Add an extra. Menu item and call the case studies or showcase or whatever. + +Zach Horn: Yeah, I don't think it needs its own. Thing in the menu per se but I do like the tiles that you're showing right now just gives it a little more weight above and beyond a blog entry. That's the one thing I've been thinking about a lot is we do more built-out posts that are very tied to specific deployment answers specific ecosystem items or just things that we want to get eyes on. I don't want those to get lost in the blog because we'll have lots of blog posts around, all kinds of things. So I do like this where does it so it's on the ecosystem page. So that's Akash net Network slash ecosystem. I assume for the domain. Okay. + +Denis Lelic: Yeah. slash case studies + +Zach Horn: right Okay. + +Denis Lelic: and basically when you click on one of these tiles you can have on article. but we can find a way to embed also for example as the Excel on Akash, so it's not like Just living on some domain, but it's part of the website. So anyone who's like playing around with it? Can also reach other? + +Denis Lelic: other information on the website + +Zach Horn: Yeah makes sense. + +Denis Lelic: But it's also reachable through this part. we have this section on the home page. I'm talking about the home page here. but when you scroll down You have this what's possible with a car so you can view the ecosystem and… + +Zach Horn: + +Denis Lelic: we can just highlight a couple of items. For example here. There's the AI Projects deployed in Akash and we present a couple of death tools. + +00:25:00 + +Zach Horn: Yeah, that looks great. I like what's possible. + +Denis Lelic: and if you hit + +Zach Horn: I like that positioning what's possible? + +Denis Lelic: So when you hit Akash ecosystem, you're just taking. to this page where you can switch between these four options and each of the options is providing these cards with Information and call to actions and stuff. So yeah,… + +Zach Horn: Yeah, that's great. + +Denis Lelic: also prayer or some. I don't know a third tool could be just awesome Akash repo So we have projects deployed in Akash with some filtering options. And we have Akash providers. This is something piercing his team also added. where we can list all of the providers. and showcase their resources + +Zach Horn: Yeah, this looks great. + +Denis Lelic: Okay, One thing I want to do. Yeah time. + +Tyler Wright: So I was gonna let you finish. So feel free if you need to finish your statement. I Correct. + +Denis Lelic: No, no. Good. + +Tyler Wright: I'm a little slow often so correct me if I'm wrong, but one of the things that also thought would be great for that where the case studies could live. I really like that positioning is Zach said about what's possible with Akash all + +Tyler Wright: I would really like what happened to gets to getting started page. I know that on the current website you have this get started area and I really like these areas where you can Are you I want to deploy I want to know how people are using I want to go to the documentation. I want to become a validated you like this whole area, but then when we go to the current website + +Denis Lelic: Yeah, it's not reachable. + +Tyler Wright: It's not. + +Denis Lelic: It's there but a couple of meetings ago, we talked about get started within the docs page. + +Denis Lelic: just because I was thinking about having to get started paid the pages or flows might be confusing for the users. So if anyone is interested. They could get started go to the docs page and all of the information and all of the stuff you've mentioned would live here. So you can still become a provider deploy an app we can exchange these tiles like we can add or remove excess gpus and basically we can just add whatever we think we need to add here, but I would just like to avoid + +Denis Lelic: having That all of the information doubled on two different places. but I'm opened for discussion if you think + +Denis Lelic: we should have it the way it is now. + +Tyler Wright: Alright, I don't know I might have missed that conversation. + +Denis Lelic: + +Tyler Wright: So I apologize. I do not want to rehash it. I just not like It's not a rock. I'll die on I guess but I understand what you're saying about the duplication. I feel like maybe the structure might be slightly duplicated, but you can have different kind of tiles. if you go to the get started area and documentation, it could be about more specific things. Whereas I think case studies. and some other more general information can live on they actually get starting page, but you can get started page which you can access from the main page of the Akash website my only fear and this might be just small is I wonder if some people would be deterred by. I wonder if it's more inviting that from the homepage or seeing. + +Tyler Wright: Get started and they're all right, cool. I can get started and then they can access documentation from there as opposed to. Having to click on documentation because I feel like some people might think all right. The documentation is going to be very Heavy and maybe that's not the way that they want to learn and they would prefer just to see it get started, but I don't know that might be semantics. So that was my only question.. + +00:30:00 + +Denis Lelic: Yeah, the way it's structured now. There's still get started call to action. But it's not taking users to a dedicated page, but it's part of the docs page for example. You get started and you're presented with everything that's presented currently get started page. It's just located within the docs. But when you click for example deploy an application. You're also presented with. Cloud nose console + +Denis Lelic: just the resources. Specified just for this product. If you want to become a provider, you still have that page where we list information and resources for the predator. + +Denis Lelic: So yeah. + +Tyler Wright: If it's that behavior, I then strongly say that we should move it out of documentation because if I click on become a provider inside of documentation, it would be my belief that I get taken to the documentation. I could take it to the document Not a page. It's even necessarily in the documentation. not like the pre-tor page, it should take me to if I wanted to deploy be the CLI of how I'm deploy the cloudmouth. I should have all those options. That's just my two cents. + +Denis Lelic: Yeah, maybe we just have to form the call to actions or the headlines differently. Maybe it's become a provider with Trader or something. But there's a couple of options for this page. we can have + +Denis Lelic: the get started section but we could add different. categories and the subcategories for example It's called Essentials here, but in the new structure is Get started with your first deployment or something. + +Denis Lelic: So we could just restructure this part as well, but I can have a better look to see what are the possibilities to restructure It's either. + +Denis Lelic: bringing this information get started into a separate page or finding a way it works within the docs. + +Tyler Wright: Okay. + +Denis Lelic: click on + +Denis Lelic: one thing I have still here in my notes. Zach what are your thoughts on having landing pages specified for or dedicated for different? campaigns for example we used to run these Chia campaigns for attract minors I think we could maybe do more. around that area like designing and building just a landing page specified for let's say one of the target groups and their needs. + +Zach Horn: I like the idea but we're Gosh, what are the words here? + +Denis Lelic: Yeah, I know. + +Zach Horn: We need to. + +Zach Horn: Some of those Target groups are in flare and… + +Denis Lelic: It's + +Zach Horn: flux right now. So I think we need to first get to a solid understanding of who we want to Target and then I totally agree that we should do some landing pages. What we could do in the short term is come up with a structure for a landing page that we like, kind of a cut and paste template that we could deploy against a number of different campaigns, without any specific content and then at the point where we're ready to start targeting individual groups weekend or audiences I should say that will be ready to go. What do you think about that? + +Denis Lelic: yeah, I was thinking about just having one template for All of the landing pages, so whatever we come up with. There's always there and we can just exchange the graphic. Content and it's ready to go. + +Zach Horn: Yeah, I like that a lot. + +Denis Lelic: Yeah, I can do some research and What would serve this purpose and just put together just a quick layout and figma something to have up for discussion. But yeah, I agree first we have to specify what kind of Target groups are retargeting and then we can move on. + +00:35:00 + +Zach Horn: Yeah, I do think it's necessary though because at the point that we want people to land, we have an audience that ing. We do need somewhere for them on the website. Probably that's targeted to their context of where they find the website and that could look a lot like a landing page for that specific group. So yeah, let's get to a template on that. Then we can go from there. I mean, I think we could have something we could move forward on, maybe by the end of the year and to see one of next year. There's just a lot of flux right now, but I agree on the template. + +Denis Lelic: Okay, cool. nice + +Denis Lelic: so any questions or any ideas anything? + +Denis Lelic: George and Emmanuel Arthur and… + +George Pro: Yeah. + +Denis Lelic: I see we have a new user here. So welcome if you Have any ideas anything you would like to discuss? You're welcome. But yeah, I see George already race his hands up, Go ahead. + +Tyler Wright: Georgia Tech Yes we can hear you George. + +George Pro: Okay. + +George Pro: Thank you very much. And I think I was checking the note and then I saw somewhere that you guys say you are going to kind of make the heroes session the new website USA anyway, a bit visualize a lot of images Tyler was comparing some other website and then we said we are going to change but when I see the one that pirate s***, you see the same thing and I don't see individual so I'm asking if Maybe we are kind of. Changed our mind and then we are going to use the more of weight than visuals. + +Denis Lelic: And that's something we discussed in the last meeting there were some examples. just + +Denis Lelic: we discussed if we should bring something that's working within a code. But I have another example. + +Denis Lelic: you just share my screen. + +Denis Lelic: The first example from the previous week you can find in Discord and the second one. I was just working on it. I think a couple of days ago, so Maybe we could highlight super cloud just towards super cloud and when a user would hover. maybe it's like + +Denis Lelic: we got different fields popping up basically buttons. and everything in the background would blur so basically the user is focused on the super cloud and these are all call to actions. They're mostly dummies now, but it's just an idea I thought of so, I just put it quickly together. so users could get started view docs find out more about Akash, or we can just customize these call to actions. That's just one of the ideas and the first one you can find in the Discord. + +Zach Horn: That's really cool. Wow, so are those buttons so when they pop up you can click on them and… + +Denis Lelic: Yeah, yeah. Yeah. yeah,… + +Zach Horn: I yeah, you go to wherever What? + +Denis Lelic: we can specify what kind of button takes a user where and + +Zach Horn: I'm curious. I don't have much contacts on this how much does that slow down page need putting something like that in? + +Denis Lelic: I think it depends on the code and implement. + +Zach Horn: Yeah. + +Denis Lelic: Yeah, but maybe it's something up for the discussion with phency and see what are the possibilities there. + +Zach Horn: Yeah, definitely. I like it. Aesthetically though. It's very cool. + +Denis Lelic: Sounds good. Thanks, George for the question Did you wanted to say something? You can just say hi. If you don't me and don't have anything else. + +Emmanuel Arthur: Yeah, yeah currently. I don't have anything specifically to talk about what I'm currently waiting for. + +00:40:00 + +George Pro: how + +Emmanuel Arthur: It is the team to make the code open source that you can see what they are written in their code base then maybe if I have anything to talk about it could be and how they are using the timing CSS. Then I will shave the feedback about them. So that's what I'm currently waiting for. + +Tyler Wright: Actually Arthur to that point can you put a message in the website working group asking for access to the code base? + +Denis Lelic: Okay. + +Tyler Wright: From Pierce and then I'll make sure it gives it to because I know it's on there, their GitHub, but if you need access you should have access to just ask for it in a public setting and I'll make sure you get it as soon as possible. + +Emmanuel Arthur: So what I was thinking of currently I can't share and back since the code is still under development. and I guess they would give us maybe why week for us to share feedback including the code base and the UI. So, when they put it out there that they are finished everything then I think I'll free to share my feedback regarding the code base and everything. + +Tyler Wright: Yeah, but I think because you'll be working in the new website as well. It'd be good for you to have it as early as possible to get yourself acclimated. I think a lot of stuff is very familiar to you, but just I would just love for you to ask for Access as early as possible. And even if you hold off on questions in the short term, I just want you to be familiar as early as possible. + +Emmanuel Arthur: so I go to so + +Denis Lelic: Sounds good. anything else before we + +Denis Lelic: Finish it for today. + +Tyler Wright: I guess as an answer to Zach's question and we can talk about this now or we could talk about this between meetings and share with peers. I think George has been taking notes and I have some notes in the background, but as we plan out the next + +Tyler Wright: next couple of weeks months. I believe there is a plan session for next Thursday. That is an American holiday. So I'm not sure Zach will be there. I am planning on just keeping the meeting because we just have so much going on and it's my only meeting for the day. I think that's all right, but by next week, I would like to have the docs kind of transferred over and we can look at it. Even if they're in a rough State there's a lot of questions on Where stuff should go that is perfectly. All right. I would like to figure out a little bit more about that get starting page because That I was sold on the workflow when we get started page as a call to action on the home page it lives now today and I would like to carry that over. I think the documentation page. I like the visual aspects of it but to + +Tyler Wright: Have some of these tiles where you clicking them at least once or twice on documentation page and not even in the documentation, I'm not sure. I love that honestly, and then I would love to presentation to the Sig documentation so that we can get some more feedback on structure for November 28th. I think some people are out of office, but I think we need to start sharing or continue sharing the website to the Insiders in the community after that Sig documentation meeting and we might have to and this goes for me Zach anybody here. I would hope that maybe that week of only check the calendar. that week of + +Tyler Wright: December 4th through the that Monday through Friday, I think it's gonna have to be an all Hands-On deck because even the content on the website is great. But there's a lot of content that these are either missing or needs to be updated because it might be old and out of date. So we're gonna have to spend I think a fair amount of time optimizing the content and maybe filling in some gaps that I can clearly see so that might be a website heavy week as we plan towards potentially having a launch for the website. Maybe that following week of the 15th. or whenever this group decides, so I just want to focus on that because I know that is a blocker for something's that Zach is thinking about and strategizing about and actually doing I would say Zach if you + +Tyler Wright: wanted put anything up in the formatting that works for the current website. I would recommend you do that and then we'll either create a bounty for somebody or we'll figure out a way at the part of this revamp to make sure that it's optimized for the new website later. I don't think I should be your priority to do it twice, but it shouldn't be a blocker for the kind of work that you're doing. I I became kind of put that in the Discord so everybody can kind of think about it at a high level, but I want to start thinking about and start working towards some actual timelines and Milestone goals so that we can deliver this website. It's officially as possible. Go ahead George. + +00:45:00 + +Tyler Wright: George you might be unmute you had your hand up. I'm not sure if you're trying to talk. + +George Pro: Okay, and this a bit outside website by I want to ask questions. I think when I was doing some good I saw somewhere that Really also need some people to kind of contribute in terms of design. So I'm asking if the opportunity is to deliver by we can kind of work with you and this person that I want to be is he's not a junior but it's no really deep like Denis bum sure. He can contribute and then he said he needs somewhere to kind of continue in terms of design he said designer, so I'm asking if there's opportunities therefore. For him to kind of support they need in terms of design. + +Denis Lelic: Yeah. There is but it's more part of Sig design discussion. So maybe you just invite this person to join our next Sig design or reach out on Discord and I can arrange a separate call and discuss everything that's + +Denis Lelic: that recurrently need or this plant in the future for we talked about a bunch of things during the Sig design in our previous meeting + +Denis Lelic: Merge design, for example, there were some other ideas. So yeah, just let this person know. + +Denis Lelic: I'm available on Discord. And of course on Sig design meetings. Yeah, I thanks for the. + +Denis Lelic: for that information, I do agree. We need to kind of be aligned with the content and everything. That's + +Denis Lelic: in the website revamp, so I know I personally have to do a bunch of Graphics as well. Currently there are a couple of just placeholders. I have to redesign some of the graphics. So I'll make sure that finalized in the next week two weeks so beers can just Bring that up. + +Zach Horn: as for the content on the website, I know there are things that we need To get sorted sooner than later A lot of this though, including some of the headline copy. I'm going to see is more punch up than something that needs to be delivered sooner than that. So I think today's Point like we're gonna have a crunch week, call it a week before we plan to launch this where we'll just have to go in and kind of punch up everything that needs to be changed in the last minute. So some of these things I am holding off on but let me know Denis if there's anything like in the immediate call of the next couple weeks that you need in terms of content. let's go from there. + +Denis Lelic: Okay, Sounds good. I see Alani just joined. So we just have to give him a big shout out. Thanks for joining. I think it's your first time here, but for others that are not aware alani's like the Akash OG as Tyler would say + +Alani Kuye: Denis good to see you Hello, everyone Zach. + +Denis Lelic: Hey. + +Alani Kuye: Hi, great to see you. + +Zach Horn: Hey Alani. + +Alani Kuye: Go always excited to be, having a chat with you guys. + +Denis Lelic: Yeah, we were just discussing a couple of things about the website. So. Anytime you have time. You're welcome to join. + +Denis Lelic: We're working currently on the Website revamp, it's pretty much done. We're just focusing more on content now and making sure everything's polished running smoothly. but you can have a look. I think there is a link. and the chat section are not sure if you can see it, but here is again, so there was a team. + +00:50:00 + +Alani Kuye: Yes. + +Denis Lelic: I think it's called human HQ. They were granted the governance proposal to redesign and + +Denis Lelic: make a better experience on the website. So for the last couple of weeks there have been working on it and they basically put it together. Everything is functional almost but yeah, we have a couple of weeks still to make sure. + +Denis Lelic: It's running as good as possible. So. Yeah. + +Alani Kuye: That's awesome. Thanks for sharing that I'm going to poke around. + +Denis Lelic: Sounds good. Yeah, any questions Alani from your side? + +Alani Kuye: No, not at all. I'm in the site just from first glance. It looks nice. And please I can help. just how to reach me and I'm gonna start joining this meetings going forward when I can. + +Denis Lelic: It sounds great. You'll be a great addition to this working group. + +Alani Kuye: appreciate + +Denis Lelic: Yeah, but for now we're Almost running out of time. So if anyone's Has anything else to share ask please free? Otherwise, we can wrap it up today for today and we'll see each other next week. + +Denis Lelic: Same time same place. + +Alani Kuye: All right. Thanks. + +Tyler Wright: Thank you all. + +Denis Lelic: Thank you. Have a good day. Bye. + +Tyler Wright: right + +Zach Horn: Thanks guys. Take care. + +Meeting ended after 00:52:05 👋 + diff --git a/wg-akash-website/meetings/018-2023-11-27.md b/wg-akash-website/meetings/018-2023-11-27.md new file mode 100644 index 00000000..2713fcb2 --- /dev/null +++ b/wg-akash-website/meetings/018-2023-11-27.md @@ -0,0 +1,592 @@ +# Akash Network - Akash Website Working Group (WG) - Meeting #18 + +## Agenda +- Website Revamp Progress +- Discussion on Website Revamp: + - Docs 2.0 integration and structure. + - Developer Documentation integration and structure. + +## Meeting Details +- Date: Monday, November 27, 2023 +- Time: 6:30 AM PT (Pacific Time) +- [Recording](https://svuqqu3fnqzburnqmdfrvy6bsku3fef2uzsbmspouj5mo2r4gjmq.arweave.net/lWkIU2VsMhpFsGDLGuPBkqmykLqmZBZJ7qJ6x2o8Mlk) +- [Transcript](#Transcript) + +## Participants +- Denis Lelic +- Piyush Choudhary +- Robert Del Rey +- Scott Hewitson +- Tyler Wright +- Zach Horn + +## Meeting Notes + +### Website Revamp Progress Update +- Piyush highlighted the functionality of "Update Post" buttons in every section, allowing direct access to the associated markdown file for making updates. +- This feature streamlines the process of editing content by eliminating the need to navigate through the repository on Github. + +#### Piyush Choudhary +##### Docs 2.0 +- Piyush shared a link for accessing updates related to the docs page, which is currently in progress. +- Emphasized that the provided link is the main one for tracking updates, and the docs page will be pushed to it once completed. +- Docs page structure follows the design plans, featuring a home page with tiles linked to various content, and a tree structure for navigation. +- Showcased a preview of the docs page, highlighting the content in the center, a display section on the right, and navigation buttons at the bottom. +- Anticipated completion of the docs page by tomorrow, with plans to push the complete update. +- Introduced the T structure implemented for Docs 2.0, encouraging individuals and committee members to contribute to it. +- Emphasized the importance of following the tree structure for consistency and ease of navigation. +- Piyush mentioned that he will try to push the docs by the morning, and in the meantime, participants can access it through a provided link. +- Piyush shared that he has guidelines ready for community members regarding documentation. + +##### Development Page +- Previously, the development page had only one option - overview. +- In the last meeting, jump links were discussed and have now been implemented for easy navigation within the page. +- Current groups are now represented as cards, making it easy to add and manage new cards, such as adding "sig documentation." +- Clicking on a card opens up an overview of the respective group. +- Highlighted the improved management ecosystem for user groups, allowing easy contribution and updates through markdown files. + +##### Pricing and Network Activity Page +- Pricing page design has been updated, providing a general comparison overview. +- Users can access custom calculations for more specific pricing details, with calculations dynamically generated from Cloudmos APIs. +- Mentioned the ongoing development of the network activity page. +- Focus on refining the docs page, development page, and network activity page, which are considered the most functional parts. +- Future steps involve addressing minor UI issues and responsiveness, followed by updates to textual content, such as testimonials. + +### Providing feedback on completed pages. +- Denis expressed appreciation for the integration of docs into the main page. +- Inquired about completed pages where feedback could be provided. +- Piyush mentioned that the homepage is considered complete and open for feedback. +- Piyush Confirmed that the Community page is complete and open for feedback. + +### Verification in the PR Process for Communinity Contributions +- Community contributions are managed through markdown files, with guidelines provided for contributors to add details such as thumbnail image, tag, author name, title, description, and date. +- Tyler expressed appreciation for the ability of community members to add their projects independently, eliminating the need to contact core team members for additions. +- Tyler Suggested the addition of a verification process, potentially in the README of the PR, to ensure the accuracy of information. +- Tyler highlighted the importance of a verification process from an operational standpoint to confirm that projects mentioned in PRs are actually deployed on Akash. +- Piyush confirmed the existence of clear guidelines in the README for PR creation, including a specific format and predefined questions for users to answer. +- Piyush Mentioned the review process, where the core team can assess PRs, provide feedback, and either merge or close them based on adherence to guidelines. + + +### Completed Pages +- Piyush confirmed that the homepage, ecosystem page, and Community page are functionally complete, with minor UI issues to be addressed. +- Mentioned that the blog page is also complete, with minor issues related to descriptions to be fixed in the next few days. +- Updates on Docs, About, and Token pages are in progress, with UI changes being worked on for the network activity page. +- Zach jotted down the information and asked about the best place to pass new copy for these pages. +- Piyush suggested using Figma for collaboration on copy changes, considering ongoing restructuring and development in the repository. +- Piyush acknowledged the possibility of adding Zach to the repository but advised against it due to the dynamic nature of ongoing changes. +- Suggested alternatives like a Google Sheet for initial copy changes. +- Zach acknowledged the instructions and clarified that he would pass the copy updates to Denis for design integration. + +### Explorers on the Website +- Denis proposed adding a link to explorers on the website, considering it could be part of the network or another relevant section. +- Scott agreed, noting that providing easy access to explorer links is helpful for users familiar with blockchains. +- Piyush suggested placing explorer links on the token page. +- Denis considered either the token page or the network activity page as suitable locations for explorer links. +- Piyush confirmed that adding explorer links would involve a button redirecting to an external page. +- Denis agreed to add the explorer links to the design and tag Piyush for coordination. + +### Participation in the Sig Documentation Call +- Tyler informed the team about the Sig documentation call tomorrow, emphasizing the importance of participation. The call will cover the structure and formatting of documentation. +- Tyler outlined that the first part of the conversation will focus on the structure of documentation, and the second part will cover formatting. +- Piyush mentioned that he had already brought up the guidelines for documentation in the current call. He stressed the importance of not altering the tree structure and mentioned that documentation should be simple and easy for new users to navigate. +- Piyush expressed his intention to participate in the Sig documentation call and provide the mentioned guidelines to ensure consistency in the documentation structure. + +### Documentation Structure +- Tyler provided context about previous decisions on documentation structure. +- Tyler highlighted that the community had previously preferred the step-by-step format over a long continuous page. +- Piyush demonstrated the current structure where the left side shows markdown files, and the right side displays the content of the selected file. The right side also allows quick navigation to specific sections. +- Tyler expressed concerns about potential pushback from the community, as some might prefer a step-by-step approach for certain instructions. +- Piyush reassured that the current format is flexible and can accommodate subsections, allowing for step-by-step instructions if needed. Proper guidelines will be shared to maintain consistency. +- Piyush emphasized the importance of following standards while creating content and expressed confidence that community members will adapt to the guidelines + +### Developer Documentation +- Tyler highlighted the importance of incorporating developer documentation on the docs home page, considering the need for contributions to the code base in 2024. +- He suggested having a link in the tile section on the docs home page and a secondary menu, possibly above the support section. +- Piyush shared the plan to have two options for users: one for regular user documentation and another for engineering notes, focusing on the technical aspects of contributing to the code base. +- The proposed solution involves a tab switch between user and engineering notes, where the content and tree structures change based on the selected option. +- Zach expressed concern about having multiple trees for different documentation types (user and developer), as it might increase complexity and confusion for users. +- Piyush proposed having a separate tile for "Engineering Notes" instead of tabs, which would change the tree and structure when clicked, keeping it distinct from the regular user documentation. +- Zach emphasized not prioritizing one segment of the user group over another, as both deployers and technical contributors are crucial for the network. +- Tyler highlighted the importance of providing engineering documentation for contributors, such as developers building on top of Akash, and proposed an "Engineering" tile to distinguish this content. +- Tyler emphasized the importance of maintaining a distinction between user-friendly documentation and more technical engineering notes. +- Tyler proposed having both menus live, with a separate "Engineering Notes" section below the main tree. +- Zach suggested consolidating all technical documentation under a top-level header, such as "Advanced Setup" or "Advanced Engineering," and having a tile that jumps to that section. +- Zach expressed concerns about potential confusion when referring to either the Akash documentation or the engineering documentation, suggesting it would be simpler to have a unified Akash docs tree. +- Zach indicated a preference for a unified tree and expressed a willingness to discuss further, either offline or during the Sig docs meeting. +- Zach requested feedback from Denis on whether to have one unified tree or two separate trees for documentation. +- Denis expressed a preference for one tree, emphasizing the challenge of prioritizing users and deciding between deployers, providers, or technical individuals. +- Piyush expressed the need to explore various options and evaluate the available choices. + +## Action Items +- Group to provide feedback on the completed pages. +- Zach to initiate copy changes for the completed pages. +- Zach to aim for completing copy changes at least a week before the targeted go-live date on December 15th. +- Denis to add explorer links to the design, considering placement on either the token page or network activity page, and tag Piyush for coordination. +- Zach to prepare and share additional thoughts on the developer documentation structure, especially regarding the distinction between Akash and engineering documentation. +- Group to explore best option for documentation structure. + + +# **Transcript** + +_This editable transcript was computer generated and might contain errors. People can also change the text after it was created._ + +Denis Lelic: Hey everyone, and welcome to today's Akash website This meeting was supposed to happen last week on Thursday, but since it was Thanksgiving. We reschedule it for today and thanks piyush for joining. + +Denis Lelic: I was planning to just used today's time just for you to give us a short. Update on all of the work. you've done and your team, of course. + +Denis Lelic: And then we have a couple of more different items to discuss but I suggest we start with your update if you agree, of course. + +Piyush Choudhary: You so I'm sharing my screen. + +Piyush Choudhary: Is my screen visible? + +Denis Lelic: Yep. + +Piyush Choudhary: Yeah, So this is the link where you can access some updates related to the docs page which are still in progress. So this is the main link where everyone will be able to see what's the current update? So once the dog piece is completely push it to the main thing. So this is the main link which can be tracked anytime with the latest from dates. But right now we have not pushed the dog's page to this link because it's still in progress and once it's completed, I guess by tomorrow, I will push the complete update so as per the plans and their designs, so dogs space looks kind of like this. We have the home page which have some tiles which we can link to some different things or website and then we have this straight which was planned by Luna's team in dogs to point or structure. So we just + +Piyush Choudhary: Use the tree structure similar to what they used and also implemented the content as well that they did in their dogs to point. so if I open this link as you can see in between we have the content and at the right hand side we have on display section and we will also have the buttons at the bottom. so people able to navigate through these pages of course and also there's some for now just ignore the phone sizing horn sizing will be similar to the left hand side. So it will look more symmetric. + +Piyush Choudhary: So right now this is what the T structure of dogs 2.0 that we implemented and accordingly I guess some individuals or some committee members plans to contribute to the dogs 2.0. So what they can do is they should follow this tree structure for example in getting started. These four options will be available and accordingly. The content will be Give me two minutes. + +Piyush Choudhary: So the new members can follow this tree structure. and I guess steering committee also grade on this tree structure. So the main Aim of this structure is that to combine things up? for example, if I'm a new user my first I want to deploy something on Akash quickly. So this is what this should only be the file that the user should be looking onto and he should be able to successfully Go through this. Page and should be able to deploy example development here. We can give some example of cloud most or something. So accordingly the content can be planned. So this was about the docs page and at the top we can go to the home page. So it looks like a dedicated page which is also good because dogs is a completely + +Piyush Choudhary: Important aspect of every ecosystem so we kept the design like this and also of course Denis created this design but this is a part of same Rapport. So it will be easier to manage things up. And then I was updates regarding the development page. So previously there was only one options like overview, but in our last meeting We discussed about creating the jump links. So we implemented the jump links so we can just jump onto the page through this and then we have the current groups. Also, these cards are very very easily available so we can add any number of cards. So let's say I want to add sick documentation. I can just go to the code add a markdown file and it will be visible. And as per the design plans if I click on to it opens up. + +00:05:00 + +Piyush Choudhary: Them overview of let's say second light X group where we have the meeting notes Etc. And right now one tree is missing. So what will happen is right now if I go to get our slash Akash Network, right? + +Piyush Choudhary: So this is the community report. So this will also become a part of this thing. So what will happen is let's say let's talk about classic chain so sick chain is one of the group which is a part of Sig group. So let's say we will have the sick chin card here when I click it opens up the sick chain with the overview which is Looking In this case this is what is basically appearing over here. And when I will click on notes, I will have a secondary tree where the meetings will be visible. So right now I have to migrate through the community rep, right, so I have to go to the meeting then I have to find it. let's say I want to see this meeting details, So all + +Piyush Choudhary: the whole meeting tree will be implemented years. So if I click over here so similar to this sig have four groups. Let's say clients have for meeting notes in the meeting folder. So it will be visible over here and everything will be manageable through the markdown files in similar way that is being here. Just a folder structure will be little different. but with little guide Anyone will be able to guess the process and can contribute to the website and keep on updating to the website repo and everything will be visible on the website itself instead of going to the repository and see what are What are the links? So it's kind of a complete management ecosystem that we have built when it comes to the user groups. And I think that was the plan. The community or I guess current groups. and then + +Piyush Choudhary: these are the pages that are there. + +Piyush Choudhary: let's not much updates and that's secondary update is about the pricing page. So I go to the presentation page. So we updated or design. So this is a general overview is the a general comparison like this is this and if the user wants through custom calculations, you can just go to the customer calculations in the number the calculations will be here time as you can see and everything is getting pulled over from the cloud most apis and all and network activity page is also there. But then there will be some design changes as possible wind. So the network activity page is not as per Tailwind right now, but it's in the process of development. So yeah, that's update. And also as you must see the design has also got a lot of event. considering the Tailwind structures and all and hopefully + +Piyush Choudhary: everything will everything is in the process and mostly we are working on to refining the docs page some work on the development page then some work on network activity page. So these are the most functional parts that are left right now then after this we will just Want to refining the minor detailings of the UI components there might be some minor issues with the uis and all responsiveness and all and then we just move on to updating the text. for example testinomials needs of date on the text what needs to be put in all so. Yeah. This is the process that you're following and will be followed throughout. + +Denis Lelic: Thanks for the update. I really like how the dogs are becoming part of the page. is there + +Denis Lelic: any of the pages do you think they're finished where we could maybe Provide feedback or everything is still part of the profit? + +Piyush Choudhary: So for example, the homepage if this is the main link which you can follow. So for dogs page the design is not yet complete. So homepage is complete. So you can provide some feedback on the home page any issues that you are seeing right now. There is little issue in this part because if you see when the content is two line, right and here there is one line. So the things are getting shifted like it's not in line. So I will just implement the proper Heights so image Let's say this will cover excite so it will be aligned. So yeah, this is but the updates is although all the homepages it's complete if you want to give the feedback feedback and then + +00:10:00 + +Denis Lelic: Okay. + +Piyush Choudhary: ecosystem is also almost complete there is just a minor issue when it comes to the responsiveness. there is some margin issue. I guess when it comes to + +Piyush Choudhary: say this + +Piyush Choudhary: So in case of the button is getting to attached to the text, so these are some minor issues that will be addressing very soon. Once the functional part with the talks page development page and things are complete. + +Piyush Choudhary: And when it comes to the Community page, it's complete. So you can also give feedbacks on the Community page as well. And this is what the community contributions so it is also written in markdowns. So we will have a guideline if someone wants to someone created a video on the YouTube and he wants to list the community contributions. You can just go on to the airport and create a folder in the markdown file. There will be three to four things will be required the name of as you can see the thumbnail image the tag. Let's say it's a video tutorial graphic or something author name the title the description and the date and after pushing the folder to the airport, it will be visible like this so we can track it over here. So + +Piyush Choudhary: Result list of community contributions and then events are also coming from the markdown. So whatever the events we have we can keep on updating this. File from the markdown itself. So yeah. + +Denis Lelic: Yeah, that's great. I mean the way the community contributions look now is like, + +Denis Lelic: I'm not gonna say it but this is a great Improvement. I see Tyler and… + +Piyush Choudhary: Yes. + +Denis Lelic: Huey joined, so Welcome guys if you have anything. You want to feel free Go ahead Tyler. + +Tyler Wright: All right. I just want to say sorry that I'm late. I miss some of it's I missed some of the stuff about docs. I did get an update and Discord, but from what I've just seen from some of these pages that piyush just showed. I really like the ability of community members previously. Somebody would have to message a member of the core team to add their project. + +Tyler Wright: I really like that. They cannot do it themselves. And then either you piyush you or somebody else can merge those PRS. I'm sorry. + +Piyush Choudhary: Yep. + +Tyler Wright: I really like that idea. The only thing that are maybe think about us adding is maybe some sort of verification as a part of the read me maybe for the pr that's just a way for us to check so that people aren't just like yeah, I'm deployed on a cast but we can't really see it. But it may not be information that will end up here on the site, but just a verification here. So I'm just thinking about from an operational standpoint if you're seeing some PRS of all these projects. + +Piyush Choudhary: Yep. + +Tyler Wright: How do you know if they're deployed on Akash or not? + +Piyush Choudhary: so basically we will have the proper guidelines. So as we will be on the part of the management, so we'll be able to say all the PRS and we will have a clear guidelines in the readme if you are catering your PR, this is the guideline that needs to be followed. And this is the syntax and while creating the pr this should be a format all of title feed at project at my project and the description should be proper We can have some. predefined questions that the users have to answer and + +Piyush Choudhary: like how it is related to Akash and what motivates the user to deploy or use Akash and all and after that once the pr is period we can just review and if it looks good we can just merge it otherwise because we will just comment like this is not in the scope of getting merged or this is not correct format this is not something that can be merged or added to the website and then we can just close the pr. So this is how we can manage things up. So this will of course require a complete because as you must see the community rep so the community repos also getting most to the website, right and + +00:15:00 + +Piyush Choudhary: I mean the community report I'm talking about this report. So all can also be managed on the website. So whatever the content that is getting updated here can also be updated to the website. So let's say signal lighting groups has five meeting nodes. So the 5 meeting notes will be available like this. So users will be able to read it. So as everything became a part of the website. So it will definitely require a complete watch and we will do our best to keep a watch on every PR and give feedbacks and merge it accordingly. + +Denis Lelic: Yeah Zach. + +Zach Horn: So for my notes here as you were talking piyush as of now the homepage the ecosystem page and the Community page or functionality Complete because I guess I need to come back and do copy changes for all those pages. So are there any other pages that are functionality complete that I should be looking at and… + +Piyush Choudhary: Yep. + +Zach Horn: any others that are going to be done soon? + +Piyush Choudhary: so basically if you see from the functionality standpoint or gosh home page is complete Community Pages complete ecosystem page is also complete just a minor UI issue is there we will fix that and log, Is also complete… + +Zach Horn: Mmm + +Piyush Choudhary: but there is a little cache the descriptions are not getting past properly. So we will just update those within the next few days from the functionality standpoints. It's complete and docs is in the process and then about is also complete. we are just working on some UI changes for the night for activity page. and token wait and token pages also complete if you see + +Zach Horn: Got it. Okay. I just jotted all those down. + +Piyush Choudhary: some yeah. Yep. + +Zach Horn: So all get started on copy changes for those pages is figma the best place to pass the new copy. + +Piyush Choudhary: Yeah, I think I can also add you to the repo but I think a chin and making any changes to the repo right now will not be a good move because still there are some restructuring and sometimes beef sometimes while developing if he finds something better. So we implement the functionalities accordingly. So for now I think either you can create a Google sheet or… + +Zach Horn: Sure. + +Piyush Choudhary: you can ask Denis to update it on the let's say for example If you want to add some heading here as this is all from Telvin, so I will just ask to not make any changes to the X text changes can be acceptable. for example, if you want to add a update any text here and text here you can just ask Denis and you updated and also I will need to wear the tooling these cards for example, we have deciding. So this is just a text. We can just a bit in within few seconds. we're to link all these things so proper links will be required for all these cards and for example on shaft very take and all and according so I would say. Watch this link as an link. + +Piyush Choudhary: and then let's say in join the community section,… + +Zach Horn: Got it, okay. + +Piyush Choudhary: we have this testinomials. I will need our username to put in here the testinomial would so accordingly. I cannot take + +Zach Horn: pass these copy updates + +Denis Lelic: It's the same one. We've been using the whole time,… + +Zach Horn: Yeah. + +Denis Lelic: I believe so, whatever you drop in there. I'll go through it and make sure that your comments are part of the design. + +Zach Horn: Okay, sounds good. I'll try to get those in over the next week. Ideally maybe a little longer than that because I guess we're targeting December the 15th at this point. So I think ideally will probably want to copy done at least a week before we go live. So everything can settle that we can do any punch up, but that sounds good. I'll get started on that. + +Denis Lelic: Yet I go ahead. + +Tyler Wright: Here so, when you'll have some of those guidelines ready for those that are submitting PRS. I just want to better understand the guidelines for documentation for the Community page. And then also for submitting projects of the ecosystem page,… + +00:20:00 + +Piyush Choudhary: yeah. + +Tyler Wright: when you'll have those ready for review. + +Piyush Choudhary: So basically, this is its private right now. So we have some guidelines already structure in the readme file. So when we will release the website to the public, so the guideline will lower it to be there in the readme here like this. + +Denis Lelic: I have a question. for healing Maybe + +Denis Lelic: do you think we should add a link to explorers somewhere on the website? Currently they are not. Placed anywhere so maybe men's Could be part of the network or something. + +Scott Hewitson: Yeah, I don't. + +Scott Hewitson: Yeah, I think it's helpful. anyone who's familiar with blockchains, regardless of the network, you'll be looking for Explorers. So feeding that to people easily is I think it's a good idea. + +Piyush Choudhary: I think we can put those on I guess token page. + +Denis Lelic: Okay. + +Scott Hewitson: Yeah. + +Denis Lelic: Could be token or could be network activity. So piyush for you that basically means just button to external page. + +Piyush Choudhary: Yep. + +Piyush Choudhary: Yeah, yeah, okay. + +Denis Lelic: Okay, I'll add that to design and tag you. + +Piyush Choudhary: and sure + +Denis Lelic: Okay, And for the home page and… + +Piyush Choudhary: Okay. + +Denis Lelic: the ecosystem page when Zach makes the final content or even before that I can have a look at the UI. + +Piyush Choudhary: slope + +Denis Lelic: For the final feedback, but so far. + +Piyush Choudhary: Yeah, Yeah, thank you so much. + +Denis Lelic: It's looking So a great job. + +Denis Lelic: Yeah, and also we have to add links. I mean, I'll add them in figma and under there. I'll just tag you so + +Piyush Choudhary: Yeah, it will also be great. If you can also create a Google s***. For example, let's say there are links we can Define for Section the stack but if it's on fig mall, so then also find over it's + +Denis Lelic: Okay, Nice anything else you want to add? + +Piyush Choudhary: Mmm, so far no, just one thing and also as everything is coming from the markdown, So for every sections we have these buttons update post. So if I click on this button It will take me directly to the markdown file so I can just make update directly instead of browsing through the repo and finding where is the blog and all and also for all these pieces? Also we have the similar functionalities for example development. So we have added this page button on GitHub. So if I click this it will take me directly to this meltdown 5 or the content from where it is coming so I can make direct changes accordingly. So, that's all. + +Denis Lelic: Yeah Thai + +Tyler Wright: This is awesome. I don't know if y'all talked about it before some of us joined. So I apologize, but in terms of documentation, it would be great if + +Tyler Wright: Piyushu and anybody else on this call can join the Sig documentation call tomorrow half that call will be about just structure of how the documentation should be for those that want to participate obviously now with being a community effort we have to have really strict guidelines on what is expected of documentation. + +Denis Lelic: you are + +Tyler Wright: We'll kind of outline that tomorrow, but the second part of that conversation will be around the formatting of documentation to make sure that… + +Piyush Choudhary: Yeah. + +Tyler Wright: if you have any other questions or Denis, if you have any other questions, you can ask those there should be pretty straightforward at this point. But again, if you all have any other questions, it would be great if you all can get those answer tomorrow and then we can Continue to populate the markdown file. + +Piyush Choudhary: So I already mentioned in the cold today. So there's one guideline that needs to be followed by all the community members who are trying to contribute to dogs. Do not mess up with the tree, right? This is what something as you said was planned in a dogs 2.0. get started then we have concept architecture deployments right Network feature provider validators. Then we have some sections like most subsections or suburb of subsections can be added but the dogs contention should be structured or shouldn't be retaining the markdown files only in the markdown and number two guideline is to not divide the content the way it is right now on the dogs Akash dot Network there are many suburbs of sections which makes sometimes for example and Gifts of deployments. + +00:25:00 + +Piyush Choudhary: I have a lot of subop sections. So this was eliminated by lunar streaming docks 2.0 so they should be the guidelines like for me users dogs. This is the structure like keeping things as simple as possible. For the end a new users will be the top priority and keeping less sub of sections for example here there are many trees and all so this is not expected. for example, I have to go through different files and all it should not be different files, but + +Piyush Choudhary: I guess should be deploysing It's a complete merger of everything the lunar stream did so this is a structure that needs to be followed. So I will also be there in the meet tomorrow. So I'll just put in this guideline. So anyone who's contributing will have a proper understanding on how to plan things out for the tops and + +Piyush Choudhary: Okay, I started you can speak. + +Tyler Wright: Sorry real quick. thank you very much. I appreciate that. For context sake it was previously decided if you go back to that documentation page as it is, I think the version worth. Yeah, it was decided during those meetings. So Luna's team did create an option where instead of having all those steps which are separate pages everything kind of lives on one page you kind of have it but what they did as they did add some subsections on the right hand side so you can quickly go to maybe where you left off. I think one thing previously just for context sake right when Scott Carruthers Join, the documentation. it was in this format as you have outlined and people liked when Scott changed it to the steps. So you go to each step one by one you click on a new page people in the community like that better. + +Tyler Wright: And so I think the happy medium was we would have it on all one page. You wouldn't have that many menus on the left hand side,… + +Piyush Choudhary: but + +Tyler Wright: but it'd be easy on the right hand side to get to the specific steps. outlined just want to make sure that that continues to be the case. + +Piyush Choudhary: So basically What's Happening Here is as every docs follow. So in the left hand side, we have the markdown files that are appearing. Let's say these are texture folder and inside that we have four markdown are Akash provider container equipments and all you so if I click on the Akash node, it opens up the return whatever or things that are eaten and that mountain and on the right hand side we have on this page. So let's say I just want to jump on to block creations that is basically written on this space somewhere so I can just click it just takes me to the block creations title. So this is how the things are and should be followed. Yeah. + +Tyler Wright: But I think that works perfectly in that scenario. Let's say this is another scenario where somebody's building a provider and they need to do Will it provide those step by steps or will it be Just had the things you know what I'm saying? what I'm saying is I think people in previously especially when they were following the documentation. They're knowing all right. I'm on step three and next to step four Nexus step five as opposed to just follow this long line of text. + +Tyler Wright: Yeah, so just keep that in the back of your mind that there might be some pushback about that tomorrow unless we can figure out a way. It sounds like you have the right menus Incorporated but maybe for some of these menus or for some specific instructions. It needs to be a step. Maybe just add it as a copy element for things that are 10 step processes to build the provider or something like that. + +Piyush Choudhary: Yeah, so basically you are seeing the copy code elements, right + +00:30:00 + +Piyush Choudhary: So yeah, I think it's a very flexible. So whatever folders let's say in this case. We have get started and let's say I'm on your first deployment and if I want to create a sub-deployment subsections for this section as well, so it's possible in this case. We have a subsections for example for most of the way we have subsections. So everything is possible. So the structure is in place. Let's try we'll just share a proper guidelines on how things needs to be done because we have to follow some standards while creating the content it should not be like we can write everything here and there so it will be a step process. I was just share the proper guidelines And I hope the community members will be able to pick it up accordingly. + +Tyler Wright: Okay, And sorry if I missed this, but when is the doc's link going to be available in the staging website? + +Piyush Choudhary: So basically, this is the main website that is being updated. So I will try to push the docs by morning. but still if you guys want to access you all can access through this link. Yeah, for some reason I wasn't able to push it. + +Denis Lelic: cool piyush if you have any questions or you need any information regarding the docs Maybe you can prepare them for tomorrow's meeting. + +Piyush Choudhary: And so basically I just have the guidelines… + +Denis Lelic: so we can + +Piyush Choudhary: because everything is written in markdown, So this is some guidelines that the community members have to follow so it should not be random work. You should give properly planned work. So things can be merged on to the stage or the scenario right now here, so we have the option at the lab and the right we have on display sections and in the middle, we'll have the content. So this is how all the dogs stays I have explored a lot of dogs as well. So Yeah, this is just a small guideline that I will share tomorrow and rest. I will just keep a watch on things like how things proceed and I will try to assist whenever required. + +Denis Lelic: Sounds good. + +Denis Lelic: cool Yeah. + +Tyler Wright: And then sorry my last chime in is have you all started to think about how we can incorporate the developer documentation? Because I think I know that's a very important for us to include someplace in the documentation side to make sure it's linked one thing that we're going to be looking for more in 2024 is people to contribute to the code base and stuff and so they need a developer documentation. And so my opinion is it should be linked have it be on the tile section on that docs home page and then also in the sidebar maybe it's like a secondary menu, maybe a line above support. But yeah, just want to put that out there Dennis Zach appears. + +Piyush Choudhary: Yeah, so basically + +Tyler Wright: Just make sure you all are thinking about that. + +Denis Lelic: a call to action. + +Tyler Wright: No, no, so basically I think we've talked about this previously Scott has developed documentation that is focused. So it's like how to set up your environment. How do you contribute to the core code how to do The nerdy stuff so not just user documentation of how to create a deployment with Cloud most it's like and I've linked it in the chat. It's literally how do I set up an environment and set up a stand box so I can test running my changes to the code base locally, I have that validators. I have to Providers. I got to have all these things and so it's literal like I'm trying to build Cloud most if I'm trying to build a tool on top of Akash, how do I do so And so having that area. + +Piyush Choudhary: Basically you're talking about the engineering notes, right? + +Tyler Wright: exactly + +Piyush Choudhary: So basically for that I thought I had a discussions with my team. So basically what we'll do is we will have to options here for the user one is for we can say a provider or whatever. So whenever I am on the user so the users will be open. So the user docs will be visible. And when I click on the engineering notes, so the engineering not stable will be open here and I can just browse to the content and the content will be so the design will look like this only so the tree and content will change accordingly as well the user or engineering notes, whatever that is being selected. + +00:35:00 + +Denis Lelic: Okay, are you talking about a tab switch? + +Piyush Choudhary: yep, so basically Yeah,… + +Denis Lelic: between users and + +Piyush Choudhary: so basically there are two dogs, right so for the user one is for let's say provider or whatever or we can call it a engineering notes so we can just switch through these two options so this is for the users like me and the second one is called the developers who wants to contribute to the code base of Akash core components as Tyler said so just the content that is being changed so the tree and the content is being changed the structures In the same as it is. + +Zach Horn: That's what I want to dive in on. + +Denis Lelic: no. + +Zach Horn: So, could you go back to the docs real quick? + +Zach Horn: When you're in the tab that you're talking about when you switch from user to developer is the tree that you can see there currently going to change or you're talking about more of a jump link to how would you say jump you to a place in that tree that we're looking at currently. + +Piyush Choudhary: No, no, so the whole tree will change because engineering notes talks I guess is completely a different thing. So it's a totally different content different tree. So the whole tree will change and accordingly effect. Let's say this is a first holder of that tree if I click on this the content will appear like this. + +Zach Horn: I might push back on that just a little bit because I do feel that we would be multiplying the complexity of the docs… + +Piyush Choudhary: Yeah. + +Zach Horn: if we have multiple different trees. From a user standpoint. + +Piyush Choudhary: remember + +Zach Horn: I know that we do have different user bases, but I feel pretty strongly that if we have multiple versions of the docs that's gonna be much more confusing for people to navigate… + +Piyush Choudhary: but + +Zach Horn: but I'd be curious what the rest of this group thinks about that. + +Piyush Choudhary: so basically what we can do is as the engineering notes is more about the core components and it's not basically targeting the general users. We can have a tile here which engineering notes when I click the engineering notes the tree and structure will change accordingly instead of tabs here. + +Zach Horn: Right, okay. That makes sense. and it's a bit of a semantics game, but I wouldn't necessarily by regular users. I assume you're referring to deployers. I wouldn't necessarily prioritize one segment of the user group over another per se because obviously people setting up providers and doing the more technical stuff is a massive part of the network and employers are definitely a part of that. but I wouldn't necessarily put deployers over other. Groups, but I Denis entire see you guys are looking to jump in curious what you guys think. + +Denis Lelic: yeah, what if we just add one additional item into the Example if its could be the last one after validators. + +Piyush Choudhary: And also basically the tree is very big. So it's a completely different context completely different technical. Descriptions and also the whole tree needs to change because if we add the tree here, so what will happen is it will look like the user might get confused they might start reading the content of the engineering notes and they will think what is this? So yeah. + +Zach Horn: Wouldn't that filter naturally though by the person choosing the top level category that relates to what they're trying to do. So, let's say you're a deployer and you come in and you're looking at the docs. Naturally, you're going to be scanning that top level list for things that are related to what you're trying to do. So let's say you're trying to ploy. You're probably going to click the deployments tab as opposed to somebody who's trying to set up a provider would look at the providers tab. I hear what you're saying that they're very different sets of content, but I do think the work to unify them would be really valuable to have one unified docs as opposed to multiple different docs. But tie I see your hands up. what do you think? + +Tyler Wright: Yeah. Yeah, I hear what you're saying. I think that there might be a little bit of a confusion. So when we think about this docs, the provider is very much part of our user base,… + +Zach Horn: For sure. + +Tyler Wright: you know that you have to deployer and you have the provider. So nothing really changes in the structure is here really what's changing is there's entire other side of people even as talented as some of the core teams that are building on top like the parade or… + +Piyush Choudhary: he + +Tyler Wright: team and most team there is a lack of understanding of how the Akash network blockchain works. And this is strictly engineering documentation that is conceptualy different, it's not even like most users won't even really be thinking about it's for a small subject that people that are looking to either build and contribute to the code base or looking to build something on top of it I get one of the sick clients groups are providers groups. I like the idea of an engineering tile on the Akash documentation,… + +00:40:00 + +Zach Horn: Sure. + +Tyler Wright: and I understand your hesitancy, but I feel My personal opinion is that both menus should live and then there should be an engineering header like engineering notes so that people that it should be below but if there are to be two separate menus, I'm all right with that because most people won't touch that engineering notes menu. They'll just stay right here in the screen that we have right here, but I'm happy to talk more about it and kind of move my fear is that some of the documentation that's Scott has written will be so technical if we put it on this page. It might confuse people getting started of that we have right now and getting started of the technical documentation is completely different. one is like you need three terminal Windows. The other is open up Cloud notes, + +Zach Horn: Yeah, I've seen the other docs. I know what you're referring to. I would be more tempted to piyush whenever you have a second if you could go back to the docs. I would be tempted to put all of that documentation under a top level header in the main tree that you have here and you could call it something like Advanced setup or Advanced engineering or something like that. So it's down at the bottom. It's a little away from all of this more friendly documentation. And then what you could do is have a tile like you're saying that jumps you to that part of the tree, so it's surface at the top but there's still one unified Akash docs tree. + +Piyush Choudhary: so there is one issue as Tyler said engineering notes is a completely different complex thing that the only code team members will be able to understand and so what we are doing here is we are not changing anything. We just have the tile here. So when I click on the tile the do engineering dogs is basically appearing here and as I can see the tree of engineering dogs is all very big. So if I merge it here, it will look very bad and it will look too complex to the common users all the deployers. just coming on to the docks. So we have just defining two categories, So we are just having two categories one for the user one is for the engineering notes and we just changing the tree accordingly. I suppose the users selections. So I think that would be the best choice. + +Zach Horn: yeah, I completely understand what you're saying, but I'm still pushing back on the two different categories. Because I can tell you strongly annoying some of the ways that people on the core team and in a community think about this stuff. Having one unified docs is in my opinion going to be something that people are going to want to see and if we start going down the path of there's actually two sets of documentation. I just have this feeling that that's going to get very confusing and become a point of contention. what I would suggest is that we separate this Advanced content that you have here under a top level section in the main tree. I think that's the possible way to do this. + +Tyler Wright: Zach I hear what you're saying, I guess my only question to you is do you think that we would have to adjust the tree as it's being shown on the screen right now or do you think from a user experience standpoint? If you have the advanced documentation on the bottom and you click it open and it goes to this big long tree people will really care. + +Zach Horn: I don't. + +Piyush Choudhary: e + +Zach Horn: I don't think that's any different than having two different trees. + +Zach Horn: You know what I'm saying? Okay, whether you click it open from an advanced tab at the bottom of this current youth quote unquote user friendly tree or… + +Tyler Wright: kind of but it's just like yeah. + +Zach Horn: whether it's a separate tree. it's the same content either way. I'm pushing back on the fact that when somebody says I was looking at the docs and you have to ask which That's what I'm pushing back on. It would be much more simple when you say I was looking at the Akash docs, there is only one box as opposed to. were you looking at the user docs or are you looking at the engineering Docs? + +Zach Horn: Does that make sense? + +Tyler Wright: Fair yeah, yeah. there that I think to solve that problem we can say are you looking at the Akash documentation or you're looking at the engineering documented, but I hear you I + +00:45:00 + +Zach Horn: but engineering is engineering documentation not Akash documentation. + +Tyler Wright: No, that'd be more like developer documentation. But again… + +Zach Horn: right + +Tyler Wright: if we're getting into straight up deep semantics. So I'm fine with either to be honest at this… + +Zach Horn: Sure. + +Tyler Wright: Is this something that we want to talk about with Sig docs tomorrow and get their opinion or is it something that we just want to make a determination on and Zach if you just want to move forward with the menu as you have described, I don't feel super strongly about it to fight it as long as it's there. + +Piyush Choudhary: so basically the thing is + +Zach Horn: I do actually feel pretty strongly about this. So we don't have to do this. I'm happy to discuss offline or in the docs meeting tomorrow and I can put together some thoughts around this if we want to dive into it deeper. It is semantics on some level but I do actually think it's fairly core to the design of how this is going to be going forward. + +Denis Lelic: Yeah, I agree with Zach Maybe. Everyone who is gonna attend tomorrow's meeting. can just Brainstorm a little bit. What are the options here? And I can put a design draft quickly together. So we have three to four options to discuss. And we're just gonna see… + +Piyush Choudhary: + +Denis Lelic: what works best. But I do agree. We have to be somehow careful not to we want to guide users so we don't want to throw stuff at Adam + +Piyush Choudhary: so my only point is the engineering mode is more about a very high core level Engineers for working on to Akash as private side. + +Denis Lelic: Go ahead. + +Piyush Choudhary: It is for cloud mode. operator or someone so It is not basically frequently required by the users. it should not be accessible. if we merge it here like this tree, so this will tree become a very big and it will confuse the users as I said, so that's why and also these two dogs are completely different thing when it's called the users and one is for the basically core level Engineers. So that's why we are just finding the categories nice. So this is how the homepage will look this is how the table with visible and for now what we can just create tile. + +Piyush Choudhary: With engineering notes and when I click on the title, the tree changes and the content appears from the engineering notes and… + +Tyler Wright: I appears. + +Piyush Choudhary: once the engineering. + +Zach Horn: Huge I completely understand… + +Zach Horn: what you're saying totally on the same page on that as to what the plan that you're putting for it is but I still disagree in several points. So just to keep it productive. I'll put some thoughts around what's impossible versions of this are and then as Dennis said we can decide how we want to move forward with that just really quick. + +Tyler Wright: And yeah. + +Tyler Wright: that + +Zach Horn: While we're on this point Denis, do you come down in one sentence? Where do you come down? As to whether it should be one tree or… + +Denis Lelic: I'm a fan of One Tree just because + +Zach Horn: two trees. What do you think? + +Piyush Choudhary: potential + +Zach Horn: Yeah. + +Denis Lelic: I don't want to dig the information deeper or Putting it behind a curtain. It's hard to tell what even like. + +Denis Lelic: Prioritize users. Who do we want to address first deployers providers or technical people who are willing to dig deeper. + +Piyush Choudhary: + +Denis Lelic: Yeah, let's just see what are the options out there and… + +Tyler Wright: Quick question for everybody here. + +Denis Lelic: we can discuss in. Yeah. + +Tyler Wright: And Zach at least we agree. And again, I don't feel super strongly about this do at least that there should be a tile into the cash documentation at sdl tile. That is at least a link to the engineering documentation. I'm not saying what the side menu looks like or anything like that. I'm just talking about the tile is that would be agree on that so that can be made or no. Okay, okay. + +Zach Horn: And we've accidentally stumbled upon a hot button issue. It would appear this is just my opinion, but the way I think about it is. There is the Akash documentation and that is a tree of content. + +Zach Horn: In my opinion, it should be one single tree. Thus that if you literally had a plain text version of it, it would just be one big document and what the website is doing is making it easier to navigate and what these tiles are doing are jumping you to different places within the documentation by surfacing them at the top of the page. So absolutely if there's an advanced section of the documentation that is for core deep level engineering that's very very Advanced we can still put a tile up at the top that calls to those people that says hey, do you want to contribute at the core level of the network on the most advanced features or whatever they could click that tile and then be jumped to that part of the documentation and then if you're a user I really need to get up and saying user because I don't necessarily think of users as a separate group than any of the people were talking about here. But if you're a deployer. + +00:50:00 + +Zach Horn: You can jump right to the easier documentation. here's cloudmouse. Here's how you set up a talk a deployment Etc. + +Tyler Wright: Yeah, so Pierce, I think that I would do nothing else except for make that tile in advance of tomorrow's conversation. I'll put something in Sig documentation. So let folks know this will be something talked about and we can figure out a solution worst case scenario. We just have to move the markdowns into the docs repo that we already had and figure out how to reorganize them. so I think that'll be just fine, but yeah, I like this discussion. So I think it's worth talking about more. I have a hard stop in four minutes. Otherwise, I would talk about + +Piyush Choudhary: and so basically what we can do is if something's not get ready by the new members so we can just migrate on the official documentation as it is to the docs. and later on when things get ready we can just keep on updating it accordingly. + +Tyler Wright: Code. Do you know how long would it take you to move the markdown files to the interchange. It's a days effort and hours effort or a week's effort just so I can think about it from a operation standpoint. + +Piyush Choudhary: So I just have to look like the folder structure and then I will just check in. How can + +Tyler Wright: What about the engineering documentation? Is that you can merge that over at the tree as it is right now into the current repo if we need to in a day is it the migration effort like a week? I that's the part. I'm just trying to understand how long would that effort take you… + +Piyush Choudhary: + +Tyler Wright: if you're not changing any menus and you're just moving the markdown file from one folder to another. + +Piyush Choudhary: So basically I have to plan things out from the functional standpoints as the new folders are getting added. I have to keep on updating the functions as well behind the scenes. So things gets reflected properly with proper functions. So engineering notes will require a proper planning because still things are not clear how we are trying to do that. So for now, I can't say anything but I just have to explore the first I will have to know how the things needs to be most and accordingly. I will have to plan things out. + +Tyler Wright: Sounds good. + +Piyush Choudhary: for example, the doc's page as you are seeing right now here we created the whole functions as you can see where we can keep on updating adding folders on the space sections how the contents get reflected. So as you must have seen I'm for the past two weeks. I was just keep on saying we are working on the docs so it took us around. Two weeks of brainstorming and then the functions and incrementations and all so according to things In the process and one of the things are pretty clear how the things needs we added with engineering notes. I can just say and this is how many days it will take to get reflected on the website. + +Tyler Wright: Okay. + +Tyler Wright: then I'll see you all tomorrow at 6 documentation. + +Piyush Choudhary: sure + +Denis Lelic: Anyone who has time, Join tomorrow's Sig dog's meeting where we can continue this discussion and thanks again for everyone who joined today's. website meeting and I'll see you not next week but on Thursday. Thank you. + +Piyush Choudhary: Thank you. Bye everybody. + +Zach Horn: thanks guys take + +Scott Hewitson: Thanks, everyone. + +Tyler Wright: thank + +Piyush Choudhary: that + +Meeting ended after 00:54:45 👋 + diff --git a/wg-akash-website/meetings/019-2023-11-30.md b/wg-akash-website/meetings/019-2023-11-30.md new file mode 100644 index 00000000..0e1b543d --- /dev/null +++ b/wg-akash-website/meetings/019-2023-11-30.md @@ -0,0 +1,321 @@ +# Akash Network - Akash Website Working Group (WG) - Meeting #19 +## Agenda +- Website Revamp Progress +- Discussion on Website Revamp: + - Updates on Stats Page. + - Documentation structure. + +## Meeting Details +- Date: Thursday, November 30, 2023 +- Time: 6:30 AM PT (Pacific Time) +- [Recording](https://ljuj3z4qnrttv4kg3z5owik37rofcpakeuwvmpqbiesastrh2coq.arweave.net/Wmid55BsZzrxRt566yFb_FxRPAolLVY-AUEkCU4n0J0) +- [Transcript](#Transcript) + +## Participants +- Denis Lelic +- Piyush Choudhary +- Robert Del Rey +- Scott Hewitson +- Thomas Greco +- Tyler Wright + +## Meeting Notes + +### Documentation Design Options +#### Denis Lelic: +- Previous meeting focused on documentation structure and docs UX. +- Prepared a few options to address this issue. +- Denis Lelic presents options for handling documentation navigation. +- Option 1: Additional navbar similar to how other platforms like Versel handle complex documentation. + - Denis emphasizes the importance of future scalability without causing issues. + - Proposes having a dedicated home page for documentation and a separate menu for related topics like engineering notes. +- Option 2: Labels above menu items, similar to YouTube's profile navigation. + - Denis highlights the usability of labels as anchors for users, making navigation easier. +- Option 3: Labels and groups, with clicks leading to a new page for specific items. + - Denis notes the advantage of providing a clear overview of items within each group. + - Acknowledges that this approach might be more suitable for projects with a large number of lengthy items. + +### Discussion on Documentation Design Options: +- Piyush expresses preference for the second option due to the simplicity of Akash's structure, suggesting it's more suitable for a maximum of two or three options. +- Zach supports the second option, finding it more organized and efficient for user navigation. +- Zach mentions a slight inclination toward the third option but agrees that further exploration may be needed. +- Tyler appreciates the discussion and suggests setting up a dedicated session for a detailed decision-making process. +- Tyler proposes exploring both options further but deferring the final decision to a later, more extended session. +- Denis emphasizes the importance of having a deeper discussion without necessarily making a decision today. +- Suggests that Piyush explores the technical difficulties and implications of implementing options two or three before the next meeting. +- Piyush stresses the urgency to finalize the decision due to time constraints and explains that option two is more feasible both technically and from a UX standpoint. +- Denis inquires about the potential delay if option three is chosen, and Piyush acknowledges that it might lead to missing the deadline. +- Zach raises the point of setting up for the future and not rushing decisions that could be suboptimal in the long term. +- Tyler agrees with the need for a timely decision but suggests deferring the final decision to a dedicated session on Monday or Tuesday. +- Thomas Greco proposes discussing development-related questions offline, specifically about setting up the IDE and development processes. +- Zach Horn acknowledges Thomas's point about improving clarity in certain sections within the docs from a development perspective. +- Zach Proposes taking the development-related discussion to the Sig docs meeting and suggests discussing it further outside the meeting. + +### Discussion on Hero Section: +- Denis Lelic brings up the previous discussion on the hero section, noting community feedback that it doesn't look as great as some others. +- Shares the idea of highlighting the "Super Cloud" and presenting different call-to-action items when users hover over it. +- Denis mentions it's currently a dummy concept and not planned for the first set of updates but could be considered later for a fresh and engaging touch. +- Zach expresses liking the idea, especially considering the site's cleanliness and text-heavy nature. +- Denis adds the possibility of adding interactive elements tied to mouse movement for a more engaging experience. +- Zach Horn approves of the concept and mentions the potential for experimenting with motion in the future. + +### Updates on Stats Page ( Website 2.0 ) +- Denis informs Piyush that Max from Team Cloudmos is working on the Stats page, and UI refinements will be handled by Max as well. +- Piyush confirms that he has updated the UI structure for the Stats page and will stop further work on it as Max is taking over. +- Denis Lelic clarifies that Max has already started working on the Stats page to avoid duplicating efforts. +- Piyush agrees and mentions that adding a button to the website to link to the Stats page will be a straightforward task. +- Specific details on reaching the page will be communicated by Denis after his next meeting. +- Denis Lelic confirms that the Pricing and Provider pages will remain as they are, and no changes are needed. +- Piyush asks about the subsections on the network activity about section, and Denis assures him that he will provide more information after his next meeting. + +## Action Items: +- Group to Consider organizing a dedicated working group session next week to finalize the design direction. +- Zach to bring up the development-related points in the Sig docs meeting for further discussion. +- Group to consider implementing the discussed changes to the hero section in future updates. +- Denis Lelic to provide information on how users will reach the "Stats" page from the website. + + +# **Transcript** + +_This editable transcript was computer generated and might contain errors. People can also change the text after it was created._ + +Denis Lelic: Hey everybody and welcome to today's. Akash website working group meeting As usual we meet on a weekly basis every Thursday. Where we discuss all the good stuff around the website piyush and his team are doing some great work and there have been implementing the designs and helping us out to make the whole website experience. + +Denis Lelic: Better in general. So I suggest we just start where we left and our previous meeting. We had a great discussion around documentation and docs so there was + +Denis Lelic: We were scratching our heads a little bit trying to figure out how to solve. And communicate to documentation at the same time without misguiding the users or throwing at them too much information. So I just Put together a couple of options. + +Denis Lelic: I'm just gonna show I'm quickly. So I can hear your thoughts. + +Denis Lelic: Can you see my screen? + +Zach Horn: Yes. + +Denis Lelic: Okay, cool, so one option would be to have additional. navbar + +Denis Lelic: I just had a look and do some research how others do it. For example verse hell has a really complex documentation with basically, they filled the whole. Line here with menu items and this one as well. So it's like a lot of happening there, but I was just thinking And looking for a solution that's going to help us in the future. So whatever we do now. I hope it's not gonna Screw us later on if we want to add or change something. So I like this approach because it gives us space to experiment later on if you want to add new. + +Denis Lelic: Subdocs, if I can call them that way and the way it would work so we have one home page for the documentation and basically what we have now and the other menu would just go like engineering notes or something. + +Denis Lelic: And of course In case the product rows the network grows. I just like the option to have that space where we can just build on. I'm just gonna go quickly through other options and then we can go back and I'm gonna leave it up to you guys for discussion. this option is something like for example, if you have a look at the YouTube and you go to your profile it has these labels above all of these menu items. So the way it works is just like these labels work as some sort of anchor for users where they can just focus on these. + +Denis Lelic: Touch points and it's easy to navigate. It's a bit longer. + +Denis Lelic: Yeah, so just mentioned Tailwind does something similar? For me personally, I know last time we discussed the docs can get longer. But when I had a look at what other projects are doing other companies are doing box are usually long and that's why the navbar is here to help. So for me personally, I don't have + +Denis Lelic: A conflict where I have to scroll through this part, that would be one. So just like providing this label and some dividers. or easier navigation the next one would be also something similar, but it's still different we have labels. and groups But for example if you click on deployments, it's going to take you to a whole new page. + +00:05:00 + +Denis Lelic: all the items from the deployments page are listed here so you can just scroll down. And find them all and if you want to have something else if you want to select something else you go back and then you select something else. + +Denis Lelic: the bad side of this approach is basically you can see the other items. but it kind of gives a good overview what items are in each of those groups. So I think this works best if you have a lot of long Items, for example if this would work a drop-down. And this would take the whole Space here. Then this approach would be better but I don't think at this point we don't have that much items. So yeah, I want to hear your thoughts. + +Denis Lelic: Yeah piyush. + +Piyush Choudhary: So after seeing all the three options, I think second item is much better because for the first item the problem is as you said there is a company which has a lot of item and they filled it up, right but in case of Akash, we can't have a lot of options we can have maximum two or three options because it's just opening up the tree off a different dots right? So I don't think that a class can have a 5 or 10. + +Piyush Choudhary: Solutions are similar to the third option. It will have a ux glitch. I will not have the buttons in. Sequence I have to go to the second page and… + +Denis Lelic: Okay. I just stop your for a… + +Piyush Choudhary: then so + +Denis Lelic: Anyone who's willing to participate in the discussion? Can you just focus on the things that you think would work and Just for the sake of time because we have to finish early today. + +Piyush Choudhary: Yeah, so I think second option is great so we can have the head category as you have mentioned and it has the tree. So I think the second option seems best. + +Denis Lelic: Okay, cool. Thanks, piyush. I know you had some opinions in our last discussion. What are your thoughts? + +Zach Horn: Yeah, I like the second option here. I like the third just for full transparency. I'm not entirely following why the third option wouldn't be feasible, but we can dive into that another time. I do the second as well. I think the high level point is that we just need this to be organized in a way that people can easily follow what is in each category and then they can also filter by what they're trying to do on the network, but I think both of these accomplish that to be fully transparent. I do think the third option leans a little bit more in that direction and I also group that is this point that it set this up for the future so + +Zach Horn: I would say because we have a short meeting today we can dive into whether or not that is truly feasible or isn't another time but I would say either option two or option three, it works for me and to denis' point like Purcell, is roughly towards option three I've seen, Tailwind is closer option too. So there's good prerequisites there on either side. Yeah time. + +Tyler Wright: I appreciate this Denis and obviously initial feedback. My question is twofold Denis. Are you looking to make a design direction today? Otherwise what I was thinking about doing especially because we have a shorter meeting is I can set up a dedicated session like a working group for us to do next Monday or Tuesday where we can finalize this if you prefer to do that if we're still decide between two and three, maybe you want to continue to mock up two and three, but I don't make a decision today, then I'm fine with that as well. + +00:10:00 + +Denis Lelic: No, we don't have to have a decision. Today would be great if we can have Just a better deeper discussion around this topic and piyush. Maybe you can find some time today tomorrow before the induct meeting happens and to see what are the technical difficulties to implement option two or three and what would that mean? + +Denis Lelic: for the progress and… + +Piyush Choudhary: The thing is we have to finalize the decision. + +Denis Lelic: stuff like that, so + +Piyush Choudhary: Because the time is too short and also as we are implementing so from the technical standpoint number two option is much more physical and also from the US standpoints as well. The number two option is much more physical because right now we can have the categories in the last meet as Jack said he wants to combine both dogs and should not have a separate columns and all so as per the last thoughts and two days discussions. I think number two option is much more physical in case of implementations and trees and the technical details that we have to look so far and I think we should not delay all this articles for a week or so because let's say we delays this isn't for a week. It will just mess up the timeline and we might not be able to make it as per the plants. + +Denis Lelic: Okay, so you Maybe just a rough estimate. In case we go for option three. And what would that mean? is that three weeks later. + +Piyush Choudhary: so on number two options Yeah. + +Denis Lelic: You don't have to answer take your time and you can always DM us and tell us if you want to go with this option. + +Denis Lelic: it will mean we're gonna miss the deadline. We're set up. so + +Denis Lelic: yeah. + +Denis Lelic: Okay, cool. + +Zach Horn: I would say The other thing on the table here is that we want to set ourselves up for the future. So as we're thinking about how we're going to organize this documentation going forward. I understand the need to hit the timelines that we set out. But we also in my opinion don't want to make any Rush decisions that are going to set us up in a suboptimal place going forward. So again, not something we need to discuss them too much detail right now, but that is definitely where my mind is for the moment. + +Tyler Wright: yeah, I would agree with that. I would say we won't wait a week. I Look to have that conversation except that meeting for Monday or Tuesday and during that time we can make a final decision. Everybody can make sure that they're prepared with all arguments and we can just like a final answer that point. I have to imagine that there's other things related to the website where energy can be transferred and maybe we should just talk about those things that we don't have maybe 13 minutes left. + +Denis Lelic: Okay, cool anyone has any thoughts About the dogs and everything or we talked about. + +Thomas Greco: Yeah, I know. + +Denis Lelic: Okay, cool. + +Thomas Greco: I think everything hey,… + +Denis Lelic: Hey Thomas, go ahead. + +Thomas Greco: how are you? I'm just kind of taking it all in but I think everything looks good. And then yeah, I think using virtual as a base mark as I could really. Just kind of good approach. because they're docs are showing depth and they cover such a wide range of use cases like Akash, so Good call there. + +Denis Lelic: Yeah, thanks Thomas. I agree. because Honestly, you can't really tell since akashi's open source how he's gonna develop we're probably gonna see different use cases. So it's hard to predict where the product will go and how to dogs will. develop but when I was looking for a solution, I was just thinking about having this freedom in space to add different things or change and it's not going to mean hey, we have to redesign the doc. So yeah. but + +00:15:00 + +Thomas Greco: Yes, I can ask offline too by yourself some questions about setting up this I did development and everything. + +Thomas Greco: Just because it really shouldn't be. difficult at all to add and another section or subset section and A subsection within a section, example Yeah,… + +Denis Lelic: Yeah. + +Piyush Choudhary: Yep. + +Thomas Greco: we can take that offline. I don't know. + +Denis Lelic: yeah, but piyush and… + +Piyush Choudhary: yes, it's like a book. + +Denis Lelic: his team One sec piyush just to clarify Peterson. His team are working on the whole website revamp. So they have a lot of work to do. + +Denis Lelic: Throughout the whole website. So of course dogs are part of it. but we want to make sure everything else is done properly So yeah, piyush you wanted to say something. + +Piyush Choudhary: I guess so once we Define the section so it's just get book only so we can just add the folders and then add the Magnum file. So it's not like changing the design initially. We have to find the structures like how we should look All right. So as you are developing everything from scratch, so the whole process the workflow like how the things will be passed in the front and all right. So it's a very smooth process one things are being finalized. It is just like a proper management tool where you can just add the Magnum files and folders. So The discussion is more about how it should look how the functionality should be and then for adding more content. It's just like updating them out on files in the + +Thomas Greco: Yeah, cool. + +Zach Horn: Yeah, let me jump in real quick because I do Thomas. that's a good point. There's lots of little sections within the docs that I think we could make a little more clear. I think that's more where you're headed with the development point, which is a good one. let's take that to the Sig docs meeting and let's chat about it offline as well because I don't want to lose that point because it is a good one. But yeah, it's a denis' point. this is more website design for the moment. + +Thomas Greco: All right. Awesome. + +Denis Lelic: Piyush I think There was one discussion around the hero section. + +Denis Lelic: For a couple of community members mentioned the hero section is not looking. + +Denis Lelic: Sexy as some of the other hero sections, so I was just thinking about it and I think you missed that meeting you were away. And I'm just going to share quickly here. What came out of that meeting? + +Denis Lelic: So one idea was to highlight the super cloud and when users would hover we could present them with different call to actions something relevant for now. It's just dummy. And we can kind of blur out the rest of the words. I'm not sure if you've seen that and I'm not planning to. Make this in the first Set of updates. So maybe later on we can find something. Cool fresh to spice up this hero section. + +Zach Horn: Yeah, I like that a lot, especially because the site is so clean and text Heavy. It would be nice to have maybe one feature thing. That's a little more engaging. what's the ux when you like Mouse over it anytime the user mouses over super cloud. It kind of highlights. It blurs out the background and it pops up those little labels. + +Denis Lelic: Yeah, we could also like a string it's to the mouse movement. So the Good interact with these so there's some movement around here. So if you want to have a front-end party and experiment with motion later on you can try of course. + +00:20:00 + +Zach Horn: Yeah, that's cool looks good. + +Denis Lelic: Okay, cool. + +Denis Lelic: Honestly, I thought discussion is going to take longer. So as a bit in a hurry, but now I see I still have some couple of minutes of time. So anything else? You guys want to discuss and Zach last time we talked about having a homepage check for the content. I'm providing some feedback from the visual point perspective and… + +Zach Horn: mmm + +Denis Lelic: just UI stuff, but whenever you have time drop some comments in the figma, so piyush can. update it as well. + +Zach Horn: Yeah, that's in progress. I'm gonna try to have the bulk of the comments by the end of the week and then it's a really next week to see if we can get everything finished up. + +Denis Lelic: cool + +Denis Lelic: one more update for you The stats page. I know you're already worked on it. + +Denis Lelic: But both Maxes from Team cloudmouse are working on that page so you don't have to do. Any more work on it? So I know we talked about there needs to be done some UI refinements. But those will be done by. Max from cloudmouse + +Denis Lelic: Is that okay? + +Piyush Choudhary: On the website? + +Denis Lelic: Sorry. + +Denis Lelic: On the website. Yeah, so not. + +Piyush Choudhary: Cloud most + +Denis Lelic: network activity page or stats Page that's going to be taking care of by Max from cloudmose. So you don't have to do any more work on it. + +Piyush Choudhary: so I did updated the UI. Yes for that structure so you can be seen here. So it's almost complete. So we will stop our work here. This can be taken care of by Max. + +Denis Lelic: yeah, the thing is he already started working on it as well and We just want to make sure it's not duplicating the efforts. So we agreed he's gonna take care of it and… + +Piyush Choudhary: + +Denis Lelic: the only information you will receive from him as how will users reach that page on the website. So we might just need to add Called stats or it's still gonna be reachable through about Akash page. + +Piyush Choudhary: you okay, but + +Denis Lelic: I'm gonna have that information today and a couple of minutes. So I'll let you know. + +Denis Lelic: Yeah, and as Tyler mentioned in this chat section, it's gonna be called stats t network. We just have to only figure out how user users will reach that page from. + +Piyush Choudhary: Yeah, so for that case as you said about most I mean Max is already working on it. So we just have to add a button in the now and just have to add a link so it's not that work so we can always add any type of buttons so we just can say and stats and whenever someone who started takes time to the start of course.net. + +Denis Lelic: cool Sounds good. + +Piyush Choudhary: So the stats that is there on the network activity about section. Is it required or they will have to remove it. + +Denis Lelic: I will provide that information today after my next meeting. + +Piyush Choudhary: And what about the pricing page? + +Denis Lelic: The pricing page is going to stay as it is. + +Piyush Choudhary: It's okay. + +Denis Lelic: So no worries about that. + +Piyush Choudhary: what about the provider page in the ecosystem? + +Denis Lelic: That's gonna stay there as well. So the only thing is the stats. + +Piyush Choudhary: So yeah, I think that's fine. So we keep the work till now. So we already implemented all the things only the subsections will not implemented I think. Those can be taken care in the scratch sort of network. So. We will keep doing it all. + +00:25:00 + +Denis Lelic: Okay, cool. + +Denis Lelic: Yeah a bit shorter today. I hope you guys don't mind and for unfortunately, I have a conflict, but if you want to discuss anything else without me you're free to but otherwise we'll meet next week for the working group for the docs and we can continue our discussion about the menu and everything that goes with it there. + +Tyler Wright: Here. sorry, Denis Pierce and others does this time on Tuesday work for you? early Tuesday morning. … + +Piyush Choudhary: it works. + +Zach Horn: Yeah, it works for me. + +Tyler Wright: or peers like Elite in the afternoon? Who's the + +Piyush Choudhary: Okay. + +Tyler Wright: Okay, perfect. So I'll look this up a session for that. I just got a confirm with one more stakeholder on the core team. + +Denis Lelic: Sounds good. So thanks everyone for joining. I'll see you next in the next one. + +Thomas Greco: Thank you. + +Denis Lelic: Thank you. + +Thomas Greco: Thank you everyone. Have a good day. + +Tyler Wright: Thank you. + +Thomas Greco: All right. + +Piyush Choudhary: Thank you. + +Zach Horn: thanks guys take + +Meeting ended after 00:26:33 👋 + diff --git a/wg-akash-website/meetings/020-2023-12-07.md b/wg-akash-website/meetings/020-2023-12-07.md new file mode 100644 index 00000000..68470e08 --- /dev/null +++ b/wg-akash-website/meetings/020-2023-12-07.md @@ -0,0 +1,496 @@ +# Akash Network - Akash Website Working Group (WG) - Meeting #20 + +## Agenda +- Website Revamp Progress. +- Discussion on Website Revamp: + - Updates on Stats Page + - Documentation structure + - Launch Timeline + +## Meeting Details +- Date: Thursday, December 07, 2023 +- Time: 6:30 AM PT (Pacific Time) +- [Recording](https://bmafqxmmyqqxc65uxwkpgetv4r6yzlx6g3wsfzqqahumvzo4hrmq.arweave.net/CwBYXYzEIXF7tL2U8xJ15H2Mrv427SLmEAHoyuXcPFk) +- [Transcript](#Transcript) + +## Participants +- Denis Lelic +- Piyush Choudhary +- Emmanuel Arthur +- Tyler Wright +- Zach Horn + +## Meeting Notes +- Piyush and Human HQ team leading Website revamp efforts, collaborating with core team and Akash community. +- Funding secured from the community pool in September for the revamp. +- Recent meeting with Sig documentations focused on optimizing Docs 2.0 integration and UX decisions. +- Design decisions outlined, and implementation in progress by Piyush's team. +- Denis and Zach leading website efforts in visual and written communication. + +### Piyush's Updates: +- Ongoing implementation of content and UI updates. +- Discussions and decisions on Docs UX and structure implemented in the code. +- Plans to share more details next week. +- Zach inquired about pages that are essential for the launch and those that could be deprioritized. +#### Piyush's Response: +- Everything is prioritized, but there are inconsistencies in Docs content. +- Lunar's team is responsible for content, and there are incomplete states, inconsistencies, and missing components. +- Piyush's team will review official documentation and refine the content with clear directions. +- Zach mentioned contributors interested in contributing to docs and suggested a live session for guidance. +- Once the website is live, there will be a guidance session for community members on updating content. +- Creating Markdown files similar to previous methods, with some syntax considerations. +#### Organization of Tutorials: +- Piyush proposed having tutorials in a separate folder under the Docs, following the new UX. +- Contributors can create tutorials in this dedicated folder, enhancing educational resources. +- Piyush suggested discussing this organization approach as progress is made, making the community aware of the contribution process. +- Zach expressed approval of the previous discussion on tutorials and documentation organization. +### Discussion on New Website Launch Timeline: +- Tyler acknowledged the progress and raised a concern about the potential delay in the timeline. +- Mentioned the initially discussed launch date of December 15th, but noted that decisions around Docs 2.0 might have slowed the process. +#### Piyush's Response on Launch Timeline: +- Piyush suggested linking a button to the existing official documentation even if Docs is not entirely ready. +- Piyush proposed making changes behind the scenes and replacing the button once the new Docs is completed and approved. +- Suggested aiming for a perfect Docs content and UX by the end of December. +- Tyler sought confirmation that they could launch on December 15th and then transition to the new documentation later in the month. +- Piyush confirmed, stating that if everything is ready, they can launch by December 15th, but a delay until the end of the month is possible if needed. +### External Links Concerns: +- Tyler raised concerns about external links, mentioning the stats page at Akash/Network. +- Acknowledged the preference for users to have the most up-to-date documentation but recognized potential inconsistencies. +- Zach and Tyler discussed the pros and cons of pushing back the launch date. +- Zach leaned towards not delaying the launch, keeping the external link temporarily and switching it over as soon as possible. +- Piyush supported this approach and emphasized addressing inconsistencies and missing guidelines in the current Docs. +### Discussion on Contributors Guidance Sessions: +- Tyler expressed enthusiasm for the idea of guidance sessions, suggesting sessions for insiders and the public. +- Proposed waiting until the new Docs are live for a comprehensive walkthrough on contributing to various sections. +- Suggested planning the sessions at the beginning of the new year for a secure and cohesive presentation. +- Zach supported the idea, emphasizing the inclusion of walkthroughs for docs, blog content, and the Community contributors page. +- Participants expressed agreement with the proposed timing for the comprehensive walkthrough. + +### Question on AI/ML Highlighting: +- Denis asked Zach if they are highlighting anything specific from AI/ML for the first launch or focusing on external links. +- Denis suggested bringing AI/ML components into the ecosystem showcase page. +- Piyush explained limitations due to different code bases and suggested linking to external pages. +- Denis proposed adding a button with an arrow to indicate external links for components like SDXL. +- Zach mentioned Mistral coming soon and suggested highlighting various model SDXLs. +- Zach proposed exploring community-developed models and blending them with their own apps. +- Recommended starting with SDXL and Mistral for the first launch. +### Discussion on Ecosystem Page Elements: +- Zach discussed exploring a new model and checking its feasibility with Julius. +- Denis mentioned the need to pick a project for the "Projects Deployed On" section from the ecosystem page. +- Zach agreed to review the existing projects and select one for the section. +- Denis suggested seeking input from the community or Akash team for the selection. +- Zach agreed to put together a shortlist and consult with Anil and Greg. +- Denis mentioned running the testimonials and impressions page by Anil, Greg, and Chang. +- Zach acknowledged, committing to adding to the list and contributing to proper population. +### Akash Edu and Community Contributions Discussion: +- Denis questioned the purpose of putting Akash Edu content behind an OmniFlex wall, expressing doubts about user payments and suggesting a discussion with Adam. +- Denis expressed the need to make some Akash Edu content more public, possibly directly on YouTube or other accessible platforms. +- Zach acknowledged the need for easily accessible content and agreed to discuss with Adam about making certain content more public. +- Piyush inquired about the difference between Akash Edu and Community Contributions on the community page. +- Zach explained that Akash Edu is a mild credentialing program with collectibles at the end to showcase completion. +- Emphasizing its structured nature compared to open and unstructured community contributions. +Community Contributions Implementation: +- Piyush explained the implementation of Akash Edu and Community Contributions on the website, detailing the structure of contribution cards. +- Piyush proposed keeping a hold on Akash Edu until directions are clear, while Community Contributions are actively implemented. +- Zach suggested looping in Adam for opinions on AkashEdu but recommended implementing it with placeholder content as major adjustments. +- Piyush agreed to the approach and confirmed the ongoing implementation of Community Contributions. +### Dark mode Version of the Website: +- Denis inquired about the progress of the dark version of the website. +- Piyush explained that the dark version would be tackled once the light version is 100% complete. +- Clarified that dark version implementation will take around three to four days and is planned after finalizing the light mode version. +- Tyler expressed concern about having the dark mode icon present in the navbar if dark mode won't be available at launch. +- Suggested removing the dark mode icon until it's ready to avoid confusion. +- Piyush agreed to remove the dark mode icon. +#### Broken Links +- Denis brought up a note from the previous week about broken links on the current website, inquiring if this would be resolved with the publication of the new website. Piyush confirmed that the issue would be addressed. +#### Stats/Network Activity Page: +- Denis mentioned still needing information about the positioning of the Stats/Network Activity page, questioning whether it would be in the menu bar. +- Piyush suggested having a link named "Stats" in the navbar, directing to the external link stats.akash.network. +#### Network Activity Page Implementation: +- Piyush informed Denis that the cloudmos team is working on the network activity page, which will be hosted at stats/network. +- They discussed potential plans for linking to this page from the new website's menu. +### Other Matters Discussed +- Tyler mentioned sharing the [shop link](https://shop.akash.network/) and explained that he suggested adding a shop link to the footer under the Akash logo, alongside other social media links. +### Action items +- Piyush and his team to continue working on changes behind the scenes and aim for a perfect Docs content and UX by the end of December. +- Piyush and his team to review the entire documentation, minimizing inconsistencies and missing guidelines. +- Group agree to proceed with the launch and adjust documentation links over time. +- Group Plan to hold documentation contribution sessions for insiders and the public in the new year. +- Zach to put together a shortlist of projects for the "Projects Deployed On" section. +- Denis to seek input from the community and Akash team on project selections. +- Zack to discuss content accessibility and updates of AkashEdu with Adam. +- Group to highlight a blend of AI/ML components on ecosystem showcase page with external link. + + +# **Transcript** + +_This editable transcript was computer generated and might contain errors. People can also change the text after it was created._ + +Tyler Wright: All right, welcome everybody to the working group for the Akash website as mentioned. This is a weekly working group that focuses on the Akash Network website revamp. Piyush and his team human HQ have been leading efforts on the redesign of the website working closely with members of the core team as well as general Akash Community anybody that wants to participate in this working group can and has been over the past couple of months. Think about piyush's team were able to get funding from the community pool for the revamp some time around September and again have been working consistently and diligently and very closely with this working group to stay alive on design Direction deliverables. + +Tyler Wright: And all things around again the website revamp, most recently. There was a meeting that just happened yesterday at the crossover between the working group Akash website and Sig documentations to make sure that docs 2.0 integration was one that was optimized and seamless there was a couple of ux decisions that were made yesterday around how things are laid out on the docs Pages as well as how engineering documentation is integrated with the Rest of the documentation for users tenants and providers and validators So again, although it'll be a recording they'll be made available shortly, but piyush and his team have the design of decisions from that meeting outlined and are starting to work on implementation. + +Tyler Wright: Denis and Zach who are on this call lead much of the website effort around visual communication and then written communication as well. So I'll hand it over to Dennis to get us kicked off with this week's agenda. + +Denis Lelic: Thanks, I would actually suggest if piyush share his updates any questions before we start with anything new and open any new discussions. So piyush. Go ahead. Thank you. + +Piyush Choudhary: So yeah, so as per our previous discussions and planning so we are right now implementing that content updates around website and also the UI updates as per the situations and feedbacks that we caught on figma. So there's going on consistently and we are working on the UI changes as well the feedback as well as the content updates. So things can be tracked or live on this link. And yesterday we got a discussions or decision about + +Piyush Choudhary: the discussions and decisions about a dog see you exchanges. So we'll be implementing those ux changes in the code and we'll share more dates next week. + +Piyush Choudhary: and in some cases it might happen that as we are reaching the date of making website live officially there might be some things that may not be perfect. But I think we can move forward with making it live after considerations from all team members and we can continue fixing minor steps that might be missing while doing the things. That's all from my site today. + +Denis Lelic: Thank you. Thanks piyush. Yeah Zach. + +Zach Horn: Yeah, quick question for you be to your point on launching the site maybe with some main features ready. but still some punch up that we need to do over time, which pages are the priority there. mean, there's the obvious ones like the homepage Community token Etc. But which Pages do you think we definitely need for the launch in which do you think could be deep prioritized? + +Piyush Choudhary: everything is so prioritized but I think there might be some inconsistencies and Dogs content, especially we can implement the dog site, but the content that is being written is being done by lunar stream, so there is a lot of income State inconsistencies and missing components and it comes to the content. So me and my team will be going through the official documentation and we'll plant things out in refining the content of the talks with as of clear directions as possible. + +00:05:00 + +Zach Horn: Got it. Okay. Thank you. + +Piyush Choudhary: And also once we make things live or once we make a rep of a black we will also have some guidance session for all the community members how to update contents it it's very easy. You just have to create the markdown file in similar fashion that you guys were doing in the previous and there are just some syntax that needs to be taken care of. So I was just address those once we get close to the life version of the website. + +Zach Horn: That sounds great. there's a number of contributors that are looking to contribute to docs. So yeah, it would be great to have a live session where we can pull those folks in and just give them a tour, let them know + +Piyush Choudhary: Yeah. I… + +Zach Horn: how to contribute. + +Piyush Choudhary: yeah, and also as per day yesterday discussions, I was thinking since we will have the two dogs right here. for example, I saw some of the contributors are planning to contribute and making the tutorials. So instead of making things like scattered, what we can do is it's very easy to do. It's all being part of the ux that we have made from scratch. So there will be a different folder that we can add as a category called as tutorials and inside that tutorials things will look like this only the contributors can make different kind of tutorials and we will be Ball similar to what the talks are visible right now. So I think that could be discussed as we progress and we can make aware about to the community like this is how they can contribute and add your educational resources to the docs itself in a separate. + +Piyush Choudhary: Column in a separate category, of course. + +Zach Horn: That sounds great. + +Denis Lelic: Thai I saw your hand went up + +Piyush Choudhary: Yeah, Tyler you can. + +Tyler Wright: Yeah, everything looks great much appreciate all the work. My question was I think originally we had talked about a timeline of potentially December 15th, which I think is a week from tomorrow. I know that this working group and some of the decisions around docs 2.0 have which are important decisions to be made but I have maybe slowed that process a little bit. Have you thought about a potential timeline that makes sense for you and your team to launch the site? + +Piyush Choudhary: So what even if the dogs is not completely ready or if we can do is we can link this button to the official documentation that is already life on dog struck network and we can access the talks changes on this link manually and whatever and we can keep on making the changes behind the scene and once it's completely done and approved by all the community members and for members we can just replace this button instead of taking talks about Network to slash talks. And I think as considering the ux as well as the content refinements. + +Tyler Wright: Perfect. So + +Piyush Choudhary: I think we can say by 25 or by end of December. We can have a perfect Dogs content as well as the US. + +Tyler Wright: So I guess to that point you're saying that you would suggest if Zach and Denis feel comfortable, we can launch December 15th and then link to the old documentation and then link to the newer documentation towards the end of the month. Is that… + +Piyush Choudhary: Yep. + +Tyler Wright: what you're saying? Okay. + +Piyush Choudhary: So if everything is ready, we can definitely launch by 15, but right now the lands are being made to make it launched by 15, but if something comes off like some UI ux issues or something, then we can definitely maximum. We can have a delay till end of the summer. + +Tyler Wright: Sounds good. Go ahead Zach. + +Zach Horn: Yeah, I understand the logic. Of maybe pushing back a few weeks what if we launched the site with the new Doc site included and… + +Piyush Choudhary: right + +Zach Horn: then just update over time, So if we're talking about a two-week delay What do you think about just launching the new docs as they are maybe linking to the old within the new docs page just so we can launch the site with no external links. That's the only thing I'm thinking around because if we're gonna have this big website launch, I think it would be good to avoid external links if possible. + +Piyush Choudhary: So yeah, we'll make sure that then. The things that are there return I will just check those and try to make them as less as possible and then we can launch with the current docs new dogs only and we can keep on making this changes as we progress. + +00:10:00 + +Zach Horn: Okay, that sounds good. And yeah I see your comments. So we're gonna have external links either way, okay. + +Tyler Wright: I believe the stats page is going to be stats at Akashi Network. I think that you brought up a good point about. The external links but I was just like putting that out just for contact thick. everything else I think is gonna be inside the website like ecosystem all those pages, but I think it's still gonna be stats network. That's linking out. am I only my … + +Zach Horn: Yeah, that's good. + +Tyler Wright: sorry to cut your uncle. my only other fear is if there are some inconsistencies with a newer documentation And then much of the core team is out around the holidays. Then I prefer users to have the most up-to-date documentation, but I don't feel so strongly about that that I could like it down that Hill… + +Piyush Choudhary: Yep. + +Tyler Wright: because I understand what you're saying, too. + +Zach Horn: Yeah, I don't feel super strongly about it. So as we're talking this out hearing a little bit towards not pushing back the launch day because I know we do want this live and there's been so much work done already. So maybe we do just set it keep the external link and then we'll switch it over as soon as possible. + +Piyush Choudhary: Yeah that's what I suggested right now. + +Zach Horn: Yeah. + +Piyush Choudhary: When I open I was reading the content so there is a lot of inconsistences and also some contentious missing some guidelines are missing so it would be great. So what me and my team will be going through the whole documentation all content of dogs. What Akash dot Network and we'll make the content as a fun as possible very close to the official documentation. So I think we can keep the dogs to this link for now. And once the new docs is completely ready for the live versions We can just change or to the existing website only. + +Piyush Choudhary: without external links + +Zach Horn: Yep, sounds good. + +Tyler Wright: I think to that point iyush. I really like the idea about having a session or maybe even a couple of sessions maybe we do something as a part of the inside or office hours for insiders. And then maybe we do a separate session that's open to the public. I love that idea. I would just say maybe in terms of timing. We wait until the documentation the new docs live so that we can do a comprehensive walk through this is how you can contribute to the blog. I can contribute to the community contributions page is that you can contribute to documentation. I suppose to having it fragmented. So maybe we do that top of the new year once everything like secure, but I love that idea. + +Piyush Choudhary: sure. + +Zach Horn: Yeah, that's a great point because if we're gonna have a walk through for contributors, it's stocks obviously, but also also the blog and also that Community contributors page for sure because I know there's basically an equal number of folks that want to do docs and some that want to do blog content and some that are gonna publish to that Community contributor page. So doing that all in one I think is something we want to wait for. + +Piyush Choudhary: So yeah, so we are progressing good for the UI changes as well as the content updates that are being requested. But in future we have structured the things in such a way that even non technical users who are able to update the contents. For example if someone wants to update let's say this so they don't have to go through the technical details. They can just update this text in the markdown itself. + +Tyler Wright: and then… + +Denis Lelic: Yeah, that sounds good. + +Tyler Wright: and then the no don't question. I won't even put it on a record. + +Tyler Wright: + +Denis Lelic: One thing we have to focus I think pretty much everything from the UI ux stuff is clear for piyush and his team, but for the rest of us, I think we should focus more on. + +Denis Lelic: Content revision and providing links. For example, maybe I'll just share my + +Piyush Choudhary: Yep soil for example in the homepage we can link this to a doc space. + +Denis Lelic: yeah. + +Piyush Choudhary: I mean the ecosystem page and where this will be going so these are the links updates that be you guys can plan and… + +00:15:00 + +Denis Lelic: Yeah. + +Piyush Choudhary: data so we can update things accordingly. + +Denis Lelic: Maybe a question here for Zach. Can you see my screen? + +Zach Horn: Okay, yeah. + +Denis Lelic: So one question are we highlighting anything from AI ml stuff so sdxl and chat. + +Denis Lelic: For the first launch, maybe are we just focusing on external links or? Could we bring that into the ecosystem showcase? Page which is this one, for example. where users + +Piyush Choudhary: so there is a + +Zach Horn: Good. + +Piyush Choudhary: so there is one point we cannot bring that to the ecosystem page because if it's a working tool with a completely different code base, so we can only link that to the external links. It cannot be a part of the current website because it's a completely different texture that box with the AIML in producing the images. And if you want to just showcase how the UI looks of a sdxl that can be done. But you want to embed the sdx is sdxl UI into the current website, then it is not possible. + +Denis Lelic: Okay, Yeah, maybe we just provide a button here with that Arrow something like this which is going to indicate it's going to open a external link. But yeah, we have sdxl chat is coming. Do we have something else to highlight here Zach? + +Zach Horn: Yeah, definitely. So we have Mistral coming soon. It's gonna be live in the next week or so. I would say we highlight various model sdls for now. I can go through what we have currently and see what would make most sense there. But I think we do like a blend at least for the AI and L stuff is our two apps that we have developed currently and then we do a couple models and then potentially we see if we can highlight any other developments from the community. I can take a look to see what's ready today, but I think we just do a mix of those things. so if I'm looking at your screen right now, we do xdxl first, maybe mistral's the second one we could do an stxl or an sdl for. + +Zach Horn: It's a good question. I mean, there's that new model that we could maybe do I can take a look and see if Julius can create that STL shortly. I guess. We just have to see if it's stock rised but Yeah,… + +Denis Lelic: Okay, cool. + +Zach Horn: I see what you're saying. let me take a look and just see what we have currently and I'll also knows over to you. + +Denis Lelic: Thanks and maybe for this section here for projects deployed on We are all also have to I guess pick one of them from the ecosystem page So at the moment we have osmosis Chi I'm presearch but these are something I just grabbed. + +Denis Lelic: so maybe can I ask someone from the community or the court team which of these would be like? + +Denis Lelic: a good project to feature in this section + +Zach Horn: You're looking for production products that are deployed on + +Denis Lelic: yeah, basically what we have in the ecosystem page now, so That's from projects from these categories. + +Zach Horn: Gotcha. + +Denis Lelic: So I can ask a Neo dragon and others what their thoughts are, but I was just wondering if you have a favorite Thai Zach. You can always drop your favorite here and… + +Zach Horn: Yeah, I can. + +Denis Lelic: we can discuss. + +Zach Horn: Sounds good. I'll put together a short list. But yeah, let's run by Neil and Greg to see what they think. + +Denis Lelic: cool and the same goes for testimonials and the Impressions paid section here. We could run that by anyo and Greg as well. Maybe Chang to that's something I've already shared and Zach. I know you're aware of it. So whenever you find time, maybe just add to that list and I'll make sure I'll reach out to others. So this thing is + +00:20:00 + +Denis Lelic: properly populated + +Zach Horn: Yeah, we'll do. + +Denis Lelic: And there's a bunch of this stuff throughout the website. + +Piyush Choudhary: + +Denis Lelic: For example, the Akash edu stuff. That's something I was questioning. But I have to talk to Adam. I don't know. What's the purpose of putting this edu content behind this? omniflex wall It's not something user users gonna pay for I'm sure. + +Denis Lelic: maybe it's good for collecting leads, but why not just share that on YouTube or whatever blog or Yeah, but that's another discussion to have maybe when Adam is around. + +Zach Horn: Yeah to stand in for laws. I think is logic was you it's like a mild credentialing program. So it's like you go through the content you get this, collectible at the end and it just showcases that you've gone through and completed the content. So it's almost like a certificate of completion. I do agree for… + +Denis Lelic: Okay. + +Zach Horn: what it's worth it. Maybe we should surface some more of that content outside of that system. Maybe just directly on YouTube. Maybe there's Samples that he has that we can make a little bit more public. let's chat with him and see what he thinks because I do agree that there should be some easy to access content that people can just view without going through that, but I also think he has Some reasoning why he wants it the way it is currently. + +Denis Lelic: Okay, Yeah, so basically what we have to do now is populate all of the website with Proper links and content and I've also started updating the typeforms. Not really website related stuff, but I went through the first one yesterday. I think it's + +Denis Lelic: the subscription type forms + +Denis Lelic: I'll just go one by one and make sure they're all up to date. With this new direction, we're set up here. Yeah piyush. + +Piyush Choudhary: on community to pays what is the difference between Akash at you and Akash conribute, Community contributions + +Denis Lelic: the community Okay,… + +Zach Horn: I'll take that one. yeah,… + +Denis Lelic: go ahead. + +Zach Horn: either of us could but I'll volunteer. The community contributions are the original idea was that it was an open source platform for people to essentially they want to write a blog about Akash. + +Denis Lelic: Thanks. + +Zach Horn: They can do that and do a PR to the repo to have that published on the site without going through our quote unquote official channels edu was waz's idea to do more of an official credentialing program around structured content. So he was going to work with Partners on the flicks was the first one where you essentially go through this, sign up process you go through the content and then you get this collectible at the end the Showcase that you gone through that content. So edu is just a structured program. The community contribution is very open and on structured. + +Piyush Choudhary: If so, basically in Akash hit you and community. So the structure that works in our implementation is in permitted a Implement Akash and it will be similar to the community contributions. So in these cards. I think the title there are few details that needs to be submitted by the + +Piyush Choudhary: Uses those who wants to add the card so they are five items that needs to be added. So one is the image one is the author name then the title of the contribution the description of the contribution the date and the category. So it's with the implemented here and it will be linked to the external source and if let's say we user wants to write a blog right so they can write the blog in the blog page with a community contributions tag. So it will be tagged as Community contributions and if we short list through all the community contributions blocks will be shortlisted on the Block page. + +Zach Horn: Next sense. let's Loop in Adam as well because I'm sure he's gonna have some opinions on what he wants on the Akashi to you page, but we can chat with him and just circle them and see what he thinks on that. but I understand what you're saying in terms of the website structure. + +Piyush Choudhary: So now I think our past schedule is added recently or a few days ago. So I'm keeping a hold on Akash at you and once directions are clear. We can Implement akashed you page for now. I'm only keeping the community contribution space. Is that fine? + +00:25:00 + +Zach Horn: I would say we could implement it right maybe just put some placeholder content and… + +Piyush Choudhary: + +Zach Horn: I don't think there's gonna be any major changes. It's just I think we want to Loop in Adam to see if he has any but I don't think there's going to be any Major adjustments to… + +Piyush Choudhary: Okay. + +Zach Horn: what you have here. + +Denis Lelic: Yeah. + +Denis Lelic: Sounds good. Piyush. I have one question. What about the + +Denis Lelic: Dark version of the website. So we have the light one here. how's that going? + +Piyush Choudhary: Yeah, it will be tackled. Once the light version is hundred percent Complete because we cannot implement the dog versions in parallel. when the light version is going on. We have to write the functions accordingly. So once the light version is complete and finalized we will just implement the dog versions. So the dog version implementation will take around maximum three to four days and slide version is in a presentation. + +Denis Lelic: Okay, cool Ty I see you share the shop link anything you want to say about it? + +Tyler Wright: Yeah, I just put a message to piyush above it. I was just asking in the footer of the site. Where under the Akash logo is a Twitter the GitHub the Discord and the YouTube. I was just asking I forget just put a Shop link under that in the footer for folks. I would also say in regards to the website launch I get what you're saying piyush about the + +Tyler Wright: about the dark mode. If we are not going to be launching with dark mode. Then I just think that we should remove that icon just so it doesn't because it's so present on the top of the nav bar if it just remove it and we can just say we can let people know what's coming soon or for the first until it's ready. We just won't have it and all of a sudden it'll appear or something like that, but I'd rather people not click things and they just don't work if that's possible. + +Piyush Choudhary: Yeah, I will remove the dark mode. + +Denis Lelic: cool + +Zach Horn: I agree with not having people click things that don't work. But when do we have a timeline for dark mode? Because I know I'll speak for some folks inside the company. They're gonna want dark mode. So do we have a timeline on one? That would be live? + +Piyush Choudhary: Yes, so as I said, once the light mode is completely done. We will take around maximum three to four days to implement the dark mode. + +Zach Horn: Got it. Okay. Thank you. + +Tyler Wright: I guess my question there is Denis. I just go off mute. I know that we're moving into the phase where we're focusing on a lot of copy edits and that kind of stuff and fine-tuning. When do we think there will be done with the light mode just so I understand we think we'll be done by launch or do you think that will be done with the light mode and just focusing on copy Monday of next week and then dark mode may be ready by launch on the 15th. Piyush I was a question for yourself. + +Piyush Choudhary: So I think we are only working on the light mode right now because there is a lot of dates that we have in our hand content link updates that there are UI ux changes as well. So I think by 15th, it's not possible to have the dark mode. We can only have the light mode for now and once everything is done with the light mode we can launch a little bit. If something goes missing we can have a plan as we approach 15, so There might be a little bit delayed into some content updates or maybe links updates, but I will try to not make those delays. So I think initial launch will be just with the light mode, but I will try to have the top mode as well. + +Piyush Choudhary: if The dark mode will not be live. Then after the launch. It will take maximum three to four days to implement the dark mode for us. + +00:30:00 + +Tyler Wright: All does anyone have any objection of me adding? arm working group Akash website meeting for next Tuesday so we can start to see where we are and maybe we don't even need one Thursday, but we could just have one for next Tuesday and then maybe meet again on Thursday or Friday when we're thinking about launching and we'll make that determination on I'll add some time on Tuesday around this time. For us to have a working group session. I'll just added to the calendar. + +Denis Lelic: Cool, sounds good. Yeah. Piyush. I have a couple of questions regarding the dart mode, but I'm just gonna ask those on Discord so we can chat there. + +Denis Lelic: It's going through my notes quickly. + +Denis Lelic: Yeah, I made a note last week regarding some broken links. That are happening on the current website. So probably what that's not going to be an issue when you published a new one, right? + +Piyush Choudhary: yeah, that will not finish. + +Denis Lelic: Okay, that's cool. + +Denis Lelic: Yeah, I'm piyush I still owe you information about the stats or network activity page. Where it's going to be positioned, is it either menu or… + +Piyush Choudhary: + +Denis Lelic: the network but yeah, I still don't have that information. But as soon as I Receive it I'll let you know. + +Piyush Choudhary: So yeah, I have the information that loud most team is working on the network activity page and it will be hosted on stats start network as well last meetings, right? + +Denis Lelic: Yeah, that's true. But I'm aware of that. But I just don't know. What are the plans. For linking that page where's the link? Is it in the menu bar? or + +Piyush Choudhary: I think we can keep the link in the navbar itself where we just name it at Stats and just point to the external link starts to talk Network. + +Denis Lelic: Okay, cool. I'll see how that works in the menu and also talk again with the team that's working on it to see what are their thoughts and plans for this. + +Piyush Choudhary: also, we have the working network activity page on about which already + +Denis Lelic: Yeah. Yeah, I saw that which is great to have a backup. What about Some sort of this announcement board and pop-ups. + +Denis Lelic: Can be Implement those maybe later after we launched. + +Piyush Choudhary: Yeah, we can Implement those. as we have ww everything from scratch. + +Denis Lelic: I know I was just + +Piyush Choudhary: We have all the flexibilities, but sometimes what happens is when we are used as so as we are using marked on for example, sometimes we can have the limitations due to the markdown stuff. But we have all the flexibility to do anything with the website as it is being made from scratch. + +Denis Lelic: Yeah, that's cool Zach. I'm sure you have ideas for some sort of a pop-ups or… + +Piyush Choudhary: but + +Denis Lelic: something that we can use from marketing efforts + +Zach Horn: Yeah, definitely. + +Denis Lelic: which is Good to know and good to have. + +Zach Horn: For sure. + +Denis Lelic: One thing I haven't seen on the website is this support piyush. Do you think we could have that? + +Piyush Choudhary: is there just yeah,… + +Denis Lelic: for the launch + +Piyush Choudhary: it's just We already have it. Just click this link. and the sharing + +Denis Lelic: Cool great. Perfect. + +00:35:00 + +Denis Lelic: And the same goes for this one if there's a dead end or… + +Piyush Choudhary: Yeah, it's our yeah,… + +Denis Lelic: are happening. + +Piyush Choudhary: it's there. You can just type in some random request and it will display. Wait, let me save it it is just running or not. Yeah, it's just playing let's say a few type in some random requests like this. I dropped in the link in the chat. + +Denis Lelic: Thanks. + +Denis Lelic: I just saw we don't have a perfect text here now Zach I should take you. So whenever you have time. + +Piyush Choudhary: but + +Denis Lelic: If you could provide. one cool. + +Zach Horn: Yep. there. + +Denis Lelic: Yeah, I think we pretty much covered everything for today unless there's some questions. + +Denis Lelic: sounds like it's going to be a short meeting this week, but doesn't matter. I'm glad everything is + +Denis Lelic: progressing well and piyush and his team are doing a great job. + +Denis Lelic: cool + +Denis Lelic: So if there's not any questions left or discussions we can just wrap it up for today. we're gonna talk on Discord as well. + +Denis Lelic: So, thanks everyone for participating today. + +Tyler Wright: Thank you. Yes. + +Denis Lelic: Your next week. + +Zach Horn: Thanks guys. Take care. + +Piyush Choudhary: Thank you. Thanks guys. Have a good day. Bye. + +Emmanuel Arthur: Bye. + +Meeting ended after 00:42:00 👋 + diff --git a/wg-crew3/README.md b/wg-crew3/README.md deleted file mode 100644 index 6521273f..00000000 --- a/wg-crew3/README.md +++ /dev/null @@ -1,30 +0,0 @@ -# Akash Network Crew3 Working Group - -This working group is to launch an Akash account on Crew3.xyz, a community builder platform. The aim of this group is to increase awareness about Akash in gamify form, and create tasks for the community based on their skill level. e.g influencer, developer, provider, content creator etc. - -The working group is created to work on the proposal to see what support is needed, outline the goals and forecast outcome, decide on the user rewards, points, ladder system and time. Based on this metrics, we will be able to see the full picture and the success of the program. - - - -## Meetings - -| Meeting | Time | Notes | Transcript | Recording -| --- | --- | --- | --- | --- | -| #1 | Friday, February 17, 2023 08:30 AM PT (Pacific Time)|[Link](https://github.com/akash-network/community/blob/main/wg-crew3/meetings/001-2023-02-17.md) |[Link](https://github.com/akash-network/community/blob/main/wg-crew3/meetings/001-2023-02-17.md#transcript) | coming soon - -## Leads - -- Andrew Gnatyuk -- Robert Del Rey - -## Contacts - -- [Discord](https://discord.gg/6ffnaGay) - - -## PRDs and other documentation -- PRD - -## Related SIGs - -- [community/sig-community](sig-community) diff --git a/wg-events/README.md b/wg-events/README.md index 36ecba29..7198cb39 100644 --- a/wg-events/README.md +++ b/wg-events/README.md @@ -3,18 +3,24 @@ title: " 2023 Events - Working Group" date: 2023-2-10T00:19:20-08:00 --- -# Akash Network - 2023 Events - WG +# Akash Network - Events - WG -This working group is to discuss events to attend and ways to encourage community attendance. +This working group is to discuss events to attend, year by year, and ways to encourage community attendance. -## Meetings +## wg-events 2023 Meetings | Meeting | Time | Notes | Transcript | Recording | --- | --- | --- | --- | --- | | #1 | Friday, February 17, 2023 10:30 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/wg-events/meetings/wg-events-001-2023-02-17.md) | [Link](https://github.com/akash-network/community/blob/main/wg-events/meetings/wg-events-001-2023-02-17.md#transcript) | Coming Soon | #2 | Wednesday April 19, 2023 10:00 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/wg-events/meetings/wg-events-002-2023-04-14.md) | [Link](https://github.com/akash-network/community/blob/main/wg-events/meetings/wg-events-002-2023-04-14.md#transcript) | Coming Soon -## Leads + +## wg-events 2024 Meetings +| Meeting | Time | Notes | Transcript | Recording +| --- | --- | --- | --- | --- | +| #1| Wednesday October 25, 2023 10:00 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/wg-events/meetings-2024/001-2023-10-25.md) | [Link](https://github.com/akash-network/community/blob/main/wg-events/meetings-2024/001-2023-10-25.md#transcript) | [Link](https://bts4wsldpu6iuvcvdvsbncztc7whshy4izdsugaho3j74nq2pcla.arweave.net/DOXLSWN9PIpUVR1kFoszF-x5HxxGRyoYB3bT_jYaeJY) +| #2| Friday November 03, 2023 10:00 AM PT (Pacific Time) |Coming Soon | Coming Soon | Coming Soon +## Lead Adam Wozney (Overclock Labs) diff --git a/wg-events/meetings/wg-events-001-2023-02-17.md b/wg-events/meetings-2023/wg-events-001-2023-02-17.md similarity index 100% rename from wg-events/meetings/wg-events-001-2023-02-17.md rename to wg-events/meetings-2023/wg-events-001-2023-02-17.md diff --git a/wg-events/meetings/wg-events-002-2023-04-14.md b/wg-events/meetings-2023/wg-events-002-2023-04-14.md similarity index 100% rename from wg-events/meetings/wg-events-002-2023-04-14.md rename to wg-events/meetings-2023/wg-events-002-2023-04-14.md diff --git a/wg-events/meetings-2024/001-2023-10-25.md b/wg-events/meetings-2024/001-2023-10-25.md new file mode 100644 index 00000000..d67a23ae --- /dev/null +++ b/wg-events/meetings-2024/001-2023-10-25.md @@ -0,0 +1,406 @@ +# Akash Network - 2024 Events Working Group (wg) - Meeting #1 + +## Agenda +- Review of 2023 events and lessons learned. +- Early planning for 2024 events. +- Review and discuss preliminary list of potential events for 2024. + +## Meeting Details + +- Date: Wednesday, October 25, 2023 +- Time: 10:00 AM PT (Pacific Time) +- [Recording](https://bts4wsldpu6iuvcvdvsbncztc7whshy4izdsugaho3j74nq2pcla.arweave.net/DOXLSWN9PIpUVR1kFoszF-x5HxxGRyoYB3bT_jYaeJY) +- [Transcript](#transcript) + +## Participants +- Adam Wozney +- Benjamin B +- Cheng Wang +- Damir Simpovic +- Daniel Moore +- George Pro +- Jannick H +- Joao Luna +- Julius Haus +- Luca Fortes +- 00 o +- Pavlo Dereniuk +- Robert Del Rey +- Scott Hewitson + +## Meeting Notes +- Adam Wozney expressed gratitude for participants joining the working group call focused on 2024 events. +- Adam emphasized the importance of early planning, citing lessons learned from the previous year's process. +- Adam acknowledged last year's late start and highlighted the aim to get ahead this year. + +### Review and discuss preliminary list of potential events for 2024 +#### Adam Wozney: +- Adam Wozney provided an overview of the purpose of the call: sharing a [preliminary list](https://docs.google.com/spreadsheets/d/1DBXUhNsf8qxIYD-NtuLeGXhmQ-WTOdcCfdyvXgaGGV0/edit#gid=0) of events and gathering input. +- Mentioned the collaborative effort in compiling events, including suggestions from participants and the PR agency. +- Emphasized that the list is not finalized, and the objective is to collectively decide on the most valuable events. +- The goal is to identify one to two key events per quarter for Akash representation in 2024. +- Highlighted the inclusion of an "overage" in the proposal to accommodate unforeseen significant events. +- Next week's focus: Finalizing the budget with input from today's discussions and through the events working group channel. +- Suggested the use of GitHub discussions or on-chain for the proposal, similar to the previous year's process. +- Proposed aiming for mid to late November for the community to approve the governance proposal. + +### Tiered Structure + +#### Adam Wozney: +- Adam emphasized the need to finalize the budget for both Tier 1 and Tier 2 events. +- Tier 1 events involve extensive participation, sponsorship, and potential external meetups. +- Tier 2 events are lighter with representation and possible stage time. +- Tier 0.5 for lightweight participation. + +### Accurate pricing and managing expenses. +- Scott raised concerns about putting the governance proposal on-chain too early. +- Scott advocated for a later timeline, preferably in late December, to ensure accurate pricing information. +- Pointed out the challenge of fronting costs, especially when dealing with vendors who may not accept AKT. +- Adam Wozney expressed agreement with the idea of delaying the on-chain proposal. +- Mentioned the historical context of previous event governance proposals passing. +- Emphasized the need to balance timing with budget considerations and community approval. + +### Suggestions form for event recommendations. +- 00 o inquired about how to provide suggestions for events and expressed difficulty in accessing the document. +- Adam Wozney shared that he had created a form for collecting event suggestions and had received one response so far. +- Scott making the document accessible for comments to facilitate input from others. +- Adam agreed with the idea of opening the document for comments, especially during the editing phase. +- Permissions were adjusted to allow commenting on the document. + +### Specific events for potential Akash representation. +- Adam clarified the process of initial review, community feedback, and potential follow-up calls with event organizers. +- Adam acknowledged the challenge of limited time for detailed evaluations and emphasized the need for quick community feedback. +- Robert Del Rey suggested categorizing events to provide more context for community decisions. +- The group discussed the potential impact and relevance of attending the AI conference and Developer Week. + +### New Voting System +- Benjamin suggested using a voting system where community members rank their preferred events from 1 to 10. +- Adam Wozney expressed the need to find a way to quantify community preferences efficiently. +- Benjamin B proposed having the community members vote on their top events, possibly using Discord or a shared document. +- Adam Wozney proposed going through the events he suggested, discussing reasons for or against each, and then having participants express their preferences with thumbs up or down. +- Benjamin B suggested a hybrid approach where participants provide reasons for their preferences, and these opinions are discussed to make collective decisions. +- The focus was on prioritizing events that the community strongly wants to attend, considering individual opinions and discussing potential disagreements. + +### Gather opinions and preferences on events(Q1 2024). +- Green Highlights: Events strongly endorsed for attendance. +- Yellow Highlights: Events needing further discussion or review. +- Red Highlights: Initially considered but may need more evaluation. +- Thumbs Up Emoji: Agreement to attend a particular event. +- Thumbs Down Emoji: Disagreement or reservations about an event. + +##### EthDenver: +- Adam highlighted EthDenver as a valuable event due to its community-owned and crypto-focused nature. +- Thumbs up. EthDenver marked as a green event for 2024. + +##### Nvidia Summit. +- Cheng suggested avoiding another hackathon. +- Nvidia Summit considered for its relevance to Akash's push into the GPU space. +- Thumbs up. Nvidia Summit marked as a green event for 2024. + +##### kubecon: +- kubecon in Europe discussed; potential conflict with Nvidia Summit. +- Positive feedback from those who attended kubecon before. +- Joao Luna provided insights into the technical nature of kubecon and the distinction between the American and European editions. +- kubecon marked as green with plans for strong representation. + +##### Blockchain Developer Conference (BDC): +- Adam presented BDC as an event with a focus on blockchain developers. +- Mixed opinions were expressed: thumbs up for visibility and thumbs down for a potentially small audience. +- BDC marked as yellow for further exploration. + +##### South by Southwest (SXSW): +- SXSW discussed as a diverse event covering various topics. +- Opinions varied on its relevance to Akash's goals. +- Mixed opinions SXSW marked as yellow for further exploration. + +##### Crypto Finance Conferernce and Enterprise AI Summit: +- Adam expresses uncertainty about the two as he has not attended it before. +- Adam suggests a similar approach to the previous event (Crypto Finance Conference) with a lightweight representation (Tier 0.5). +- Cheng suggested exploring better review mechanisms for AI-specific events and considering calls with event organizers for more information. + +### Organization for Future Events: +- Cheng emphasized the importance of evaluating product development status before committing to events with product showcases. +- Discussion on the technical expertise of the audience at certain events and potential barriers. + +## Action Item +- Adam to categorize events for better organization. +- Adam to propose a tiered budgeting system for community review. +- Adam to explore lightweight community pool sponsorships for smaller events. +- Participants to use the suggestions form to recommend events for consideration. +- Adamto ontinue monitoring form responses and add suggested events to the list. +- Group to Further exploration and research on events marked as yellow. +- Participants to join the next working group call for finalizing event selections and discussing the proposed tiered structure. + +# **Transcript** + +_This editable transcript was computer generated and might contain errors. People can also change the text after it was created._ + +Robert Del Rey: Thank you so much for that Tyler and thank you all for joining. Welcome to this city called. I believe this is the first goal. We have a community group. So the agenda is gonna be brief project overview some objectives and how can we all work together to make this happen? Also, I believe this call is gonna be good to find out if this is gonna be Viable initiative or maybe if we have to hold it for a later time in the next year. So I'm open for anything. I'm just can't wait to hear just your guys simply. There is a document in the peaceful Channel. It's a Google doc there. You can see all the information. Initially put there. + +Robert Del Rey: And yeah silly is basically a platform that lets. project Founders and Community managers basically To organize your people, It's a tool that you can create submissions. any kind of missions depending on your community, I've seen different kinds of missions. + +Scott Hewitson: that + +Robert Del Rey: So that's why I believe it's a good tool because we can customize it for cash needs. Let me know if you guys can hear me. All right, because I want to speak too loud. + +Scott Hewitson: yep. + +Robert Del Rey: I have someone next to me and I don't. So yeah. + +Scott Hewitson: Stop yelling. + +Robert Del Rey: So, yeah I believe it can be very beneficial for a cash because we have many community members with different backgrounds. We have validators. We have developers. We have just normal Community people that just want to see how a cash develops. And then we also have projects Founders. We have providers. We have a lot in a cache. That's why I believe we have many rooms To do many tasks idea. I did a few tasks or as a test. So you can have an idea. One of them is likely deploying a provider on a cash. Another one is a host X node from X Network my cash. And if you do that and if you upload all the documents you can get rewarded. I mean + +Robert Del Rey: It's not necessary to make all the missions if we are reward if you do them. But it's good to have the option in case when we want to incentivize certain actions or certain people in the community. + +Robert Del Rey: For example missions that I'm not excited about are normal missions go on Twitter stuff and comment whatever the missions are more excited about our Dimensions Host this application host a Blog on a cash. And you can see the examples if you can access the document, you will find all the links. The numbers we had there we had numbers for how much we want to give away in akt prices Rewards. And how much we have to pay or we should pay the people reviewing the missions. Because how silly works is that? + +Robert Del Rey: You can do a missions and there are missions that you can claim them right away and you can get your points right away. But there are other missions that depending on the criteria. Someone has to review them and after they review the missions they can go ahead and run their rewards and the points you access. I'm making sense of course are good. + +Scott Hewitson: Yep. tracking + +Robert Del Rey: awesome guys So yeah, that's basically I do like the tool I use it before when I was working with the staking. I also participated as a community member for Chris and CK Roll-Ups was the name at all. I don't remember And yeah, it was really cool. I mean it has to be a balance because the majority of the projects you got people that just come in to do them easy missions and get the easy rewards. I want to make maybe less missions. But with a bigger reward and a bigger outcome, if you feel like something valuable you can get rewarded for that and that can be monitored in the same silly applications. + +Robert Del Rey: Other benefits that zealy has is that you can add up to five people as admins in the free version. They have a paid version, but I don't know anybody using the paid version and in the free version you have up to five people that can manage missions create missions. Run Points review task. So yeah, it's very complete industry package. and yeah, that's all I want to say at the moment. I'm super happy to work with you guys if you want to work with me. And if we design very very good missions that can attract developers to a cash and can attract applications to a cash. I believe this can be a very good investment in my own opinion and it doesn't have to be like that expensive investment. + +00:05:00 + +Robert Del Rey: So if you guys have a comment question, yeah, I will be the time let's taken from here. + +Scott Hewitson: What? Benjamin go ahead. + +Benjamin B: So the mic now,… + +Robert Del Rey: Sorry Benjamin didn't see I was looking at the document. + +Benjamin B: thank No problem. I just want to say they're here that I really like this idea. I also like that you're trying to focus on some of them harder missions, for people actually get involved and try out the network. I don't think that this would be a good idea. If everything was just follow a caution Twitter retweet maybe create a Reddit post sure. That's great if you want to Shield something or great, so, Bad quality marketing, but if you actually get this harder missions out and you get people to either create their own stuff or just see how the network works and that it works. I think that's a great way to get real members to the community. I think the only thing here that I'm a bit + +Benjamin B: worried about is that the funding is just a rough estimation and everything is just pending do the math. If you could explain more of that stuff would be great. + +Robert Del Rey: internet here Yeah, the reason why is that it's because I don't know. How much would it be in? Initially was Android I assembled the document thinking about the missions and rewards Etc. It's a rough estimate like you say. But I'm happy that I have more people now like you that can help me getting to the best number. That's why it's great at Scott is in this call. Maybe he can give us an idea on how much would be good to start. Maybe a good time frame could be maybe launch this for three to six months with a 5,000. I did it or maybe a 10,000 it's gonna depend on how many missions we want to do because + +Robert Del Rey: Maybe more than one people can make the mission and more than one people can get the rewards. So I'm more than happy to hear what you think things would be a fair value for this. I don't have any experience like organizing prices. So that's why I need help guys. If it's like reviewing missions controlling the tool. Economy for that. So I'm coming on you to get to the best number for our caching for the people that they're gonna participate. + +Scott Hewitson: Go ahead Benjamin. + +Benjamin B: I want to add onto this by saying that I believe that… + +Robert Del Rey: What happened? + +Benjamin B: if a Coach could add the European electric core team. They're the ones controlling the community budget right now and I'm guessing if this budget were to be used for the pilot program on this select the first test to see how viability is for a one-time thing and potentially for multiple rounds. I think they should be a bit in control of how much We should have in the budget and how much should be spent on reviewing and how much should be spent on prices. I would love to hear more from Scott and Tyler. + +Tyler Wright: Before Scott jumps in I just wanted at the highest level just make it clear. + +Scott Hewitson: Pick it up. + +Tyler Wright: I don't think Ben was insinuating this but overclock does not control the Akash community pool that's just like a public good overclock has asked for some Community funding for a small bounties and Small items that Scott who will talk further has been a good Steward on there's a certain amount of money that's been a lot of for again small bounties and small items whether it be like building models documentation management of certain sorts of public goods. But yeah, I just want to make that clarification just for the record. Sorry, go ahead and… + +Scott Hewitson: Yeah, yeah,… + +Tyler Wright: do it. + +Scott Hewitson: no You're right on the head that 5K is what we're talking about. First Thanks for everybody for do doing all the legwork to put all this together. I personally think it's a good idea. and the fact that you guys keep saying let's get the hot the high quality submissions, people use in the network thing. We don't want is right just a bunch of Twitter trolls come in and let me get my 10 akt here and there we want long-term developers George. What's up? + +00:10:00 + +Robert Del Rey: Hey George's Community. + +Scott Hewitson: George you have a question + +George Pro: Yeah. Yeah Robert. Thank you very much. I wanted to touch on the mission because I'm thinking if you are living out the softest BC the one that I know had out we are trying to read the zealy to Target outside people who are not really inside our community. So I believe that we should kind of are the low hungry why so that people when they are kind of find something to do it shouldn't be that hard. You should say that you progress through the ladder and then go to the harder part, but also he said to me that you can kind of skip from the least hard one and then go to + +George Pro: the hardest one so you can do it in two ways. You can have to whereby you can start from social media and then gaining Discord something like that. And then we go to have the one that's only doing machine that our heart. I don't want that to leave the one that so I want people to kind of come and then feel like they are participating and then also doing something when they come to I was in + +Scott Hewitson: Yeah, I think you hit it everyone here. I think we're all aligned and that this is a potential tool to help grow our community in a positive way bringing in the right kind of people not to say there's nothing wrong with The Shield shoulders on Twitter, but, at the end of the day, we're trying to progress the development and use of open or decentralized cloud. so kind of Yeah, Robert, what's up? + +Robert Del Rey: Yeah, there's a quick question. You guys remember how much was a cash budget for the hackathon and specifically only the prices? + +Scott Hewitson: The prizes I think first place was Seven Grand second place was four grand third place might have been one Grand in US Dollars the hackathon budget itself when it went on chain there it was when the price was way lower. So there's a ton of leftover hackathon funds and I'm gonna be returning those or we are going to be returning those back to the community pool soon. But yeah, that was kind of the rough amounts for the winners. + +Scott Hewitson: Yeah, so I guess going a little bit back to what I was talking about. this five grand a month, we kind of put it in for bounties. I think on chain, we called out a few kinds of things and Ty mentioned a little bit like building sdls and blog posts and a couple hundred dollar tasks, I'd say that being said, internally and externally I'm trying to spend that money, we're tracking it and I don't know if you guys have seen let me drop this in here the community support dashboard that covers the vanguards note-taking which we haven't spent any money on and then bounties + +Scott Hewitson: so really what I see this as is we're not spending enough money from bounties just for small things here there or whatever so We got 10 days to spend. I think we've got four grand left for it I don't know if you have anything coming down the pike, but I think it'd be a good opportunity and I know it's not five grand, but if we can get something started and maybe do like a pilot as I think Robert and Benjamin were saying I think it's a good use of funds because we're just going to return it to the community pool if we don't + +Scott Hewitson: Yeah. What's up, Robert? + +Robert Del Rey: Thanks Scott and just adding to that I just thought that besides those missions that we're going to think about. We can also use silly for that to have that cash only for those overclock bounties that you guys release from time to time and that can be a tool for that as well. It can help us keeping track and see actually who's doing more counties and such. + +00:15:00 + +Scott Hewitson: No doubt Benjamin looks up. + +Benjamin B: I wanted to say that I agree that this is a good spending money. I think that regardless if you create one blog post or if you create one still or if you do a program like this targeted to create more than one. I think that we could use the same numbers to try estimate the numbers of outcomes. So if an article is estimated to be at 250, how much is an Estimated to be at do you have that information here? + +Scott Hewitson: Yeah, so I mean when we made it, it's kind of a rough. I think sdl says a hundred bucks. It ranges from 100 to 500 and that's all I think it says these are estimates based on What we think but it could be way less. Yeah. + +Benjamin B: Yeah, I just want to say that I think that this averages could be spent so that if we were to be given a budget of 4K, maybe we should try to at least March the number of stls created through this the program. So if we were to have the 4K and let's just very quickly. 4,000 divided by a hundred is 40 and divided by 500 is 8 so somewhere between four eight and fourth STL should be created ideally from the worker Seeley project or whatever to call it and if this does not happen any + +Benjamin B: Yeah, I don't know how to trace this really, but we could use this as a baseline so. If we are able to create this money through the users using sealer, I think. That's enough for you have anything else you want to? Mention how much to spend on each part? + +Scott Hewitson: Yeah, so I mean, I guess like I said, we've got four grand left for this month. That being said I think the most expensive thing that we've put a bounty out for was sdxl and that was two grand or 2500. So, I don't want to say hey, let's spend four grand on this one thing when it's kind of for bounties, but it's like personally I was thinking if we did something around the 2,500 range that is, kind of like a pilot a stepping stone and it's like all right, we're gonna use it's not really a bounty right? It's a mini program. + +Scott Hewitson: But I think it's well worth our month, well worth exploring and seeing what we can get out of it and you never know. It's like if we do, we do this and it's getting good traction and then it's like, okay, maybe we do need 10 grand or 15 grand to do something like this. That's when we could go with a gov prop, for an ask for a little bit more money and Define the program a little bit. Robert what's up? + +Robert Del Rey: Yeah, I'm with you. It's got 120% so. What if we go ahead and reduce the amount for 1500 to 2,000 and Benjamin. Maybe you and I can design Seven to eight missions and the rewards can range within a hundred and fifty dollars and we couldn't start from there with that budget. The question I have is called is that let's say we go that route we do eight missions and people do them and we give them their Rewards. what will be the metrics we will have to + +Robert Del Rey: to keep in mind in order to make this a successful initiative or maybe a successful pilot because initiative started right, but how can we make on what indicators make this as accessible in European? + +Scott Hewitson: Hi, do you want to say something? I can answer to that question? + +Tyler Wright: Yeah, maybe you go first off all. + +Scott Hewitson: Yeah, I think I mean and you guys laid it all out, it's at least five, in this number obviously, the skilled back a little bit. That's at least 500 curious devs and Tech enthusiasts to test out I think the single metric Is there a er or one or two? is there one new developer maybe it's a person who's excited now, they want to be an Insider or just bringing in smart people and people that are aligned I think is my personal number one goal. Yeah, I don't know how you guys see it, but it's like if we did something like this and we got two or three new Kick-Ass people. I'm all about that. + +00:20:00 + +Tyler Wright: yeah, I would decide to that to Scott's Point earlier about funding I think we've all said it but I think a number like 2000 to 2500 makes a lot of sense because when we want to use this program is we want to keep the dollars and cents of each ask. + +Tyler Wright: Kind of small and have this be an incubator program for things that eventually would come from community pool spend. So I love the idea of funding this and we don't have to go through a community pool right now. It's just like there's funds there a lot for this kind of stuff if the program has legs and continues to be successful. Then we take the next steps and we have this case study. We're not asking for community pool funding just out of nowhere. It's just like hey, we had 2500 dollars. We are trying to hundred and akt and so what we did in the month and a half we brought on two new insiders and a Vanguard that's contributed X Y and Z, and we've gotten X number of eyes on it to the latter point and then Benjamin, I'll hop it over to you. + +Tyler Wright: To the latter point about success. I think we hit it on the head just like trying to find if we could find two or three more insiders that are technical or if somebody from zealy is able to do some sort of bounty or some sort of bigger task like notification tool or something that improves the network even one. I think that would be successful for the dollar amount and we're looking to spend I think it's easy to scale it from there. Or so go ahead Benjamin. + +Benjamin B: I just wanted to ask something here. If we were to actually go through with this should we make that Robert would be the one in lead since he's been creating some of the documents and the Robert can have a free handle the bit on how to create this budget and help spend the money and then we could try to work together everyone interested in. All this smaller details, like what should the tasks be related to how could we get the greater results and how could we reach out to a lot of people? + +Tyler Wright: I would certainly say that Roberts should be the owner and the boss. I would ask that and this is what we've been trying to do with the entire open framework that some of these decisions. I'm not saying that you weren't saying it's bad but somebody's decisions just get made as a group because it just works better that way then a singular person making decision and then letting people know later and then we could have just gotten group feedback. So I believe that Robert should be the owner and kind of be the manager but then some of this decision has relate to tasks that relate to just general budgets in the short-term and long term. I think should just be done as working group sessions where lazy agenda Robert lease is through but again, we can make these decisions and have action I have to come out of this as a group. + +Scott Hewitson: Go ahead Benmin. sorry. + +Benjamin B: Yeah, if this sounds good to me and the last thing I want to ask Harry start related to how much should be spent on the tasks. And how much should we spend on the admin? Should this be done in the working groups Maybe? + +Scott Hewitson: as far as the breakout of funds yeah,… + +Benjamin B: Yes. + +Scott Hewitson: I mean, we're kind of having the conversation now, personally I think if we start with 2500 if that's 2,000 towards the + +Scott Hewitson: towards rewards and 500 bucks for people's time. if that sounds crazy tell me I don't know, and we've got these different funding mechanisms and I want to try to use it as much as possible. But I also want to be respectful of people's time. And I know here is said a couple month ordeal and I don't want you guys to be doing all this work and not getting any compensation for yourselves either kind of just leaning on you guys a little bit to + +00:25:00 + +Scott Hewitson: Hey, this is what we think and I like giving people autonomy. I like giving you get the most out of people when you trust them and you can when they give them their own devices to succeed or fail and then after there. It's like all right, we know it was a failure or we know is a success and it is a decent amount of money, but it's not like it's the whole community pool. off the top of you guys' heads. How do you see let's just throw out the 2500 right now. how would you do it? If you had the keys to the castle today to this disperse that 2500? + +Tyler Wright: Benjamin Sorry real quick before you speak because Scott just brought up a great point. I just want to reiterate and I wanted to Huey has been done a great job of providing transparency and I accountability as it takes the community pool and holding whether it be overclock accountable or members of the community accountable. I try to do my best to make sure that people are doing what they say that they're going to be doing. So whoever takes on this management job just know that it comes with a little bit like being an owner comes with responsibility and Huey and I are going to make sure that we hold people accountable, as stewards of + +Tyler Wright: the open source of caution Network, we do not want funds to just spend on wisely and we're We're doing the same thing for technical development. We're doing the same thing for everything that comes out of that community pool everything that can get upon about it retains to the akt Token. There's some care behind the scenes that's being taken. So there is going to be some accountability for this position, if somebody's like we're happy to pay anybody for their time and their energy, but if you say I'm going to do x y a and you're certainly getting paid from again public funds, Harry and I both come from + +Tyler Wright: a different world where dollars and cents actually matter and people have to be held accountable when they use those dollars and cents. So we will be holding people accountable. I just want to let people know that before 2024 starts. + +Robert Del Rey: And thanks that a great point. + +Scott Hewitson: go ahead Benjamin. + +Benjamin B: I want to say that. Yes. I think we should even have a round of applause for Scott here. + +Benjamin B: I don't even know if it can hear it anyways. + +Scott Hewitson: I can see it. + +Scott Hewitson: I can see it. I appreciate it. + +Benjamin B: Great. + +Benjamin B: Back to the question if I had the keys to the treasury to the two and a half Kate treasure, I would do something similar. I would either do I would depending on how large these prices would be and how many you'd estimate the program to have I would either have between 500 to the free admins unless there will be more or 1000 between the free elements. I think that both of those. Somewhere around in that range would be a good. starting point for the pilot + +Scott Hewitson: About 750 so it's 250 API a pop for the three of three folks in here doing it. And then that gives us 1750 in rewards and for a budgets and tasks + +Tyler Wright: I think that makes sense. I also think that if everybody agrees that we should not be promoting the Shilling. I don't think we should give a single Cent for somebody following us on Twitter unless it's a prerequisite of the platform and we should just focus on just some of those smaller bounties maybe we're getting doing something that benefits of network and maybe to be just a price maybe if somebody updates documentation. It's five akt. I don't know. Maybe we can get some more value from this zealy community. So just want to put that out there. Go ahead Benjamin. + +Benjamin B: I think that it could make sense to pay people to have to follow on Twitter as well. But from what I've heard you can have this minimum ranges. So if you only get 50 points, you won't get paid. But as soon as you hit a certain threshold, you will get paid for everything. So then maybe just following and just doing this small things. They won't give you anything. But if you do something and also do the small things you will get a little for everything. So if having people get connected with a coach Community is worth something. I think that we could add just a tiny tiny bits to making them follow as well. + +00:30:00 + +Scott Hewitson: Yeah, I mean, I agree with that. It's like if you need 30 points to get paid anything and it's 25 to deploy something and then it's five to share and then that gets you to 30. I think that's reasonable. But yeah, it's to your point. It's like if all the easy Bounty Hunter airdrop Style Tasks, you can get full payout based off of that then we're just gonna attract those kinds of people. + +Scott Hewitson: Thanks for taking notes Robert. Appreciate you. + +Scott Hewitson: I mean, I'm excited. I think let's press with it. I'm cool with let's do 2500 750 of that for admin and 1750 for Rewards is that sound all right with everyone is that any adjustments or? + +Scott Hewitson: Okay. + +Robert Del Rey: However, if it's straight for this pilot, thanks, Scott. + +Scott Hewitson: Of course, I guess the next step is because we've got a 70% solution. We kind of know what we want to do a little bit. I'd like to let's see. I mean we can call it a bounty and I can have have it sent out this week before November for sure probably wait till a little drawback in price so that we get the most akt out of it. so for next steps, do you guys want to schedule another one of these calls in a couple weeks? Do you want to do it? Async? Do you want to I think the next step would be coming up with a formalized plan and then that we can all review and press with. What's up, Robert? + +Robert Del Rey: I agree 100% and Monday is great for this goal. Maybe we can make it green now. And next Monday. We can give you some updates and when I say we are Benjamin. ation, and of course myself + +Scott Hewitson: Of course the boss man. + +Robert Del Rey: Thanks, Lord. + +Scott Hewitson: That sounds great. + +Robert Del Rey: Yeah. + +Scott Hewitson: Tyler do you have anything else you want to add? + +Tyler Wright: No, I think you just said we can turn this into a weekly meeting. Until we get this program kind of off the ground I think as a strategy document for next week, and then it's success documents. for next week would be great. I think the goal of this pilot is to See if it can get some momentum on zealy and turn this into something that gets community pool funding on a year over year basis because it's just a part of the community success program. So really looking forward to it. I'll put some time on the calendar. And at least we'll have a couple meetings maybe over the next three or four weeks. We'll have a meeting on this and next week is still November. So maybe my next week. maybe you talk about this. I don't just run for a quick second to chase a dog. + +Tyler Wright: Maybe there's a specific wallet that gets spun up for this and we can look to get this funded for next week. Especially for one do this in November, but I'll give us the next week to figure out strategy and we can maybe share some documents async this week. And this look to me next week if that works for everybody. + +Scott Hewitson: Okay works for me. Yeah, I think it's one of you guys want to hold the funds you can have fun send over. Like I said, I'll probably wait till a little drawback. we'll see what happens on akt's kind of mooning right now. + +Tyler Wright: Yeah. + +Scott Hewitson: but Yeah,… + +Robert Del Rey: It's crazy. + +Scott Hewitson: I know right? + +Tyler Wright: No, but I think that's a good plan. Maybe Robert you spin up the wallet as the owner and then it'll be part of your own responsibilities to pay out the rest of the management team. But again, we can make sure that gets done and we could talk about a little bit more about that next week from an operational standpoint, but the focus of next week's conversation should just be on strategy and implementation. + +00:35:00 + +Robert Del Rey: Absolutely. Awesome. + +Scott Hewitson: Sounds good. of + +Robert Del Rey: Thank you so much guys, Fury. Really really appreciate it. + +Tyler Wright: + +Scott Hewitson: we appreciate mean, we've got all these mechanisms for funding, it behooves us to use them. If not, then what are we doing? + +Tyler Wright: plus one. + +Robert Del Rey: Okay, yeah. + +Benjamin B: Okay, yeah. The super fun to see that this actually worked out with the funding and everything. I believe that for the remainder of the 4K in this month's budget. You can just send that to me. I have a little room for a one and… + +Scott Hewitson: Okay. + +Benjamin B: a half K in one of my wallets. Just send me a message. + +Scott Hewitson: You have just enough room,… + +Tyler Wright: but + +Scott Hewitson: speaking. I wanted to mention so we've kind of bring it back to + +Robert Del Rey: They're gonna send it to me and I think we posted. + +Scott Hewitson: yeah, there we go. I trust you guys. No, just talking about the bounties. So, it started as a let's get a little bit of money in one of the props so that we can do certain things bounties. Whatever part of that has been, we kind of just been going one to one with people kind of I've been telling people on the ternal side. Hey, if you need things done, you need small tasks. Let me know that I know let the community know we've got money to use it coming out this week. Hopefully is we're gonna Define the program a little bit more for bounties if you guys have seen The cohesive product and Engineering roadmap. We're looking to put out something that looks very similar to that but + +Scott Hewitson: from the community side and then it's like we'll have tat there will be backlog items up next items in progress items and then kind of to show one what core team is working on in the marketing Community side, but also where those gaps are and it'll call out Bounty specifically. So I think it's gonna get a lot cleaner A lot more efficient for the bounties. But because we are where we are today, let's spend some money doing some stuff that we think will progress the network. So Look forward to releasing that and if you guys have any questions comments concerns, please please please let me know that Ty know and we'll try to address some best we can. + +Robert Del Rey: Thank you so much and start Tyler George Benji. I guess we are right on time this book about a lot. I noted a few things down. Also, this call is being recorded in transcribed. Hopefully the people are then join now can listen to it and maybe we have more people but operating. Let's see how that goes. In case you have any extra comments concerns questions regrets. Also, feel free to drop any message in the city of channel, right? + +Scott Hewitson: That was good. + +Tyler Wright: Thank you all I'll add some time for next week or in the following weeks. But if this works for everybody, then we'll do the same time next week. We'll see you then. And thank you. + +Robert Del Rey: Thank you, Tyler. + +Benjamin B: Awesome. Thank you everyone. + +Scott Hewitson: All right. Have a great day everybody. + +Robert Del Rey: Stay safe guys. Bye-bye. + +Tyler Wright: ever over + +Benjamin B: but + +Scott Hewitson: right + +Meeting ended after 00:39:13 👋 diff --git a/wg-zealy/README.md b/wg-zealy/README.md new file mode 100644 index 00000000..005132b7 --- /dev/null +++ b/wg-zealy/README.md @@ -0,0 +1,35 @@ +# Akash Network Zealy Working Group + +This working group is to launch an Akash account on Zealy (formerly Crew3.xyz), a community builder platform. The aim of this group is to increase awareness about Akash in gamify form, and create tasks for the community based on their skill level. e.g influencer, developer, provider, content creator etc. + +The working group is created to work on the proposal to see what support is needed, outline the goals and forecast outcome, decide on the user rewards, points, ladder system and time. Based on this metrics, we will be able to see the full picture and the success of the program. + + + +## Meetings + +| Meeting | Time | Notes | Transcript | Recording +| --- | --- | --- | --- | --- | +| #1 | Friday, February 17, 2023 08:30 AM PT (Pacific Time)|[Link](https://github.com/akash-network/community/blob/main/wg-crew3/meetings/001-2023-02-17.md) |[Link](https://github.com/akash-network/community/blob/main/wg-crew3/meetings/001-2023-02-17.md#transcript) | coming soon +| #2 | Monday, November 20th, 2023 08:30 AM PT (Pacific Time)|[Link](https://github.com/akash-network/community/blob/main/wg-zealy/meetings/002-2023-11-20.md)|[Link](https://github.com/akash-network/community/blob/main/wg-zealy/meetings/002-2023-11-20.md#transcript)|[Link](https://omnv3rqpb3qrv5iw4tdpu2eipbonzvjr2khqiponlrtgftkwwybq.arweave.net/cxtdxg8O4Rr1FuTG-miIeFzc1THSjwQ9zVxmYs1WtgM) +| #3 | Monday, November 27th, 2023 08:30 AM PT (Pacific Time)|[Link](https://github.com/akash-network/community/blob/main/wg-zealy/meetings/003-2023-11-27.md)|[Link](https://github.com/akash-network/community/blob/main/wg-zealy/meetings/003-2023-11-27.md#transcript)|[Link](https://47vhtsd36l63wlteorhccwvklpzihemikfrxljg6mebv2myt7bzq.arweave.net/5-p5yHvy_bsuZHROIVqqW_KDkYhRY3Wk3mEDXTMT-HM) +| #4 | Monday, December 4th, 2023 06:30 AM PT (Pacific Time)|[Link](https://github.com/akash-network/community/blob/main/wg-zealy/meetings/004-2023-12-04.md)|[Link](https://github.com/akash-network/community/blob/main/wg-zealy/meetings/004-2023-12-04.md#transcript)|[Link](https://sq2ysituuvyyyeuuw7eawkdlbmvqpwtlkqkpogujyh5jfoxexosq.arweave.net/lDWJInSlcYwSlLfICyhrCysH2mtUFPcaicH6krrku6U) +| #5 | Monday, December 11th, 2023 06:30 AM PT (Pacific Time)|[Link](https://github.com/akash-network/community/blob/main/wg-zealy/meetings/005-2023-12-11.md)|[Link](https://github.com/akash-network/community/blob/main/wg-zealy/meetings/005-2023-12-11.md#transcript)|[Link](https://hp5novctzn3y56mrqix5wq3knexy4w24tk2ugahmstq2ofxzp57a.arweave.net/O_rXVFPLd475kYIv20NqaS-OW1yatUMA7JThpxb5f34) +| #6 | Monday, December 18th, 2023 06:30 AM PT (Pacific Time)|[Link](https://github.com/akash-network/community/blob/main/wg-zealy/meetings/006-2023-12-18.md)|[Link](https://github.com/akash-network/community/blob/main/wg-zealy/meetings/006-2023-12-18.md#transcript)|[Link](https://efn65ve3e5sebv7bhpgilvvzv23zx3ln6goskfwwrhj5rsmbludq.arweave.net/IVvu1JsnZEDX4TvMhda5rreb7W3xnSUW1onT2MmBXQc) +| #7 | Monday, January 15th, 2023 06:30 AM PT (Pacific Time)||| +## Leads + +- Piber Dev +- Robert Del Rey + +## Contacts + +- [Discord](https://discord.gg/6ffnaGay) + + +## PRDs and other documentation +- PRD + +## Related SIGs + +- [community/sig-community](sig-community) diff --git a/wg-crew3/meetings/001-2023-02-17.md b/wg-zealy/meetings/001-2023-02-17.md similarity index 100% rename from wg-crew3/meetings/001-2023-02-17.md rename to wg-zealy/meetings/001-2023-02-17.md diff --git a/wg-zealy/meetings/002-2023-11-20.md b/wg-zealy/meetings/002-2023-11-20.md new file mode 100644 index 00000000..784eee3f --- /dev/null +++ b/wg-zealy/meetings/002-2023-11-20.md @@ -0,0 +1,431 @@ +# Akash Network - Zealy Working Group (WG) - Meeting #2 + +## Agenda +- Overview of the Zealy platform. +- Discussions of Zealy missions and the overall pilot phase + +## Meeting Details +- Date: Monday, November 20, 2023 +- Time: 6:00 AM PT (Pacific Time) +- [Recording](https://omnv3rqpb3qrv5iw4tdpu2eipbonzvjr2khqiponlrtgftkwwybq.arweave.net/cxtdxg8O4Rr1FuTG-miIeFzc1THSjwQ9zVxmYs1WtgM) +- [Transcript](#transcript) + +## Participants +- Benjamin B +- George Pro +- Robert Del Rey +- Scott Hewitson +- Tyler Wright + +## Meeting Notes + +##### Robert Del Rey: +- Outlines the agenda: project overview, objectives, collaboration, and viability assessment. +- Mentions the presence of a document in the Zealy Discord Channel, a Google doc with all relevant information. +- Describes Zealy as a platform for project founders and community managers to organize people. +- Highlights the potential benefits of Zealy for Akash due to the diverse backgrounds of community members (validators, developers, etc.). +- Mentions the variety of tasks that can be accomplished on Zealy, citing examples like deploying a provider on Akash and hosting an X node from X Network. +- Discusses the option to reward participants for completing missions on Zealy. +- Stresses that completing all missions is not necessary but provides the option for incentivizing specific actions or individuals within the community. +- Expressed excitement for missions like hosting applications and blogs on Akash, as opposed to more generic tasks like Twitter engagement. +- Stresses the need for balance in mission design to avoid attracting participants solely interested in easy missions and rewards. +- Advocates for fewer missions with larger rewards for valuable contributions. +- Highlights Zealy's features, such as the ability to add up to five people as admins in the free version. +- Mentions a paid version but notes lack of information on users utilizing it. +- Views well-designed missions as a valuable investment, emphasizing that it doesn't have to be an expensive one. +- Expresses uncertainty about the initial cost and welcomes input to arrive at a more accurate figure. + +##### Benjamin B: +- Expresses appreciation for the idea and highlights his liking for the focus on more challenging missions to engage people with the network. +- Emphasizes that simple tasks like retweeting or creating Reddit posts might lead to low-quality marketing. +- Supports the idea that harder missions involving creating content or exploring the network can attract genuine community members. +- Benjamin expresses his belief about the involvement of the Akash core team on budget. +- Suggests that the team, currently controlling the community budget, could have a role in overseeing the budget for the pilot program. +- Benjamin suggests that payment for tasks, including following on Twitter, could be based on a minimum threshold of points. +- Scott agrees with the idea, emphasizing the need to balance easy tasks with those that bring tangible value. +- Benjamin B raises a concern about funding being a rough estimation and pending further calculations. +- Requests more clarification and information on the financial aspects to address potential worries. + +##### Scott Hewitson: +- Scott Hewitson acknowledges agreement with the suggested budget, confirming that $5,000 is the amount under consideration. +- Appreciates the emphasis on obtaining high-quality submissions and encouraging people to engage with the network meaningfully. +- Highlights the goal of attracting long-term developers rather than individuals only seeking small rewards for simple tasks on social media platforms like Twitter. + +##### George Pro: +- George Pro addresses Robert, expressing gratitude and raising a question regarding the missions. +- Suggests using Zealy to target individuals outside the community, aiming to attract those not already involved. +- Advocates for including missions that are not too difficult, allowing people to find something to do without it being overly challenging. +- Recommends a ladder approach, where participants can progress from easier missions to more challenging ones. +- Suggests allowing participants to skip levels, going from the least difficult to the most challenging if they prefer. +- Proposes two approaches: starting from social media and then transitioning to Discord, or directly engaging in more challenging tasks like deploying a website. +- Emphasizes the importance of making participants feel like they are actively contributing and participating when they join the Zealy platform. + +### Financial Considerations + +##### Scott Hewitson: +- Discusses the monthly allocation of five grand for bounties. +- Mentions on-chain calls for tasks like building sdls, blog posts, and smaller assignments. +- Expresses efforts to spend the allocated money both internally and externally. +- Shares the Community Support Dashboard covering vanguards note-taking and unspent bounty funds. +- Recognizes the need to spend more on bounties, emphasizing small tasks with four grand remaining. +- Proposes the idea of initiating a pilot program, as suggested by Robert and Benjamin. + +##### Tyler Wright: +- Suggests the creation of a specific wallet for the pilot program. +- Aims to secure funding for the program by the next week, preferably within November. +- Proposes a week dedicated to figuring out the strategy and asynchronous document sharing. + +### Budget Consideration + +##### Scott Hewitson: +- Acknowledges that the estimates for outcomes are rough, ranging from $100 to $500 for tasks like creating blog posts or sdls. +- Discusses the possibility of tracking outcomes as a baseline for success. +- Mentions a potential budget allocation for a pilot program around the $2,500 range. +- Considers it a stepping stone for exploring the effectiveness of the program. +- Responds to Benjamin's question about fund allocation for tasks and administration. +- Proposes an initial allocation of $2000 for rewards and $500 for people's time. +- Scott proposes a distribution of $750 for three admins and $1750 for rewards and tasks. +- The suggested breakdown aligns with the total budget of $2500. +- Expresses a desire to use different funding mechanisms while being considerate of participants' time and ensuring fair compensation. + +##### Benjamin B: +- Agrees with the idea of using the remaining budget to create sdls and other tasks. +- Proposes reducing the budget per sdl to increase the number of missions. +- Suggests designing seven to eight missions with rewards ranging from $150 to $200. +- Raises the question of defining metrics for success and indicators for a successful pilot initiative. +- Benjamin suggests allocating between $500 and $1000 for three admins. + +##### Robert Del Rey: +- Supports the idea of reducing the budget per sdl and designing multiple missions. +- Seeks clarity on the metrics and indicators that would define the success of the initiative or pilot program. +- Discusses the possibility of him creating and managing the wallet for the program. + +##### Tyler Wright: +- Agrees with Scott's perspective on funding, suggesting a budget range of $2000 to $2500. +- Discusses the purpose of the program, aiming to keep individual ask amounts small and using it as an incubator for future community pool spend. +- Supports funding the program without an immediate need for community pool approval. + +### Discussion on Metrics and Success Indicators: + +##### Tyler: +- Envisions the program as a case study, showcasing its success with tangible outcomes such as new insiders and Vanguards. +- Discusses the importance of tracking metrics related to success, including bringing in new insiders and achieving improvements to the network. + +##### Scott Hewitson: +- Emphasizes the goal of attracting at least 500 curious developers and tech enthusiasts to test the initiative. +- Highlights the single metric for success: the recruitment of one or two new developers, particularly those excited to become insiders. +- Stresses the importance of bringing in smart individuals and people aligned with the project. +- Expresses personal enthusiasm for the initiative, particularly if it leads to the recruitment of two or three new valuable contributors. + +### Leadership Concerns + +##### Benjamin B: +- Proposes that Robert takes the lead as the owner and manager of the initiative, given his role in creating documents. +- Suggests working together as a group to refine details such as tasks, reaching out to people, and optimizing results. +- Asks about the allocation of funds for tasks and administration and suggests discussing it in working group sessions. +##### Tyler Wright: +- Supports the idea of Robert being the owner and manager of the initiative. +- Advocates for collaborative decision-making in the working group sessions to ensure diverse perspectives and feedback. +- Discusses the importance of involving the group in decisions related to tasks, budgets, and other aspects. + +### Reminder on Accountability: +- Appreciates Scott's point and emphasizes transparency and accountability. +- Stresses the responsibility that comes with managing funds and the importance of accountability. +- Highlights the commitment to holding individuals accountable for the wise use of public funds. +- Tyler emphasizes the importance of not incentivizing shilling or tasks with minimal value. +- Recommends focusing on tasks that bring value to the network, such as updating documentation. + +### Next Steps: +- Scott Hewitson suggests proceeding with the proposed allocation for the pilot. +- Scott plans to send out the bounty announcement before the end of November. +- Robert Del Rey proposes scheduling another meeting for the following Monday to provide updates. +- Scott Hewitson agrees and suggests turning it into a weekly meeting until the program gains momentum. +- Robert Del Rey mentions that updates can be provided by Benjamin and himself in the next meeting. +- Tyler Wright acknowledges the plan and emphasizes turning the program into a community success initiative. +- Tyler suggests creating a strategy document for the next week and a success document for future reference. +- The goal is to assess the pilot's momentum on Zealy and potentially secure community pool funding. +- Tyler decided to schedule meetings over the next three to four weeks to discuss the progress of the program. +### Other Matters Discussed +#### Clarification on Overclock's Role: +- Tyler clarifies that Overclock does not control the Akash community pool. +- Describes Overclock's involvement, stating they have requested some community funding for small bounties and items. +- Credits Scott Hewitson for being a good steward in managing a specific amount of money allocated for small bounties and items related to public goods. +## Action Items +- Scott Hewitson to draft and send out the bounty announcement before the end of November. +- Robert Del Rey, Benjamin B, and Scott Hewitson to collaborate on formalizing a plan for the pilot program. +- Group to schedule weekly meetings to discuss the progress, challenges, and updates related to the pilot program. +- Tyler to explore the creation of a specific wallet to hold funding for the pilot phase. + +# **Transcript** + +_This editable transcript was computer generated and might contain errors. People can also change the text after it was created._ + +Robert Del Rey: Thank you so much for that Tyler and thank you all for joining. Welcome to this city called. I believe this is the first goal. We have a community group. So the agenda is gonna be brief project overview some objectives and how can we all work together to make this happen? Also, I believe this call is gonna be good to find out if this is gonna be Viable initiative or maybe if we have to hold it for a later time in the next year. So I'm open for anything. I'm just can't wait to hear just your guys simply. There is a document in the peaceful Channel. It's a Google doc there. You can see all the information. Initially put there. + +Robert Del Rey: And yeah silly is basically a platform that lets. project Founders and Community managers basically To organize your people, It's a tool that you can create submissions. any kind of missions depending on your community, I've seen different kinds of missions. + +Scott Hewitson: that + +Robert Del Rey: So that's why I believe it's a good tool because we can customize it for cash needs. Let me know if you guys can hear me. All right, because I want to speak too loud. + +Scott Hewitson: yep. + +Robert Del Rey: I have someone next to me and I don't. So yeah. + +Scott Hewitson: Stop yelling. + +Robert Del Rey: So, yeah I believe it can be very beneficial for a cash because we have many community members with different backgrounds. We have validators. We have developers. We have just normal Community people that just want to see how a cash develops. And then we also have projects Founders. We have providers. We have a lot in a cache. That's why I believe we have many rooms To do many tasks idea. I did a few tasks or as a test. So you can have an idea. One of them is likely deploying a provider on a cash. Another one is a host X node from X Network my cash. And if you do that and if you upload all the documents you can get rewarded. I mean + +Robert Del Rey: It's not necessary to make all the missions if we are reward if you do them. But it's good to have the option in case when we want to incentivize certain actions or certain people in the community. + +Robert Del Rey: For example missions that I'm not excited about are normal missions go on Twitter stuff and comment whatever the missions are more excited about our Dimensions Host this application host a Blog on a cash. And you can see the examples if you can access the document, you will find all the links. The numbers we had there we had numbers for how much we want to give away in akt prices Rewards. And how much we have to pay or we should pay the people reviewing the missions. Because how silly works is that? + +Robert Del Rey: You can do a missions and there are missions that you can claim them right away and you can get your points right away. But there are other missions that depending on the criteria. Someone has to review them and after they review the missions they can go ahead and run their rewards and the points you access. I'm making sense of course are good. + +Scott Hewitson: Yep. tracking + +Robert Del Rey: awesome guys So yeah, that's basically I do like the tool I use it before when I was working with the staking. I also participated as a community member for Chris and CK Roll-Ups was the name at all. I don't remember And yeah, it was really cool. I mean it has to be a balance because the majority of the projects you got people that just come in to do them easy missions and get the easy rewards. I want to make maybe less missions. But with a bigger reward and a bigger outcome, if you feel like something valuable you can get rewarded for that and that can be monitored in the same silly applications. + +Robert Del Rey: Other benefits that zealy has is that you can add up to five people as admins in the free version. They have a paid version, but I don't know anybody using the paid version and in the free version you have up to five people that can manage missions create missions. Run Points review task. So yeah, it's very complete industry package. and yeah, that's all I want to say at the moment. I'm super happy to work with you guys if you want to work with me. And if we design very very good missions that can attract developers to a cash and can attract applications to a cash. I believe this can be a very good investment in my own opinion and it doesn't have to be like that expensive investment. + +00:05:00 + +Robert Del Rey: So if you guys have a comment question, yeah, I will be the time let's taken from here. + +Scott Hewitson: What? Benjamin go ahead. + +Benjamin B: So the mic now,… + +Robert Del Rey: Sorry Benjamin didn't see I was looking at the document. + +Benjamin B: thank No problem. I just want to say they're here that I really like this idea. I also like that you're trying to focus on some of them harder missions, for people actually get involved and try out the network. I don't think that this would be a good idea. If everything was just follow a caution Twitter retweet maybe create a Reddit post sure. That's great if you want to Shield something or great, so, Bad quality marketing, but if you actually get this harder missions out and you get people to either create their own stuff or just see how the network works and that it works. I think that's a great way to get real members to the community. I think the only thing here that I'm a bit + +Benjamin B: worried about is that the funding is just a rough estimation and everything is just pending do the math. If you could explain more of that stuff would be great. + +Robert Del Rey: internet here Yeah, the reason why is that it's because I don't know. How much would it be in? Initially was Android I assembled the document thinking about the missions and rewards Etc. It's a rough estimate like you say. But I'm happy that I have more people now like you that can help me getting to the best number. That's why it's great at Scott is in this call. Maybe he can give us an idea on how much would be good to start. Maybe a good time frame could be maybe launch this for three to six months with a 5,000. I did it or maybe a 10,000 it's gonna depend on how many missions we want to do because + +Robert Del Rey: Maybe more than one people can make the mission and more than one people can get the rewards. So I'm more than happy to hear what you think things would be a fair value for this. I don't have any experience like organizing prices. So that's why I need help guys. If it's like reviewing missions controlling the tool. Economy for that. So I'm coming on you to get to the best number for our caching for the people that they're gonna participate. + +Scott Hewitson: Go ahead Benjamin. + +Benjamin B: I want to add onto this by saying that I believe that… + +Robert Del Rey: What happened? + +Benjamin B: if a Coach could add the European electric core team. They're the ones controlling the community budget right now and I'm guessing if this budget were to be used for the pilot program on this select the first test to see how viability is for a one-time thing and potentially for multiple rounds. I think they should be a bit in control of how much We should have in the budget and how much should be spent on reviewing and how much should be spent on prices. I would love to hear more from Scott and Tyler. + +Tyler Wright: Before Scott jumps in I just wanted at the highest level just make it clear. + +Scott Hewitson: Pick it up. + +Tyler Wright: I don't think Ben was insinuating this but overclock does not control the Akash community pool that's just like a public good overclock has asked for some Community funding for a small bounties and Small items that Scott who will talk further has been a good Steward on there's a certain amount of money that's been a lot of for again small bounties and small items whether it be like building models documentation management of certain sorts of public goods. But yeah, I just want to make that clarification just for the record. Sorry, go ahead and… + +Scott Hewitson: Yeah, yeah,… + +Tyler Wright: do it. + +Scott Hewitson: no You're right on the head that 5K is what we're talking about. First Thanks for everybody for do doing all the legwork to put all this together. I personally think it's a good idea. and the fact that you guys keep saying let's get the hot the high quality submissions, people use in the network thing. We don't want is right just a bunch of Twitter trolls come in and let me get my 10 akt here and there we want long-term developers George. What's up? + +00:10:00 + +Robert Del Rey: Hey George's Community. + +Scott Hewitson: George you have a question + +George Pro: Yeah. Yeah Robert. Thank you very much. I wanted to touch on the mission because I'm thinking if you are living out the softest BC the one that I know had out we are trying to read the zealy to Target outside people who are not really inside our community. So I believe that we should kind of are the low hungry why so that people when they are kind of find something to do it shouldn't be that hard. You should say that you progress through the ladder and then go to the harder part, but also he said to me that you can kind of skip from the least hard one and then go to + +George Pro: the hardest one so you can do it in two ways. You can have to whereby you can start from social media and then gaining Discord something like that. And then we go to have the one that's only doing machine that our heart. I don't want that to leave the one that so I want people to kind of come and then feel like they are participating and then also doing something when they come to I was in + +Scott Hewitson: Yeah, I think you hit it everyone here. I think we're all aligned and that this is a potential tool to help grow our community in a positive way bringing in the right kind of people not to say there's nothing wrong with The Shield shoulders on Twitter, but, at the end of the day, we're trying to progress the development and use of open or decentralized cloud. so kind of Yeah, Robert, what's up? + +Robert Del Rey: Yeah, there's a quick question. You guys remember how much was a cash budget for the hackathon and specifically only the prices? + +Scott Hewitson: The prizes I think first place was Seven Grand second place was four grand third place might have been one Grand in US Dollars the hackathon budget itself when it went on chain there it was when the price was way lower. So there's a ton of leftover hackathon funds and I'm gonna be returning those or we are going to be returning those back to the community pool soon. But yeah, that was kind of the rough amounts for the winners. + +Scott Hewitson: Yeah, so I guess going a little bit back to what I was talking about. this five grand a month, we kind of put it in for bounties. I think on chain, we called out a few kinds of things and Ty mentioned a little bit like building sdls and blog posts and a couple hundred dollar tasks, I'd say that being said, internally and externally I'm trying to spend that money, we're tracking it and I don't know if you guys have seen let me drop this in here the community support dashboard that covers the vanguards note-taking which we haven't spent any money on and then bounties + +Scott Hewitson: so really what I see this as is we're not spending enough money from bounties just for small things here there or whatever so We got 10 days to spend. I think we've got four grand left for it I don't know if you have anything coming down the pike, but I think it'd be a good opportunity and I know it's not five grand, but if we can get something started and maybe do like a pilot as I think Robert and Benjamin were saying I think it's a good use of funds because we're just going to return it to the community pool if we don't + +Scott Hewitson: Yeah. What's up, Robert? + +Robert Del Rey: Thanks Scott and just adding to that I just thought that besides those missions that we're going to think about. We can also use silly for that to have that cash only for those overclock bounties that you guys release from time to time and that can be a tool for that as well. It can help us keeping track and see actually who's doing more counties and such. + +00:15:00 + +Scott Hewitson: No doubt Benjamin looks up. + +Benjamin B: I wanted to say that I agree that this is a good spending money. I think that regardless if you create one blog post or if you create one still or if you do a program like this targeted to create more than one. I think that we could use the same numbers to try estimate the numbers of outcomes. So if an article is estimated to be at 250, how much is an Estimated to be at do you have that information here? + +Scott Hewitson: Yeah, so I mean when we made it, it's kind of a rough. I think sdl says a hundred bucks. It ranges from 100 to 500 and that's all I think it says these are estimates based on What we think but it could be way less. Yeah. + +Benjamin B: Yeah, I just want to say that I think that this averages could be spent so that if we were to be given a budget of 4K, maybe we should try to at least March the number of stls created through this the program. So if we were to have the 4K and let's just very quickly. 4,000 divided by a hundred is 40 and divided by 500 is 8 so somewhere between four eight and fourth STL should be created ideally from the worker Seeley project or whatever to call it and if this does not happen any + +Benjamin B: Yeah, I don't know how to trace this really, but we could use this as a baseline so. If we are able to create this money through the users using sealer, I think. That's enough for you have anything else you want to? Mention how much to spend on each part? + +Scott Hewitson: Yeah, so I mean, I guess like I said, we've got four grand left for this month. That being said I think the most expensive thing that we've put a bounty out for was sdxl and that was two grand or 2500. So, I don't want to say hey, let's spend four grand on this one thing when it's kind of for bounties, but it's like personally I was thinking if we did something around the 2,500 range that is, kind of like a pilot a stepping stone and it's like all right, we're gonna use it's not really a bounty right? It's a mini program. + +Scott Hewitson: But I think it's well worth our month, well worth exploring and seeing what we can get out of it and you never know. It's like if we do, we do this and it's getting good traction and then it's like, okay, maybe we do need 10 grand or 15 grand to do something like this. That's when we could go with a gov prop, for an ask for a little bit more money and Define the program a little bit. Robert what's up? + +Robert Del Rey: Yeah, I'm with you. It's got 120% so. What if we go ahead and reduce the amount for 1500 to 2,000 and Benjamin. Maybe you and I can design Seven to eight missions and the rewards can range within a hundred and fifty dollars and we couldn't start from there with that budget. The question I have is called is that let's say we go that route we do eight missions and people do them and we give them their Rewards. what will be the metrics we will have to + +Robert Del Rey: to keep in mind in order to make this a successful initiative or maybe a successful pilot because initiative started right, but how can we make on what indicators make this as accessible in European? + +Scott Hewitson: Hi, do you want to say something? I can answer to that question? + +Tyler Wright: Yeah, maybe you go first off all. + +Scott Hewitson: Yeah, I think I mean and you guys laid it all out, it's at least five, in this number obviously, the skilled back a little bit. That's at least 500 curious devs and Tech enthusiasts to test out I think the single metric Is there a er or one or two? is there one new developer maybe it's a person who's excited now, they want to be an Insider or just bringing in smart people and people that are aligned I think is my personal number one goal. Yeah, I don't know how you guys see it, but it's like if we did something like this and we got two or three new Kick-Ass people. I'm all about that. + +00:20:00 + +Tyler Wright: yeah, I would decide to that to Scott's Point earlier about funding I think we've all said it but I think a number like 2000 to 2500 makes a lot of sense because when we want to use this program is we want to keep the dollars and cents of each ask. + +Tyler Wright: Kind of small and have this be an incubator program for things that eventually would come from community pool spend. So I love the idea of funding this and we don't have to go through a community pool right now. It's just like there's funds there a lot for this kind of stuff if the program has legs and continues to be successful. Then we take the next steps and we have this case study. We're not asking for community pool funding just out of nowhere. It's just like hey, we had 2500 dollars. We are trying to hundred and akt and so what we did in the month and a half we brought on two new insiders and a Vanguard that's contributed X Y and Z, and we've gotten X number of eyes on it to the latter point and then Benjamin, I'll hop it over to you. + +Tyler Wright: To the latter point about success. I think we hit it on the head just like trying to find if we could find two or three more insiders that are technical or if somebody from zealy is able to do some sort of bounty or some sort of bigger task like notification tool or something that improves the network even one. I think that would be successful for the dollar amount and we're looking to spend I think it's easy to scale it from there. Or so go ahead Benjamin. + +Benjamin B: I just wanted to ask something here. If we were to actually go through with this should we make that Robert would be the one in lead since he's been creating some of the documents and the Robert can have a free handle the bit on how to create this budget and help spend the money and then we could try to work together everyone interested in. All this smaller details, like what should the tasks be related to how could we get the greater results and how could we reach out to a lot of people? + +Tyler Wright: I would certainly say that Roberts should be the owner and the boss. I would ask that and this is what we've been trying to do with the entire open framework that some of these decisions. I'm not saying that you weren't saying it's bad but somebody's decisions just get made as a group because it just works better that way then a singular person making decision and then letting people know later and then we could have just gotten group feedback. So I believe that Robert should be the owner and kind of be the manager but then some of this decision has relate to tasks that relate to just general budgets in the short-term and long term. I think should just be done as working group sessions where lazy agenda Robert lease is through but again, we can make these decisions and have action I have to come out of this as a group. + +Scott Hewitson: Go ahead Benmin. sorry. + +Benjamin B: Yeah, if this sounds good to me and the last thing I want to ask Harry start related to how much should be spent on the tasks. And how much should we spend on the admin? Should this be done in the working groups Maybe? + +Scott Hewitson: as far as the breakout of funds yeah,… + +Benjamin B: Yes. + +Scott Hewitson: I mean, we're kind of having the conversation now, personally I think if we start with 2500 if that's 2,000 towards the + +Scott Hewitson: towards rewards and 500 bucks for people's time. if that sounds crazy tell me I don't know, and we've got these different funding mechanisms and I want to try to use it as much as possible. But I also want to be respectful of people's time. And I know here is said a couple month ordeal and I don't want you guys to be doing all this work and not getting any compensation for yourselves either kind of just leaning on you guys a little bit to + +00:25:00 + +Scott Hewitson: Hey, this is what we think and I like giving people autonomy. I like giving you get the most out of people when you trust them and you can when they give them their own devices to succeed or fail and then after there. It's like all right, we know it was a failure or we know is a success and it is a decent amount of money, but it's not like it's the whole community pool. off the top of you guys' heads. How do you see let's just throw out the 2500 right now. how would you do it? If you had the keys to the castle today to this disperse that 2500? + +Tyler Wright: Benjamin Sorry real quick before you speak because Scott just brought up a great point. I just want to reiterate and I wanted to Huey has been done a great job of providing transparency and I accountability as it takes the community pool and holding whether it be overclock accountable or members of the community accountable. I try to do my best to make sure that people are doing what they say that they're going to be doing. So whoever takes on this management job just know that it comes with a little bit like being an owner comes with responsibility and Huey and I are going to make sure that we hold people accountable, as stewards of + +Tyler Wright: the open source of caution Network, we do not want funds to just spend on wisely and we're We're doing the same thing for technical development. We're doing the same thing for everything that comes out of that community pool everything that can get upon about it retains to the akt Token. There's some care behind the scenes that's being taken. So there is going to be some accountability for this position, if somebody's like we're happy to pay anybody for their time and their energy, but if you say I'm going to do x y a and you're certainly getting paid from again public funds, Harry and I both come from + +Tyler Wright: a different world where dollars and cents actually matter and people have to be held accountable when they use those dollars and cents. So we will be holding people accountable. I just want to let people know that before 2024 starts. + +Robert Del Rey: And thanks that a great point. + +Scott Hewitson: go ahead Benjamin. + +Benjamin B: I want to say that. Yes. I think we should even have a round of applause for Scott here. + +Benjamin B: I don't even know if it can hear it anyways. + +Scott Hewitson: I can see it. + +Scott Hewitson: I can see it. I appreciate it. + +Benjamin B: Great. + +Benjamin B: Back to the question if I had the keys to the treasury to the two and a half Kate treasure, I would do something similar. I would either do I would depending on how large these prices would be and how many you'd estimate the program to have I would either have between 500 to the free admins unless there will be more or 1000 between the free elements. I think that both of those. Somewhere around in that range would be a good. starting point for the pilot + +Scott Hewitson: About 750 so it's 250 API a pop for the three of three folks in here doing it. And then that gives us 1750 in rewards and for a budgets and tasks + +Tyler Wright: I think that makes sense. I also think that if everybody agrees that we should not be promoting the Shilling. I don't think we should give a single Cent for somebody following us on Twitter unless it's a prerequisite of the platform and we should just focus on just some of those smaller bounties maybe we're getting doing something that benefits of network and maybe to be just a price maybe if somebody updates documentation. It's five akt. I don't know. Maybe we can get some more value from this zealy community. So just want to put that out there. Go ahead Benjamin. + +Benjamin B: I think that it could make sense to pay people to have to follow on Twitter as well. But from what I've heard you can have this minimum ranges. So if you only get 50 points, you won't get paid. But as soon as you hit a certain threshold, you will get paid for everything. So then maybe just following and just doing this small things. They won't give you anything. But if you do something and also do the small things you will get a little for everything. So if having people get connected with a coach Community is worth something. I think that we could add just a tiny tiny bits to making them follow as well. + +00:30:00 + +Scott Hewitson: Yeah, I mean, I agree with that. It's like if you need 30 points to get paid anything and it's 25 to deploy something and then it's five to share and then that gets you to 30. I think that's reasonable. But yeah, it's to your point. It's like if all the easy Bounty Hunter airdrop Style Tasks, you can get full payout based off of that then we're just gonna attract those kinds of people. + +Scott Hewitson: Thanks for taking notes Robert. Appreciate you. + +Scott Hewitson: I mean, I'm excited. I think let's press with it. I'm cool with let's do 2500 750 of that for admin and 1750 for Rewards is that sound all right with everyone is that any adjustments or? + +Scott Hewitson: Okay. + +Robert Del Rey: However, if it's straight for this pilot, thanks, Scott. + +Scott Hewitson: Of course, I guess the next step is because we've got a 70% solution. We kind of know what we want to do a little bit. I'd like to let's see. I mean we can call it a bounty and I can have have it sent out this week before November for sure probably wait till a little drawback in price so that we get the most akt out of it. so for next steps, do you guys want to schedule another one of these calls in a couple weeks? Do you want to do it? Async? Do you want to I think the next step would be coming up with a formalized plan and then that we can all review and press with. What's up, Robert? + +Robert Del Rey: I agree 100% and Monday is great for this goal. Maybe we can make it green now. And next Monday. We can give you some updates and when I say we are Benjamin. ation, and of course myself + +Scott Hewitson: Of course the boss man. + +Robert Del Rey: Thanks, Lord. + +Scott Hewitson: That sounds great. + +Robert Del Rey: Yeah. + +Scott Hewitson: Tyler do you have anything else you want to add? + +Tyler Wright: No, I think you just said we can turn this into a weekly meeting. Until we get this program kind of off the ground I think as a strategy document for next week, and then it's success documents. for next week would be great. I think the goal of this pilot is to See if it can get some momentum on zealy and turn this into something that gets community pool funding on a year over year basis because it's just a part of the community success program. So really looking forward to it. I'll put some time on the calendar. And at least we'll have a couple meetings maybe over the next three or four weeks. We'll have a meeting on this and next week is still November. So maybe my next week. maybe you talk about this. I don't just run for a quick second to chase a dog. + +Tyler Wright: Maybe there's a specific wallet that gets spun up for this and we can look to get this funded for next week. Especially for one do this in November, but I'll give us the next week to figure out strategy and we can maybe share some documents async this week. And this look to me next week if that works for everybody. + +Scott Hewitson: Okay works for me. Yeah, I think it's one of you guys want to hold the funds you can have fun send over. Like I said, I'll probably wait till a little drawback. we'll see what happens on akt's kind of mooning right now. + +Tyler Wright: Yeah. + +Scott Hewitson: but Yeah,… + +Robert Del Rey: It's crazy. + +Scott Hewitson: I know right? + +Tyler Wright: No, but I think that's a good plan. Maybe Robert you spin up the wallet as the owner and then it'll be part of your own responsibilities to pay out the rest of the management team. But again, we can make sure that gets done and we could talk about a little bit more about that next week from an operational standpoint, but the focus of next week's conversation should just be on strategy and implementation. + +00:35:00 + +Robert Del Rey: Absolutely. Awesome. + +Scott Hewitson: Sounds good. of + +Robert Del Rey: Thank you so much guys, Fury. Really really appreciate it. + +Tyler Wright: + +Scott Hewitson: we appreciate mean, we've got all these mechanisms for funding, it behooves us to use them. If not, then what are we doing? + +Tyler Wright: plus one. + +Robert Del Rey: Okay, yeah. + +Benjamin B: Okay, yeah. The super fun to see that this actually worked out with the funding and everything. I believe that for the remainder of the 4K in this month's budget. You can just send that to me. I have a little room for a one and… + +Scott Hewitson: Okay. + +Benjamin B: a half K in one of my wallets. Just send me a message. + +Scott Hewitson: You have just enough room,… + +Tyler Wright: but + +Scott Hewitson: speaking. I wanted to mention so we've kind of bring it back to + +Robert Del Rey: They're gonna send it to me and I think we posted. + +Scott Hewitson: yeah, there we go. I trust you guys. No, just talking about the bounties. So, it started as a let's get a little bit of money in one of the props so that we can do certain things bounties. Whatever part of that has been, we kind of just been going one to one with people kind of I've been telling people on the ternal side. Hey, if you need things done, you need small tasks. Let me know that I know let the community know we've got money to use it coming out this week. Hopefully is we're gonna Define the program a little bit more for bounties if you guys have seen The cohesive product and Engineering roadmap. We're looking to put out something that looks very similar to that but + +Scott Hewitson: from the community side and then it's like we'll have tat there will be backlog items up next items in progress items and then kind of to show one what core team is working on in the marketing Community side, but also where those gaps are and it'll call out Bounty specifically. So I think it's gonna get a lot cleaner A lot more efficient for the bounties. But because we are where we are today, let's spend some money doing some stuff that we think will progress the network. So Look forward to releasing that and if you guys have any questions comments concerns, please please please let me know that Ty know and we'll try to address some best we can. + +Robert Del Rey: Thank you so much and start Tyler George Benji. I guess we are right on time this book about a lot. I noted a few things down. Also, this call is being recorded in transcribed. Hopefully the people are then join now can listen to it and maybe we have more people but operating. Let's see how that goes. In case you have any extra comments concerns questions regrets. Also, feel free to drop any message in the city of channel, right? + +Scott Hewitson: That was good. + +Tyler Wright: Thank you all I'll add some time for next week or in the following weeks. But if this works for everybody, then we'll do the same time next week. We'll see you then. And thank you. + +Robert Del Rey: Thank you, Tyler. + +Benjamin B: Awesome. Thank you everyone. + +Scott Hewitson: All right. Have a great day everybody. + +Robert Del Rey: Stay safe guys. Bye-bye. + +Tyler Wright: ever over + +Benjamin B: but + +Scott Hewitson: right + +Meeting ended after 00:39:13 👋 diff --git a/wg-zealy/meetings/003-2023-11-27.md b/wg-zealy/meetings/003-2023-11-27.md new file mode 100644 index 00000000..a2453466 --- /dev/null +++ b/wg-zealy/meetings/003-2023-11-27.md @@ -0,0 +1,473 @@ +# Akash Network - Zealy Working Group (WG) - Meeting #3 + +## Agenda +- Overview of the Zealy platform. +- Discussions of Zealy missions and the overall pilot phase +- Progress Updates + +## Meeting Details +- Date: Monday, November 27, 2023 +- Time: 6:00 AM PT (Pacific Time) +- [Recording](https://47vhtsd36l63wlteorhccwvklpzihemikfrxljg6mebv2myt7bzq.arweave.net/5-p5yHvy_bsuZHROIVqqW_KDkYhRY3Wk3mEDXTMT-HM) +- [Transcript](#transcript) + +## Participants +- Benjamin B +- George Pro +- Robert Del Rey +- Scott Hewitson +- Tyler Wright + +# Meeting Notes + +### Progress Updates: +##### Robert Del Rey: +- Worked with Benjamin on new missions and finding the right balance between mission quality and pricing. +- Shared that they presented a quick overview and budget for the initial pilot last week. +- Shared the Zealy dashboard, presenting the gathered missions (12 complete + 2 ideas, totaling 14 missions). +- Initially priced missions at 25, 50, and 100 AKT; later reduced based on feedback for better budget utilization and broader participation. +- Average mission price now between 5 and 10 AKT. +- Emphasized the fairness of the current prices, considering the value of AKT. +- Worked on strategies for sharing missions. +- Aimed to discuss and polish the Zealy document for GitHub upload. +- Mentioned the importance of GitHub for Akash discussions. +- Expresses the desire to upload the document to GitHub to initiate community feedback. +- Robert Del Rey successfully shared the Zealy dashboard. +- Highlighted a favorite mission, emphasizing its purpose of earning experience points rather than AKT. +- Explained a mission involving Osmosis swap for AKT, providing a simple entry point for users. +- Stressed the importance of missions for accessing Zealy, citing the Osmosis swap mission as an easy starting point. +- Robert Del Rey acknowledged the importance of finding a balance between specific mission requirements and allowing participants the freedom to create. +- Stressed the goal of getting users to engage with Akash, regardless of the project's nature. +- Supported the ideas of creating personal Docker projects and contributing to Awesome Akash. +- Robert Del Rey demonstrated the Zealy platform, showcasing the missions, both pending and in the history section. +- Discussed the mission review process, including mission descriptions and user submissions. + +### KPI Discussion and Launch Plan: +Robert Del Rey: +- Expressed readiness to launch the Zealy pilot today, believing there's enough material. +- Outlined the plan to run the pilot for two weeks and then share statistics with the team. +- Mentioned ongoing discussions about KPIs ideas and feedback but emphasized the need to start now due to the approaching holiday season. +- Urged the team to take advantage of the two weeks before the Christmas mode to kickstart the Zealy pilot. +- Emphasized the initial focus on attracting and engaging the existing community before expanding to a broader audience. +- Stressed the importance of keeping the initiative in-house initially. +- Discussed the plan to review missions with Benjamin one week after completion and initiate reward payouts after ensuring mission quality and funding availability. +- Shared the intention of attracting active participants within the community to increase engagement. +- Acknowledged the progress made in organizing the Zealy dashboard over the past week, with categories evolving as missions progressed. +- Discussed changes in mission categories over time, noting shifts from stages to categories like onboarding, deploy on Akash, etc. +- Highlighted the difference in missions between "Deploy on Akash" and "Akash to You," mentioning the latter doesn't provide AKT but offers XP points. + +### Feedback from Benjamin B: +- Benjamin raised a concern about the first task targeting Cosmos-based coins, potentially excluding those outside the Cosmos ecosystem. +- Robert acknowledged the point and expressed openness to addressing the issue. +- Benjamin suggested using a testnet faucet to make the mission accessible to a broader audience. +- Robert agreed to implement the suggested change to ensure inclusivity. +- Beniamin suggested introducing missions related to creating unique projects rather than generic tasks. +- Emphasized the need for missions that target building something specific and unique, not just deploying templates. +- Proposed missions like creating one's app and deploying it on Akash, contributing to Awesome Akash, or Dockerizing a personal project. + +### Tyler Wright's Feedback and Suggestions: +- Tyler expressed appreciation for the initiative and proposed missions. +- Suggested adjusting specific missions to align with broader Akash goals, SIGs, and working group initiatives, including hackathons, events, and educational programs. +- Discussed the current approval status of the pilot and phase one through bounties. +- Proposed focusing on user acquisition and interaction rather than immediate discussions for additional funds. +- Advocated for the primary focus of Zealy to be onboarding new users rather than engaging insiders or vanguards. +- Highlighted the need to reach individuals on the fringes or outside the community to broaden participation. +- Encouraged utilizing Zealy as a platform to attract individuals interested in learning about Akash. +- Discussed the idea of a testnet provider as part of the missions and recommended connecting wallets to Cloudmos. +- Tyler agreed with the suggestion and further proposed creating Dockerized projects, contributing to Awesome Akash, and building unique SDLs. +- Encouraged missions that contribute to the Akash ecosystem and benefit others. + +### Scott Hewitson's Feedback and Suggestions: +- Scott commended the team for turning around the project in a week, emphasizing the value of quick learning, adjustments, and deployment. +- Express excitement about the potential traffic and the ability to pivot quickly as needed. +- Robert Dechoed the excitement and expressed anticipation for the upcoming pilot. +- Scott Hdiscussed the next steps, suggesting fund allocation for contributors like Robert and Benjamin. +- Robert committed to creating a wallet post-call for fund allocation. +- Participants confirmed that the current meeting time worked well for them. +- Scott suggested considering a cap for rewards initially to manage potential high participation. +- The idea is seen as a starting point to gauge interest and potentially request additional funding based on community engagement. +### Discussion on Mission Submission: +- Robert Examined a specific mission where a user installed the CLI, and discussed the submission in detail. +- Tyler outlined next steps, including creating a wallet, transferring funds, testing, and sharing messaging in different channels. +- Tyler emphasized the need for documentation links and optimizing the review process. +- Tyler suggested adding structure and clarity to mission instructions to prevent potential abuse. +- Tyler suggested cutting missions related to persistence storage and three persistence storage for the time being +- Encouraged creating an SDL and adding relevant missions to Awesome Akash. +- Tyler suggested leveraging Zealy's community channels and creating documentation for clarity. +- Tyler recommended optimizing the review process, clarifying submission formats, and maintaining operational structure. + +### Exploring Additional Missions: +- Scott mentioned the presence of a text-to-image model in the deploy section, highlighting the aim to make users comfortable and excited about using Akash. +- The discussion emphasized creating missions that serve as gateways to the broader Akash community. +- Consideration of stable diffusion missions and the potential for adding them to Zealy. +- Discussion of the idea to have a stable diffusion mission, potentially with a requirement for users to earn a minimum amount of experience points (XP) before receiving rewards. +- The proposal received positive feedback, and it was agreed that a minimum XP requirement could be a good approach. +- Acknowledgment of the importance of clear guidelines for users to earn rewards. +### Other Matters Discussed +#### Spam Protection Discussion: +- The team discussed the potential for spam submissions and the need for spam protection in Zealy. +- Reference was made to experiences in other communities, such as UMe and A Staking, where spam protection strategies were employed. +- It was acknowledged that spam levels could depend on the size of the community and the types of missions shared. +- The Zealy Academy was noted for its educational approach, with weekly calls and community managers providing valuable insights. +- Tyler raised concerns about potential spam submissions in Zealy, emphasizing the need to address it promptly. +- A plan of action was suggested to mitigate spam, including a quick response and potential adjustments to experience points or other measures to prevent abuse. +- Tyler expressed appreciation for Ben's support, noting that it has been crucial in the project's progress. +- Robert thanked Ben for his support, emphasizing the significance of his contributions. +- Tyler conveyed gratitude for the teamwork and collaboration. +- Robert expressed his thanks, acknowledging the importance of everyone's efforts in the project. +## Action Item +- Robert to initiate the launch of the Zealy pilot. +- Group to run the pilot for two weeks and compile statistics. +- Robert to optimize mission instructions and format for submissions. + + +# **Transcript** + +_This editable transcript was computer generated and might contain errors. People can also change the text after it was created._ + +Robert Del Rey: Alright, alright. Alright. Hello guys, Happy Monday. Welcome to this. silly working group call Last week we had our first pilot test I guess this is the second call we do and today is gonna be really fun. Because last week we kind of presented the general idea quick overview of the idea some folks of the idea. And also what could be a possible budget for this initial pilot. So this past week I was working with Benji. + +Robert Del Rey: Coming up with New Missions getting the right balance between a good Mission. And what would be a good price for the mission when people do them? We also work in some strategies to share those and those are The main topic I want to discuss with you guys. So without further Ado, I will go ahead and get right into it. And yeah. + +Robert Del Rey: I'm sharing attached this not This is the silly dashboard here you will be able to see the missions We Gather so far at the moment we have. 12 complete missions plus two more missions ideas making it 14 missions total. and the prices initially there they were + +Robert Del Rey: 25 50 akt 100 AKP and after a few feedbacks we reduce the price. That way we can make more use of our budget and more people have a chance to get something out of the missions. So right now the average permission is between five and 10 akd, which I believe is still very fair since ikashi's over a dollar or ready and five bucks. It's a monthly subscription in anything. So, I believe it's a fair price. Thank you rotary for your ideas. You really helped me a lot in trying to get the best number. Another thing we were working on last week was let me open up my notion now. + +Robert Del Rey: I wasn't ready for this call guys. I mean I was reading something I was planning to get a shower and when I saw I just got the notification like hey your city call is just a status. So please bear with me. I wasn't 100% ready for this call. + +Scott Hewitson: You do it you're doing great. You doing great. Yeah. + +Robert Del Rey: Thanks Scott you you're the man? so yeah guys, this is the dashboard. Let me share the screen better. Right. I have Microsoft Edge the entire screen. Let's go with entire screen. I'm sharing now and you should be able to see the notion page I have for the silly pilot. So what I wanted to talk about in this call, yeah is this I wanted to present this to Tyler and the guys and shared the actual pot the action plan. I want to polish out the silly document a little more. + +Robert Del Rey: So that I can upload it to GitHub. and the reason I want to upload it to git Hobbies because we are doing 95% of a cash discussions on GitHub. So I believe it's a good idea if we just go ahead and upload this to GitHub right away after a few weeks and start getting Community feedback now. And yeah, that's my mission. If it's for me, we can launch this today. I don't mind. I believe we have enough material to launch today. Okay. Do you see the city dashboard now + +Tyler Wright: No, we're just still see your notion screen. + +Robert Del Rey: You still see the ocean? Okay, let me fix that. I swear I click on entire as screen. I see I have Some screens now. I got it. That was the shortcut. Okay, okay. + +Robert Del Rey: Let's do this. guys, we're live. Okay, we're with me. + +00:05:00 + +Robert Del Rey: I have + +Robert Del Rey: okay, I will try Let me know if you see the Sealy. dashboard now + +Scott Hewitson: I see it. + +Tyler Wright: Yes. + +Robert Del Rey: Thank you guys. this is one of my favorite missions. This one doesn't get you any akt. But we'll get you some experience points can be used for something later down the line. I guess. It's really simple just go to osmosis swap some token for akd and you the transaction hash link, you're upload it here and that gives you a hundred XP. I guess it's a good mission to get started because with C, for example, you cannot search for this and join right away. + +Robert Del Rey: The only way to join it's doing a mission. So I believe this is a good mission to just join the city dashboard. You can start with any mission right? But I believe if you do this one first, it's gonna be easy simple and people will do it quickly and they will get access without much hassle in my honest opinion. So guys what I was saying before sharing you this screen is that I'm planning to start this today running for And after two weeks, I will share some stats with you. + +Robert Del Rey: I asked for some kpis ideas and feedbacks for some kpis. We're still working on that but I believe we should use time and start this now because people are going into holiday season some of them try to relax some of them just disappear from the market altogether. So I guess we have to take advantage of these two weeks before we go full into Christmas mode in my opinion. So I will go ahead and start sharing this missions on Twitter on telegram on a cache Discord. And the main focus for me is attracting people that are part of the community. And the reason why studies because I want them to become more active. I want to keep this in house initially. + +Robert Del Rey: And then once we got a few people doing the missions and rewarding akt, we can go ahead and expand this to a cash social media and share that on social media and potentially reaching more people. Yeah, after those two weeks. We're gonna review the missions when I say, I'm referring to Benji and I we're gonna review the missions and One week after we are done. We're gonna paid out those rewards so we can have enough time to review the missions to make sure they are quality missions and to make sure we have the funding to start giving away the rewards instead of giving them + +Robert Del Rey: Right away. offer between how we review the missions and then paint out the reward. It's gonna be fine. And yeah, I know I said a lot in five minutes, but that's my general idea of silly how we can get started how we can follow up and now it's the time for your input guys. I love to know what you think about now after a complete week pass now, you can see there is more order in the city dashboard. We have some missions the categories change. We had one stage to a stage stage 3 the category change for onboarding deploy on a cash in you and a cash account. + +Robert Del Rey: And depending on the category that missions are going to be different in the deployed my cash. I have more missions because I guess those were easier to think about and come up with. But Akashi to you, if you notice this one doesn't pay any AKP, but if you some XP points, so just still gonna get something out of it if you do it. I guess also we can complement other initiatives using silly. For example, if there are bounties we can create a bounty category and just respond is there so when people access they will know exactly where to go to find the bounties or to find the missions that they're gonna + +00:10:00 + +Robert Del Rey: So yeah, I'm done. it's your turn to do the talking. I see some hands race which I love thank you. I don't know who raised the hands first. So guys be gentlemen's whoever raised the hands. First go first,… + +Tyler Wright: Go ahead Ben. + +Robert Del Rey: please. All right. + +Benjamin B: All right, that makes me I wanted to say that for the first task for the initial one to get the rest of the dashboard. If we do what you plan for that to have the house from swapping will be osmosis. We are only targeting people who over they have. Cosmos based coins is this intentional or not? + +Robert Del Rey: That's a good point Maybe wasn't intentional. But now that you mention it you're right, maybe this. Can only be inviting to people in the cosmos ecosystem and could push away people outside. The customer's ecosystem. However, I guess she's a cosmos based project even though we try to extend out on our own Akashi Cecilia Customs project. So I don't believe it's gonna be an issue at least in this first stage. That's what I think although it's a great observation I didn't notice until you mention it. + +Benjamin B: Yeah, I think we could solve this if you wanted to because there is a testament force it and I believe that you get from using that test net force it so by just changing the text and the leading them to that force it you could just have the same Mission but for testnet users so If you want that's to happen. They will just open the faucet. They'll write their akt address. And they will get the testnet funds there and they will get onboarded to the dashboard. + +Robert Del Rey: Okay, I like that Let's do it. Whatever makes these more accessible to people I'm all ears. So thank you for that in poop. And you? + +Robert Del Rey: + +Tyler Wright: excellent Yeah,… + +Robert Del Rey: Alright Tyler they get away. + +Tyler Wright: I really like what you put together here. Obviously, we can adjust some of the specific missions to I like what you just said actually just a minute or so ago about aligning with whether it be Akash goals or other cigs and working groups initiatives, whether it be hackathon events, whatever, the edu program we can add this kind of programming. So I really like that. I do want to change some of these specific missions and from an overarching standpoint. I am curious right because right now it seems like The pilot and Huey, correct me if I'm wrong, but at least the pilot and phase one has been approved via the bounties. + +Tyler Wright: I'm not really sure we need to necessarily go to discussions with anything at this point. I think that we can have the pilot start to get some users interacting with dealing and figure out from there. If you want to have a wire discussion to get more funds to face to but I think the focus should just be getting users. And frankly, I'm not saying that we shouldn't have insiders and vanguards and folks like that interact with this. as quickly as possible, but I feel like the focus of zealy should be about onboarding new people, like wow. + +Tyler Wright: It's great Robert for you to do a mission. There's other ways that I can get you you join all the Insiders meetings. You're already engaged. I think at least to me the point of zealy was to get more folks like you that are not involved yet and maybe need that push and zealy could be a push of I can do something and learn about a project. I think it's interesting and want to be involved with but I can also earn some akt or some experience points or it could be game of fine in the way. So I would like for us and this is just my opinion for even out of the gates, maybe social media is good. But I would like for us to try to insert ourselves and to other communities and said, join our zealy, or put this in the general chat and say hey, if you're looking for a way to get involved, here's another way to get involved be a zealy and look for people that are either on the fringes of the community or outside of the community versus people like yourself or Benjamin. + +00:15:00 + +Tyler Wright: George that are really accountable reliable and already very engaged And I'm not saying you all can't do the activities, but I think we want to find more people like you as opposed to just continue to give you akt, which we could do. In other ways. I think + +Robert Del Rey: Absolutely meant agree 100% Thank you for that. I mean, right. I read a few. + +Tyler Wright: Yeah, I really like the idea. + +Robert Del Rey: things down your hand up. + +Tyler Wright: I really like the idea of a test net provider. I don't know what installed Cloud most is because I feel like most people are now using the web app. So is that just connecting? Maybe it should be connect your wallet to Cloud most or something like that either Kepler or leap, and they can do that, Because yeah, I don't think many people are using. + +Tyler Wright: The downloaded version anymore. I think that people just use a web app. + +Robert Del Rey: Okay, I wasn't aware of that that tells you how long I go was the last time I used cloudbus. + +Tyler Wright: Yeah. Yeah, I think you have to attach your wallet to be able to effectively do anything in Cloud Wells… + +Robert Del Rey: Thank you for that. + +Tyler Wright: which I don't really love but Yeah, that could be an experience or an activity in itself is like they're connecting their wallet. + +Tyler Wright: And then you can access the cost of living. + +Tyler Wright: Go ahead Ben. + +Benjamin B: I would like some missions also related to creating something of their own here everything you can do by just the following steps kind of but there's nothing and that's Target's creating something unique. We have the deployed WordPress website, but it should be something specific but just rather it should just be the template. I would like these missions to be greater. So your own app and deploy it to my gosh maybe even if it's super simple. + +Tyler Wright: Yeah, I would agree with that. I create your own sdl create dockerized something that you have or contribute to awesome Akash, if there's something that you don't want to do it's not your own website create something that can be added to awesome I think these are great examples Benjamin. I agree with you, wholeheartedly of things that should be specific missions, I would actually vote and this is just again my opinion up for discussion vote against having people doing generic things maybe + +Tyler Wright: one of the simple games from awesome Akash can be at a starter mission for folks so that people can interact with learning how to deploy and see a deployment up and running very quickly, but I don't know if we want people just like trying to earn five akt and doing something for 10 seconds, I think we want people contributing to the ecosystem really like doing things to other people can benefit from + +Robert Del Rey: thanks, the + +Robert Del Rey: And I agree 100% with you guys and that's why I believe it's so critical to find that balance. I also don't want people to do just deploy whatever. Shed, they think about and let me claim my stuff, right? So yeah, we gotta be super specific in what we're looking for. But we're gonna find a way to let people be themselves and build whatever stuff they want to build because they keep for me. The key thing is that Having them using a cache. That's what I want to do initially or at least that is one of my main goals make them use a cash doesn't matter what they do. But make them use a cash and I love your ideas guys, create your own Docker. Is that okay? If I say that and contribute to us some awesome my cash. I believe are great ideas for other missions. + +Robert Del Rey: The keyword, it's like own your own and stuff I guess that gives people the space they need to create whatever they want to build and still build something useful. + +Robert Del Rey: The other comments or feedbacks guys. + +Scott Hewitson: I'll just stay. I mean it looks great, turning it around in a week. This is Exactly the kind of stuff, we want to use. In my mind, if we can do a little pilot programs like this, it's quickly learn quickly adjust quickly, Redeploy, whatever we're doing. No, I like it a lot. I think we just, keep moving fast and I'm excited to see what kind of traffic we can get. + +00:20:00 + +Robert Del Rey: Yeah. + +Scott Hewitson: I need to Pivot we can pivot so I'm happy about it. + +Robert Del Rey: It's interesting man for I'm also very much looking forward to it. Hey My brother, I know you are super busy. Sometimes George's super both in a cash groups making notes. He also has his own communities. So my bad George because I believe I assigned this to you without properly asking you how you could contribute to this project. So I'm using this platform now to ask you in front of everybody. What do you think you can do and how you want to help because I know you want to help right, but maybe you were too busy this last week to contribute with some messages. So if you could maybe let me know how you think you can help us and we can go from there That is very straight about working in a community. + +Robert Del Rey: You're muted your channel hear you if you're talking. + +Scott Hewitson: He may not be able to chat right now. but + +Robert Del Rey: Yeah, it's fine. It happens. I will send him a message. + +Scott Hewitson: good, I was gonna say since we're trying to move fast to after this, we can start. Getting y'all funds. So whether Robert if you want to hold it or Benji George, just let me know and we'll get that. Paid out and we can just start tracking from there. We've got quite a big dip right now on akt, so I want to do it now. + +Robert Del Rey: Alright, I will go ahead and create the wallet after this call and send it to you because I honestly didn't do… + +Scott Hewitson: Okay, perfect. + +Robert Del Rey: Thanks for the reminder. + +Scott Hewitson: No worries. + +Robert Del Rey: Okay, yeah. That lots of notes. Thank you so much guys, this call was great. What do you think about the time? Was it good for you? This time today this day. To have in this call. + +Scott Hewitson: Yes, that's fine for me. + +Benjamin B: yeah, it worked for me as + +Robert Del Rey: For me, it's also fine. + +Robert Del Rey: Awesome, that's good to hear George thumbs up seems that this time is also good for him. Thanks Tyler for arranging this again. And yeah. reviews one Okay, someone did a mission already. + +Scott Hewitson: I love it. + +Robert Del Rey: I have she 21 + +Scott Hewitson: I love it. It's not even on blast yet and people are already doing stuff. + +Robert Del Rey: Yes, yes,… + +Tyler Wright: Yeah. + +Robert Del Rey: so let's go ahead and use this so you can see how the missions look like when you're reviewing them. For example, you see pending and history here. You can see all the missions that the community has done in the past. Really nice. Remember I've been doing this since August. So it's understandable. You're gonna see very old missions here. This one was claimed three months ago. Really good. Now the one that are pending for review are gonna appear here as you can see it's suspending. You click on the mission. This is the mission description. This is the same that the person so when they initially saw the mission. And this is the submission depending on. + +Robert Del Rey: On the depending on the submission type type People can submit links images they can do certain actions. and this person uploaded a link. I'm a scare now to click on this because it doesn't look familiar to me at all. But yeah, I'm gonna take this one for you guys. Let's see where this takes. Okay. What is this guys? Do you know? + +Benjamin B: Yeah, it's someone that installed the CL. + +Robert Del Rey: awesome Really cool. It seems this is a screenshot that was uploaded as a link I believe. or not am I tripping? + +00:25:00 + +Tyler Wright: Yes, I think it is a screenshot that was updated as a link in the shortened. + +Scott Hewitson: You're right. + +Tyler Wright: I would love and I have to play around with zealy this week. I think as here. We just have one. I think those are next steps is creating a wallet us transferring the funds over to you ASAP while there's a dip and before December starts and then doing some testing and you sharing some messaging in different channels. It looks like zealy has their own Community, which we should also try to leverage as well. So those are action items. + +Robert Del Rey: yes. + +Tyler Wright: I would love to make sure that and I don't know if this is the combined effort with George and you or the three of you but I would love to make sure that there's documentation. I think for some of these it's already linked but make sure that there's documentation links for everything and then + +Tyler Wright: it just optimize the review process so that you're not opening Scary links, make sure that the formatting exactly what you want hey put the screenshot on this kind of format or whatever. Try to create as much operational structure as possible. So that it leaves zero little room for people to. Abuse, I would add all the classes from the edu to that edu section. + +Robert Del Rey: he + +Tyler Wright: Three persistence storage. I probably cut that one for the time being. + +Robert Del Rey: Sure, I can do that, right? + +Tyler Wright: Here, let's cut that one, too. + +Robert Del Rey: No worries. + +Robert Del Rey: Those were the only two missions that were not completed after that. All these ones have descriptions the prices and stuff. I will take your advice Tyler and make sure the instructions are clear. We have the correct links. And also we have an specific format for submissions. So we know… + +Tyler Wright: Yeah. + +Robert Del Rey: what to expect when people submit stuff. + +Tyler Wright: exactly … + +Robert Del Rey: Thank you so much. + +Tyler Wright: please my pleasure. Maybe you should have as again the stuff I just talked about created an sdl and awesome Akash or something some of those things. We just talked about I think that you'll add those later. Huey anybody else here on the calls or anything else? I'm trying to think of something like AI ml specific should build an sdl like an AI. Fbl, + +Scott Hewitson: He has a text to image model on the deploy section. + +Tyler Wright: Okay, cool. + +Scott Hewitson: Yeah. Yeah, I mean we're just want people to get familiar get comfortable be like, this actually is kind of cool and get a little paid to do it and… + +Tyler Wright: Yeah. + +Scott Hewitson: then that can be The gateway drug to the rest of a cash. + +Tyler Wright: Love that. + +Robert Del Rey: the bigger Community absolutely meant great point What about a stable the future guys? + +Scott Hewitson: exactly + +Robert Del Rey: I saw a tweet yesterday from my cash and establish the future images. Do we have one of those meetings too? + +Scott Hewitson: as a stable video or stable video diffusion. that's like I want to say ZJ made a I personally + +Robert Del Rey: Yeah, yeah, I'm thinking about him when saying this. + +Tyler Wright: There's sdxl.acost.network, we can have that as a simple mission of make an image on there and it could be for experience points, which uses your cost Network. + +Robert Del Rey: let me look it up. + +Benjamin B: And we could make up they must do certain things to get their XP to maybe 500 before getting any rewards. + +Scott Hewitson: Actually like that one. + +Tyler Wright: Yeah, for sure for sure. + +Robert Del Rey: Okay, that's gonna be easy. and I like that minimum XP to earn the right to get akt, right, so + +Tyler Wright: exactly + +Robert Del Rey: Thank you for your input guys. Do access to AKA rewards? Yeah, That makes sense. And I was here in Tweeteria the stable video diffusion exactly. Yeah, you were right Scott. Thank you so much. I don't know how this works or… + +Scott Hewitson: Got you. + +Robert Del Rey: what they do it, but maybe we can add one stable diffusion mission to the ceiling. I don't mind maybe see he's gonna like that one. + +00:30:00 + +Scott Hewitson: I mean, I think where it's at today is a great starting point. I mean, we've got quite a few missions to get a little bit of akt and get started and I think maybe the only thing that we should say is there may be a cap for rewards right now or something just in the best case where we get a ton of people and then it's like okay then that gives us good ammo to go forward and ask for more money. + +Tyler Wright: I think that's a great call out. + +Robert Del Rey: Yeah, that's true. Because even if it's the mission is just five akd imagine 1000 people do it. so yeah,… + +Tyler Wright: Yeah. + +Scott Hewitson: Because those are good problems. + +Robert Del Rey: I feel. + +Robert Del Rey: Yeah, Absolutely. But Yahoo, is saying thank you so much for coming that out. + +Benjamin B: I'm gonna create some of these and I can claim all rewards myself. + +Scott Hewitson: Okay. gamify the game + +Robert Del Rey: But that sounds like something I know you would do Benji. + +Benjamin B: I mean, let's be honest accept that for the authentication to zealy. We have no spam protection. + +Robert Del Rey: Yes through. + +Scott Hewitson: Correct. + +Robert Del Rey: I remember on you me I talked with Brandon. He's the community guy over there. I'm talking almost a year back when they launched this and I remember I asked him dude. What was something you wasn't expecting from lunch in this campaign and he told me that he wasn't ready for the amount of span mission that they got over there. so yeah, that's quickest story over there. You can see some of the missions they have it's read about me check out universidi. but if you notice they only Require XP points. They don't give you you meet tokens. And the reason why studies because they do or I don't know if they still do it. + +Robert Del Rey: But they do a Sprints. Let's say for this week. The one that does more XP points is gonna get extra water and people would compete to do as many missions as they can to get the required. Some of but they didn't pay you in Yumi talk and it was just experience. So people could compete in the leaderboard. so Just during that with you guys. But yeah, they got lots of spam in a staking we didn't got many spam. This was one that I spin up myself when I was with a staking. + +Robert Del Rey: And we didn't get many spam because we didn't get many people in the community that discourse was 500 people in a staking the score and you can see how many people actually interacted with it like 23 people. so yeah, I guess the amount of spam it's gonna depend on the amount of people in our community. And also what missions are we gonna share with the world because missions like retweeting in tweets and sharing and stuff they get lots of a Spam and Bots account, So yeah, you're sharing that bit of experience with These are communities that have a half joined myself and do some missions, but honestly, this is the silly Academy. I was there on April March last year + +Robert Del Rey: and it's real nice. I learned a lot from it and to join this one. You have to be part of the silly Discord and I was there they do a weekly call with the community managers are the people that have seen the communities that they run. + +Robert Del Rey: And they share great insights over there too. It's been a few months since I don't joined the cdb score, but I will definitely be joining back to share that we have a community because if I recall correctly, of course, I'm recalling correctly. They had this channel that you could promote your project and the community managers would support each other in sharing and doing some missions and just doing missions to give you the feedback. It was a really good Community. I should go ahead and join back in now that we're talking about that. So yeah. + +Robert Del Rey: Anything else guys, you want to cover this? Cause just a little recap we went over the missions the structure. You also provide me with some valuable feedback as far as missions required regard cap minimum experience in order to get the required and some missions ideas that we got ahead and translate them into silly after we're done with this call. Another thing. We spoke about was funding the wallet for this pilot and that we will take the discussions once we run this by a lot and we have more information to discuss about and guys anything else you want to go over before? I don't know we wrap this up. I guess 45 minutes is a good time for this call. + +00:35:00 + +Robert Del Rey: You tell me but we can save one hour slot like we're doing it Tyler. But if… + +Tyler Wright: Okay. + +Robert Del Rey: if we make it to 45 minutes, it's gonna be more than enough if nobody else has anything to support or to share. + +Tyler Wright: Sounds good to me. So we'll schedule another one for next Monday as well. And then we'll just continue to push forward. hopefully we can get that wallet funded today and then we can just continue to such a share some of these things. My only call out real quick is if we notice that we're getting a lot of spam and zealy, I would ask that we either connect as quickly as possible and just figure out a plan of action so that people aren't getting to the point where they're just asking for akt, we can limit that because it seems like the other project you were talking about me that had spam didn't give akt so I didn't really affect them. And you said some other products didn't have spam. I just want to make sure people start spamming looking for akt because the price is so good right now. We have a plan B to mitigate abuse. + +Robert Del Rey: Okay. + +Tyler Wright: those are something for us to think about and just like having the back of our mind whether it be to increase the amount of experience points or to do something we can figure out something in the short term, but I just want to make sure that we're just kind of on high alert and if you need Huey for that to support in any way just let us know but I just want us to have that in the back of our mind. + +Robert Del Rey: Thanks, Ben. Let me tell you your support has been Paramount. I learned that word the other day. It has been Paramount and thank you again for pushing these guys. Yeah, please. + +Tyler Wright: Please actually, thank you. + +Robert Del Rey: A schedule a call for next week. So we can follow up and check how this is doing. And let me know what you think about this maybe after next week. We can go ahead and have a bye weekly call or maybe a studying next year. We can do it on a weekly basis. I guess it's gonna depend but that's an idea. I'm having right now. And also most of the community groups working group calls are five weekly. It's only a few of them that are weekly basis, right? + +Tyler Wright: Yeah, it's only one. This is the second most of them are monthly so we can change the Cadence to monthly most of their monthly thick support is biweekly and then only working group Akash website is weekly so we can do it. However, you want to do it you're in charge, but let's just get through next week and we'll figure out from there. + +Robert Del Rey: Let's get to next week. Are you say and I'm gonna think about that. Thank you so much guys and… + +Tyler Wright: Okay. + +Robert Del Rey: I hope you enjoyed the weather over there, man. + +Scott Hewitson: Yeah, of… + +Tyler Wright: that's + +Benjamin B: yeah, it looked like + +Scott Hewitson: Actually cold in Florida right now. + +Robert Del Rey: I went. What's that Benji? + +Benjamin B: It looks like you're going to have to take the shovel out. It's snowing in back. + +Scott Hewitson: Get my shovel. That's right. + +Robert Del Rey: and possible guys both + +Tyler Wright: Alright y'all. I'm running over to Scott's website. So I'll talk to you later. + +Robert Del Rey: Right, right. + +Scott Hewitson: alrighty + +Robert Del Rey: Let's do it. It's got expected wallet address really shortly, right? + +Scott Hewitson: Sounds good. Thanks guys. + +Robert Del Rey: Talk to you guys. Bye. + +Scott Hewitson: Appreciate y'all. + +Benjamin B: Bye. + +Meeting ended after 00:39:09 👋 + diff --git a/wg-zealy/meetings/004-2023-12-04.md b/wg-zealy/meetings/004-2023-12-04.md new file mode 100644 index 00000000..ef9a2644 --- /dev/null +++ b/wg-zealy/meetings/004-2023-12-04.md @@ -0,0 +1,396 @@ +# Akash Network - Zealy Working Group (WG) - Meeting #4 + +## Agenda +- Overview of the Zealy platform. +- Discussions of Zealy missions and the overall pilot phase +- Progress Updates +## Meeting Details +- Date: Monday, December 04, 2023 +- Time: 6:00 AM PT (Pacific Time) +- [Recording](https://sq2ysituuvyyyeuuw7eawkdlbmvqpwtlkqkpogujyh5jfoxexosq.arweave.net/lDWJInSlcYwSlLfICyhrCysH2mtUFPcaicH6krrku6U) +- [Transcript](#transcript) + +## Participants +- Benjamin B +- George Pro +- Robert Del Rey +- Scott Hewitson +- Tyler Wright + +## Meeting Notes +##### Robert Del Rey: +- Robert Del Rey initiates the meeting and expresses gratitude for participants joining. +- Plans to address questions received about the Zealy campaign, social media posting, group sharing, and Mission reviewing and abuse. +- Plans to share updates on Zealy campaign questions and engagement on social media and groups. +- Notes positive engagement on social media but mentions lack of textual feedback on the Zealy Discord group. +- Proposes another round of sharing on Wednesday across social media, Zealy groups, and Akash Telegram. +- Robert addresses questions from the Akash Telegram group regarding rewards. +- Notes that common questions revolve around the timing of rewards after completing missions. +- Clarifies that rewards will be paid out on December 21st, one week after the two-week pilot concludes on December 15th. +- Expresses the need to ensure clear communication for future iterations. + +#### Scott Hewitson: +- Scott Hewitson emphasizes the importance of sticking to the established game plan. +- Mentions that in previous experiences, there are always individuals seeking faster rewards. +- Encourages the group not to feel pressured by external inputs and to stick to the planned timeline. +- Acknowledges that individuals expressing impatience may not be the target audience. +- Robert agrees with Scott Hewitson, highlighting the importance of adhering to the set dates. +- Emphasizes that deviating from the planned timeline could create a sense of entitlement among participants. +- Scott Hewitson suggests providing more specific instructions in the very first mission to join Akash Discord, directing participants to the Zealy working group channel for questions. +- Acknowledgment of the overwhelming nature of numerous channels in Akash Discord and the need for clear guidance. + +### Demonstration of Zealy Platform +- Robert explains the structure, highlighting the initial open mission for 100 XP points and the locked missions. +- Unpublished missions due to AkashEdu sign-up issues are discussed, with plans to republish them in the future. +- Clarifies that users can only do each mission once. +- Demonstrates how completing a mission earns XP and AKT. +- Showcases the leaderboard with user participation, cumulative XP points, and mission details. +- Emphasizes the connection requirement of Discord or Twitter for Zealy profile access. +- Robert proposes using the leaderboard to determine reward payouts after all missions are reviewed. +- Suggests waiting until all missions are reviewed before processing payouts to simplify the process. +- Acknowledges the challenge of not having access to analytics but considers exploring automations. +- Robert discusses the automation tab and potential future uses, such as creating specific channels for Zealy members on Discord. +- Demonstrates attempts to download member information into an Excel file for better visibility. +### Exploring Member Information +- Benjamin raises concerns about the efficiency of the proposed method and suggests exploring alternatives. +- Benjamin inquires about viewing individual member information, specifically AKT balances. +- Robert attempts to download member information into an Excel file, facing challenges. +- Benjamin queries about accessing analytics and member information efficiently. +- Robert explains limitations in accessing analytics due to being on the waiting list. +- Robert seeks feedback from Benjamin on ways to make the mission review process easier and more efficient. +- Encourages sharing thoughts on improvements to enhance the platform for mission reviewers. +### Review and reward calculation process +- Benjamin shares the view that the review process itself doesn't take long. +- Benjamin emphasizes the simplicity of opening the link, verifying validity, and confirming the completion of the mission. +- Benjamin identifies the challenge in tracking all submissions and determining the owed rewards. +- Raises concerns about the complexity of tracking user rewards, especially in a scenario where there are numerous submissions. +- Suggests a potential change to XP for easier tracking and mentions the challenge of determining appropriate payouts for each user. +- Benjamin suggests converting XP to AKT based on a linear scale, for example, 10 XP equals 1 AKT. +- Intends to display both XP and AKT numbers, allowing for easy conversion. +- Benjamin discusses the difficulty in manually tracking XP and suggests potential automated solutions. +- Robert proposes a tiered system where XP levels correspond to specific AKT payouts. +- Benjamin suggests giving XP based on the number of APIs, potentially automating the leaderboard. +- Discusses potential challenges, including the impact on the current leaderboard if missions change. +- Robert acknowledges the experimental nature of the pilot. +- Expresses a willingness to test, trial, and refine the process for improvement. +- Benjamin proposes keeping both XP and AKT numbers but changing the XP conversion to a linear scale. +- Addresses the challenge of altering XP without impacting the leaderboard, suggesting potential solutions. +- Considers the option of exporting the leaderboard data, adjusting AKT values, and potentially starting a new sprint with adjusted values. +- Benjamin requests the CSV file from the leaderboard to explore the possibility of automating the update process. +- Robert agrees and initiates the export of the CSV file +### Payment for Support +- Scott suggests that Robert Del Rey and Benjamin B can proceed to pay themselves the $250 allocated for support. +- Emphasizes that dollar denominated payments would avoid complications related to cryptocurrency price fluctuations. +- Acknowledgment from Benjamin B that a fraction of $250 (10% of the total) has been used for internal calculations. +- Robert Del Rey expresses the intention to run the numbers and make the payments after the call. +- Scott supports the idea of separating payments from incentives to avoid mixing funds. +- Benjamin suggests sticking to the initially created budget for both rewards and payouts based on the work done. +- Scott expresses complete trust in Robert Del Rey and Benjamin and emphasizes that they can decide the best way to handle payments. +- Tyler announces the addition of another meeting next week to continue the momentum. +- Tyler Acknowledges Robert Del Rey's and Benjamin B's contributions in leading the missions. +## Action Items +- Group agrees to continue exploring and refining the reward calculation process. +- Group to find potential solutions for leaderboard challenges +- Benjamin to explore the possibility of automating the leaderboard update process using the CSV file provided by Robert Del Rey. +- Robert to update the Akash Discord descriptions to guide participants to the Zealy working group channel for questions. +- Robert to share plans for promoting the Zealy pilot on Akash Telegram, the Zealy group, and social media. + + +# **Transcript** + +_This editable transcript was computer generated and might contain errors. People can also change the text after it was created._ + +Robert Del Rey: All right, guys. Hello and Happy Monday. I'm not counting the calls. But if I'm correct, this should be the third silly call, right? Yeah, the Federal. + +Scott Hewitson: Heard that I've been on. + +Robert Del Rey: Yeah, I mean to Me too. hopefully more people can join this cold over time. Luckily. We're recording the call for that one to see it later. much Tyler. Thank you guys for joining. So the agenda I have for today. it's gonna go over the questions. We have got in the shed about the Sealy campaign some posting on social media and groups sharing will update you how that went. And how will I continue with that and also some questions about Mission reviewing and abuse? So if you guys do you have any other item you want to add to the agenda? or place called + +Scott Hewitson: I think I'm Sounds good to me. + +Benjamin B: I have one thing because of the George not wanting to get part of the pilot anymore and… + +Robert Del Rey: go go. + +Benjamin B: we decided on having this as a conversation on what to use those funds were + +Robert Del Rey: You got it. Thanks. + +Scott Hewitson: + +Scott Hewitson: Yeah, I mean, I think if George isn't gonna be involved or does he doesn't have the bandwidth that's working on other things. I think we've originally talked about it like 2500 and then 250 to the three of you all and the rest go to rewards so just say Throw George's to Rewards. + +Robert Del Rey: Yeah for… + +Scott Hewitson: and then there's no issues. + +Robert Del Rey: that's a good fix. So more rewards for people. + +Scott Hewitson: Is that sound reasonable Benji? + +Benjamin B: Yeah, that was one of the things mean Robert agreed on. When writing about it that we would be fine with that. + +Scott Hewitson: Perfect. Okay. + +Robert Del Rey: Yeah, we're that call me but it's fine. We're gonna push forward. That's what we do here on a cash, especially in silly working group. So guys about the shots I was saying before I was so happy to see all the comments. I got a few Retweet some likes on social media, which was really nice on the silly discogroup. Sadly, I didn't get any feedback people react to the post by then receive any textual feedback. So what I will do is that on. Wednesday I will go ahead and do another round of sharing I'm gonna go ahead and share again of social media and share again in the city groups. And also I cash this Korean cash Telegram + +Robert Del Rey: Speaking of Akash this current telegram. Yeah, that is where most of the questions came from which is totally understandable. We share it for the group first insiders, then the broader community. And I believe the most common question is regarding the rewards it seems that people got the understanding that. They would do the missions and claim the rewards right away. So I mean if the first thing I did this morning was clarifying that you should just do the missions and the rewards are going to be paid out. + +Robert Del Rey: On December 21st, which is one week after we run The Silicon paint is gonna run from its running from last Friday was first. It's gonna run until Friday the 15th. So it's a two week pilot. So one week after that until the 21st or 22nd. We're gonna go ahead and start paying out those Rewards. + +Robert Del Rey: and I believe I answered that. So the question I have is how maybe we can go ahead and make sure this is clear for next iterations one idea. I have a monies that we can go ahead and compile the most asked questions or all the questions that they ask and maybe select the top five most common questions and add that somewhere where people can see that. But that's something I got right away off my mind. I don't know what you guys think about this so far. + +00:05:00 + +Robert Del Rey: Go ahead Scott. + +Scott Hewitson: Yes, so something I'll just say in general anytime like, members of overclock or whatever we've done stuff in the past where people are getting rewards. You're always gonna have people like whatever words remember words. So, it's a good thing like people are doing it again, but you don't feel the pressure to speed things up based off of external inputs. You got a game plan, I think we stick with it. And yeah, I mean anyone who's whining about it or whatever. Those aren't necessarily the people. We want to stick around anyway, so I'm not overly concerned. Just from a high level. + +Robert Del Rey: Thanks, man. + +Scott Hewitson: So I still think that thank you guys are doing a great job. + +Robert Del Rey: Thanks, I think you're right about that. + +Scott Hewitson: Yeah. + +Robert Del Rey: And yeah, we also said that dates. So we're gonna just stick to those imagine if we break that for any people in the group, then everybody's gonna feel entitled. So yeah,… + +Scott Hewitson: 100% + +Robert Del Rey: I agree with you 100% of Scott and anyone else. maybe when I don't have some questions for you Benjamin, but that's in a moment because I don't want you to expand on that but it's basically on how you feel about reviewing the missions. We're gonna go over that in a moment. I just believe that is what it's gonna take the most Of our call so that's why I'm going to leave those for the last part. + +Robert Del Rey: But yeah, what was other question as so but yeah, the mainly one was in regards to the rewards. So we made sure that it's a specific now before going over reviewing the missions. I want to show you something guys. Let me go ahead and share my screen. Right now sorry Tyler. I'm gonna take over you. But I hope you can understand. So here's the silly Bachelor We No One Love. Let me know if you can see it. Awesome. + +Scott Hewitson: Yep, I can see it. + +Robert Del Rey: So you can see the first mission is open for everybody doesn't pay out akt gives you 100 XP points. And the rest of the missions are locked until you do this one single Mission. So if I do this one single Mission people + +Robert Del Rey: will have access to do any of the missions here. the one from osmosis and the one for the cash EDU. I on published them. So they're not published. That's why they're grayed out. I didn't believe them but they are unpublished. Nobody can see them. So the reason why I did that is because Adam told me about the issues signing up with the cash in you. He's kind of working that I truly understand him. He has a lot in his plate so I don't judge him at all. + +Robert Del Rey: and yeah, I decided to unpublish this Mission they get to know greater Mission. This one didn't pay out any akt, but yeah, I didn't want to add work to what Adam is doing, people have to request access to this and maybe we're gonna have this one For another season I guess but yeah, as I was saying all the missions are locked onto you don't do this Mission. You cannot do these missions. I'm sure that already. One user can do the missions only once as you can see here, they can do the emissions only once so, let's say I do this Mission. I created my own as the L using cloudmose. I submitted when you review it. He accepted. And I got 100 XP and I got 10 akt. + +Robert Del Rey: Where can we see this information? If we go to the leaderboard on the left side of the screen. You can see all the people participate in missions. This is current but also got people from the past these two here if I'm not mistaken, but these guys participate in this guy is current these are kind of new users that we had so far kinda around 11 users. So let's say we're going to see how many missions Hitachi did. Or it's easier to pronounce against Pablo. He did request you can see that and he has cumulated 300 XP points. If I click on Pablo. We can see in more detail. We can see his Discord user. + +00:10:00 + +Robert Del Rey: So we can confirm his identity and we can also see his Twitter account. If you want to open up a silly profile, you have to connect either one of these two or the two accounts you're But there's no way to have access to this without connecting a Discord or paragraph. Sorry or Twitter account. below here, it's the missions they did. + +Robert Del Rey: As you can see the guys have done three missions so far. So this is my proposal and I'm gonna drop this in the chat. I want to hear your thoughts and specifically you been using your day one. There is taking the lead reviewing the missions and correcting and giving the points. How would you feel about reviewing the missions in a proven them? And then use the leaderboard. So that we can see how many rewards we have to pay out instead of Hitachi did one mission is instead of going a mission by Mission and having a sheet like login the rewards you got to pay out. + +Robert Del Rey: Since everything is together here. I would suggest that we could wait until all the missions are reviewed and then based on the leaderboard we can go ahead and pay it out the required. I just believe it's gonna be easier if we do it that way as you can see we're gonna also export this to an Excel file. But yeah, that are basically the options on reviewing the missions and paying out the rewards. So yeah, I'll leave it to you guys. how would you feel about using the leaderboard to pay out the Rewards or have you thought about any other way of reviewing and paying out these Rewards? + +Benjamin B: And not reviews. It's not needed and the analytics members and automations. I believe without more maybe. + +Robert Del Rey: Absolutely sadly Analytics is not available or a while I mean since + +Robert Del Rey: when we first started this it asked us to sign up for the waitlist, and I haven't got any emails about it. I don't know if people got access to it yet, but it's planning to launch monthly subscriptions. So people can see more information. But yeah analytic is not available some beta testers in the CD score group have access to it. But yeah, we don't just so guys, so it's gonna be a bit challenging knowing the analytics. I believe it's gonna be nice seeing them, but I will see what I can do about automations then + +Robert Del Rey: This one is really good. For example, let's say if we want to have a specific channel on this score and the only way to access that is be a silly role in your profile. For that we will need to connect a cache Discord to see we need admin rights to do that or an administrator or a cash Discord can go ahead and do that. Let me do a quick demo. I guess if I go here it says you need an information to what the silly but to the server. So yeah, let's add the permission whatever. + +Robert Del Rey: It's gonna ask me for the permissions. Can you guys see what I'm seeing now? + +Scott Hewitson: Yep. + +Robert Del Rey: Thank you. So, yeah, it's gonna ask you for permissions connect the board whatever but since I don't have access to a cash. Discord as an admin. I cannot add the silly button and that's why we don't have a specific channel that only silly people can see for now. I think it's not needed. Because we have the silly working group channel in Discord, but maybe that's something we can consider in the future when this is an official Community program, I guess but yeah, that's what you do in this automation tab. there is another way to access this you can go ahead and click on the three dots go on And from settings you go to Integrations. That's the same that is the automation step. + +00:15:00 + +Robert Del Rey: But yeah, then after that is just general settings so yeah. I hope that covers your question Ben you + +Benjamin B: Yeah, there's one more thing. What happens if you click members. I'm trying to see if there's a good way to see how much ATT each member should have the way you proposed seems really consuming for no apparent reason + +Robert Del Rey: German let's find a way. This is the member stop I can import members. download that into an Excel file. Yeah, I remember Sorry, You can download this into an Excel file. You will be able to see. This information. I guess this is the formula. Let's do a try now. I'm downloading. Let's see. + +Robert Del Rey: Okay, that did nothing. + +Benjamin B: Maybe don't show it in front of everyone. + +Robert Del Rey: No worries. + +Robert Del Rey: Yeah, let me close this. Yeah. Maybe I can explore these further. But when you click on upgrade plan, I told you with the analytics to join the waiting list again, I join a few months and I didn't got an email. I guess I would just go ahead and write up my email again. So to see maybe we have a better luck this time. But yeah, that's how it is and analytics and members the review ones. + +Benjamin B: I have yeah. + +Robert Del Rey: I believe you have access to see the review Once since you have already. review submissions and inbox here. This is more for the admin side. I don't know if you can see that bendy. Let me know if you cannot so I can add you. But yeah, I believe only admins can see that. + +Benjamin B: again + +Robert Del Rey: and this is for notifications when someone joins organizations someone joins the + +Robert Del Rey: the quest whatever. But yeah. You have another question about the platform. I'm more than happy to chat with anybody about it. But going back to the question I guess what other things could make your work easier in review emissions because I understand it can be very consuming. So I'm only years Let me know how this would be easier and better and stronger for you. + +Benjamin B: I don't think the review process takes that long. It's just open the link and see whether or not it's valid or you see the emotion you see if it's valid or not. When you already have the knowledge, it doesn't take that long. However, When tracking everything and knowing how much we owe to the users and how much to pay out. I think that's another thing so the one more the question I have now is that if we were to change it like XP, could we track how much to pay out the adults? because I think Let me see if we have. + +Benjamin B: What is about 1080p? and we give it to let's say an average of + +Benjamin B: things to make it different person. We would have to go through almost seven three. Users just seeing what they've done or not. + +Robert Del Rey: I get it something a range for example, if you get between 500 XP to 200 XP you will get 25kt. For example if you get from 1,080 to 2018, you will get 180. I just made up the numbers but is that something similar to what you have in mind? + +Benjamin B: what you could do is that you could give XP based of the number of apis who may be 10 XP per 180 or something and then payout together, but then you have the old XP and it's not certain whether or not the old XP the current leaderboard will be changed. Yes, because you changed missions. I think we have to look into this a bit more but the only other solution that I think makes sense is automating The leaderboard so if we were to export it put it in Excel, but I think that's a lot of effort for something that could be. Sold probably not much easier way. + +00:20:00 + +Robert Del Rey: Guided men absolutely. Yeah, Let's talk more about this. That's what grade level about this pilot. We're just testing out and any straight that we can go ahead and test trial error and then refine and do it better. and yeah, this is great. I'm learning so much after we launch this that is crazy. So just to recap I really forget your idea right now Let's say for example instead of having five 10 akt and 10 akt Maybe it could be only in based on the XP we can do a conversion. + +Robert Del Rey: Maybe 10 XP equals one akt and based on that XP that you accumulate right? You will get akt. it is that similar to + +Benjamin B: Yeah, This is almost correct. You could still have the akt number displayed to them. But because we can't see it. We have to understand how much we should give them. + +Robert Del Rey: Got it guide. + +Benjamin B: So I would say keep both but change the XP to be holy say it linear to the amount of akt. + +Robert Del Rey: No, the other question you had is if the leaderboard changes if we change. + +Robert Del Rey: Is on the mission? And we're gonna find out now life, but you guys say I do it? I will go ahead and… + +Benjamin B: Yes. + +Robert Del Rey: change this one. the axis Let's see. Chicha, he has 400 XP. + +Robert Del Rey: He did the first mission. He got a hundred XP out of that. Let's update that mission now. Let's see what happens. I'm excited. + +Robert Del Rey: Let's Play five XP. All right. + +Robert Del Rey: Just to change the number. Let's go to leaderboard again. And it didn't change Can you see here still has 400 XP? + +Scott Hewitson: Might refresh the app or something. I mean it changed somewhere might not reflect… + +Robert Del Rey: then + +Scott Hewitson: until you. + +Robert Del Rey: Yeah, let's do that. There's nothing a refresh can't fix. All right. Let's try again. + +Scott Hewitson: + +Robert Del Rey: I will close the tab altogether. It's a good sign so you can see how bad I am. I'm a close-up together and open up again. + +Robert Del Rey: Okay, I will share the screen again. I haven't seen anything yet. + +Robert Del Rey: I'm sharing now. Let me know if you guys can see it. + +Robert Del Rey: You guys see my screen. + +Benjamin B: Yeah, I'm guessing this does not work though. + +Robert Del Rey: Let's see. this is a little more. yeah. No, okay. It seems like it doesn't work out because you know why because this is Yeah,… + +Benjamin B: Already given to them. + +Robert Del Rey: besides it's for life. since they join our city. This is how much they have done since they join our city. we can do is that we can go ahead and create a Sprint. If you go here clear strength, I can set up the duration and that's your update the number. Let's try that. So we started is still on Friday first the XP was the same so I don't know. how can we go about this? But yeah. And date. Yes, it's gonna last two weeks. + +Robert Del Rey: So you can see we'll do current and Sprint now. No one is in the leaderboard yet. Because I just started the Sprint. so maybe One thing we could do is ask people to do that again, maybe and we start from zero because again, this is something I didn't consider. So it's this point. + +Benjamin B: I don't think we can make everyone redo everything. + +Robert Del Rey: It's for life. + +Benjamin B: I would say a better solution is. and just going through exporting the leaderboard down the trying to figure out the adapt. It's not impossible. But it's not preferable leader. + +00:25:00 + +Robert Del Rey: Yeah, I really think it's gonna come down to that at the end. But it's still the good thing is that we have the knowledge for So next time we can make sure that we start the Sprint before letting people know. Hey, you can start doing the missions. Does that sound fair? + +Scott Hewitson: Sounds good to me. I mean and… + +Benjamin B: Robert + +Scott Hewitson: it's a pilot, So we learning you said it Robert we're learning things. We're trying things, it's all about just improving on it. So I'm fine with all this. + +Robert Del Rey: Absolutely. Thanks, Scott. Go ahead Benny. + +Benjamin B: If you could send me the CSV file from the leaderboard, I could take a look if it's possible to automate it in a simple way. And then we could keep the XP the same. + +Robert Del Rey: Sure. + +Robert Del Rey: I'll go ahead and stop sharing the screen. And we export. + +Robert Del Rey: So it gives me two options to export they give me all time numbers and the numbers from the Sprint I use that so I'll go ahead and go with all time for you so you can see all the information. Okay? + +Benjamin B: Yeah, sounds good. + +Robert Del Rey: awesome, and yeah, that. I don't have any other agenda items. I basically cover most what I wanted to cover if there's anything else you guys want to cover now, this is the perfect time. + +Scott Hewitson: The only thing so on the very first mission to join a cautious Discord, if you have questions, maybe we could be more specific and join Akash and then the working group zealy channel for questions. because we have a ton of channels and Akash, and I know some people I've talked to people in the past it's just too much going on so + +Robert Del Rey: A bigger one. Thanks, That's super important because It's true. And I also saw many questions in the general chat. So yeah great cash escort Discord description to be more expensive. so people can go to silly working group to ask questions specifically. Thanks Scott. And let's do a quick commercial break, right? I see George in the audience. Welcome George and also see a new face Daniel. I don't know if it's a new face. Honestly. I don't know if you were in previous calls, but welcome both if you have anything to say just come to the stage. This is open. + +Robert Del Rey: In any case guys, so I got a few deliverables Benjamin. I will send you the CVS file. Like I said, I will update the discourse descriptions to make sure people can see that they can go to their cash CD working group Discord Channel. I also shared with you the plans on sharing the silly pilot on their cache these score in the cash Telegram and the silly group again and on social media again, I would share them one day not and yeah, hopefully we can get even more people to participate. + +Robert Del Rey: I also made some clarifications on the telegram chat. I said that we had a price full of 1,000 for incentives those of you that know know that this is not the correct amount. it's a little more than that, right, but I just wanted to say that number. + +Robert Del Rey: Just in case. I don't know. I just saw that we could use that later to our advantage hey, we run out of numbers, but we got five hundred dollars more in incentives. So yeah, I mean if we have to do that I'm not saying that we will do that. But you guys know what's the correct number we have for incentives the budget was initially to those. No total was 2500. So + +00:30:00 + +Robert Del Rey: 750 was for payment George you were not here when we were discussing about this. We honestly are not sure if you have enough bandwidth to continue with this project. So I guess that for the pilot me and Ben you're going to continue and maybe you can join us in other silicon paints. So having said that $500 will go for payments. So 2000 will be for incentives in their cash machines. If I didn't get that right, maybe Benji, you can give me the correct numbers. Please forgive me from if I have the numbers. But yeah, it's a rough estimate. + +Robert Del Rey: I just clear out that in the group that we have a price pool. So I guess that when we run out of money in the pool, I guess we will run out of prices for participants. So I guess the best way to go over that is just that letting people know that first serve until the last one is serve. Maybe you have any suggestions on how to go around this Scott scenes. You have go with boy getting stuff or maybe when you have an idea or anything else in this call. If you have a suggestion on how to go around the price cap that we have. + +Scott Hewitson: Benjamin did you have anything or? I can. + +Benjamin B: No, I don't have anything really on that topic,… + +Scott Hewitson: I can jump in okay. + +Benjamin B: but I can say no that I'm unmute that I sent the correct numbers in the shot. + +Scott Hewitson: I think just how I'm thinking about it, the payments for support to you to Robert and Benji was 250 USD. + +Scott Hewitson: You guys can I mean in my mind if you pay yourself out now, I mean, we're kind of along far enough where it's like right you're not just taking the money and running. I mean, I think it's fine. If you pay yourself out the dollar denominated and then we have an actual akt amount moving forward then you can track to that exactly. + +Benjamin B: What mean Robert did as soon as he sent the money was to create a fraction of 250 is 10% of the total? so this is the number we've been calculating internally. + +Robert Del Rey: No Thanks I will go ahead and after this call right now. I will just run the number make it to 50 and send out the payments because I believe we don't mix that with the incentives. So yeah Benjamin, I initially spoke about this. We actually didn't mind. if we didn't pay ourselves until the last day, but I believe that it's good if we don't have that money mix out in my opinion which Goes with your opinion and… + +Scott Hewitson: Yeah. I think it's difficult when we have a … + +Robert Del Rey: Scott, right? + +Scott Hewitson: a token that changes and it swings 20% one day down 20, it's craziness. So the only thing for sure is like when something's paid at spot price that day, it has that amount whether you decide to hold it or sell it or whatever that's on the person but I've found just from all the other things I've supported. It's just easier that way. But yeah, I mean honestly however you guys would like to do it. I don't have strong opinions. Either way. That's just I guess it's an opinion. It's not a directive. So, however, you guys think you can do it the best I got complete faith complete trust in you guys. + +Robert Del Rey: Appreciate it Go bendy. + +Benjamin B: Yeah, so if it is okay, I think that what we created with our budgets initially. I think that's the one we should go by and both the rewards and the payouts will be based in akt done. + +Benjamin B: We have a message in the shot, by the way. + +Robert Del Rey: Yes, Mr. Daniel. Let me go ahead and read this. + +Robert Del Rey: he's dasher. Okay, you dust yourself, man. No worries. + +00:35:00 + +Robert Del Rey: Let me read this now. + +Robert Del Rey: Okay, okay. Okay. let me keep this out for First of all, Thanks for joining and participating in the missions. Feel free to drop any other comment and feedback you have in the cash discount silly group And no you haven't missed the pilot that started. Last Friday first and it's gonna run onto December 15, which is also Friday. So it's basically You have those days to do the missions after those two weeks. + +Robert Del Rey: We're gonna start paying out the required for those who did the missions now, since this is a pilot. There are things that can change as we go that's why we're having these kind of calls so we can update ourselves and find better ways to do this and we're gonna do a change In how we calculate those rewards so yeah, we're still working on this you haven't missed anything It's a great time for you if you want to get involved. So I extend that invitation to you Daniel about a 18 News. we have made it eight of great recently or maybe nine. I don't remember but Tyler can give you more about a cash news, but you can also go to a cash Tweeter to a state up to a speed with a cash news in my opinion + +Robert Del Rey: But yeah, I don't know if I left anything behind but yeah, that should cover your comment. anything else guys? I guess we're running good on time, right? + +Robert Del Rey: Let's see. What else I will call. go ahead and sign up for the waiting list again. Let's see if we have better luck this time. That was another thing that we spoke about. Because it would be so great if we could see those Analytics. + +Robert Del Rey: And Besides that anything else I'm missing guys. I believe not. + +Tyler Wright: I'm gonna add another meeting for next week. So we could just continue on with the momentum that we've got going and it sounds like action items are clearly outlined Robert you do a great job of running these meetings so much appreciate you and Benjamin you and as Huey has mentioned having this pilot in you and… + +Robert Del Rey: + +Tyler Wright: Ben's hands. we have a lot of confidence. So excited to see next steps. + +Robert Del Rey: Thank you means a lot of you saying that Thank you so much, That's what we're here for and that's because of mean We hear you speaking. week after week leading. This missions doesn't matter who goes on vacation. You take the lead and continue with the meetings. And yeah, it's awesome and that we can also do that and that we can also contribute to a cash that way. So yeah, that's all for me. Maybe I can give you some minutes of your life back. I don't have anything else to add if you guys have anything else to feel free to drop your comment right here right now, or you can also go to a cash CD Discord especific channel for this. my name is Del Rey so you can have that in the recording and yeah, see you next time guys. + +Benjamin B: Thank you, everyone. + +Scott Hewitson: Thanks everybody. + +Tyler Wright: Thank you. + +Robert Del Rey: That again next Monday or in the other cash meeting, bye-bye. + +Meeting ended after 00:39:17 👋 + diff --git a/wg-zealy/meetings/005-2023-12-11.md b/wg-zealy/meetings/005-2023-12-11.md new file mode 100644 index 00000000..f2f0a47d --- /dev/null +++ b/wg-zealy/meetings/005-2023-12-11.md @@ -0,0 +1,315 @@ +# Akash Network - Zealy Working Group (WG) - Meeting #5 + +## Agenda +- Overview of the Zealy platform. +- Discussions of Zealy missions and the overall pilot phase +- Progress Updates + +## Meeting Details +- Date: Monday, December 11, 2023 +- Time: 6:00 AM PT (Pacific Time) +- [Recording](https://hp5novctzn3y56mrqix5wq3knexy4w24tk2ugahmstq2ofxzp57a.arweave.net/O_rXVFPLd475kYIv20NqaS-OW1yatUMA7JThpxb5f34) +- [Transcript](#transcript) + +## Participants +- Benjamin B +- George Pro +- Robert Del Rey +- Scott Hewitson +- Tyler Wright + +## Meeting Notes +##### Robert Del Rey: +- Robert Del Rey welcomed everyone to the fourth Zealy working group call, expressing enthusiasm for Monday meetings. +- Mentioned the conclusion of the pilot on Friday the 15th of December and upcoming reviews of missions and payouts. +- Tyler raised the question about considering participation levels for future initiatives, acknowledged by Robert and added to the agenda. +- Robert explained the change in the first mission to make it auto-claimable, eliminating the waiting time for manual review by Benji. +- Emphasized that this adjustment allows users to access other missions immediately, improving the overall user experience. +- Scott inquired about the auto-claimable mission, clarifying that it awards XP points rather than AKT. +- Robert confirmed and shared his screen to demonstrate the process of claiming XP points for the auto-claimable mission. +- Scott acknowledged the adjustment, appreciating the effort to reduce friction in the user experience. +- Robert discussed the need for special access to analytics on Zealy. +- Noticed a paid plan for analytics but observed it's not available to everyone. +- Signed up for the waiting list and attempted registration with another email. +- Robert shared information about Zealy collaboration request process. +- Explained filling out a form with details about Zealy participation and community involvement. +- Requested to be featured on Zealy pages for increased visibility of Akash Quest and Discord. +- Submitted the collaboration request last week but has not received a response from the Zealy team. +- Acknowledged the possibility of a delay due to a potential high volume of requests. +- Briefly touched on a quick collaboration update, mentioning signing up for the newsletter for more information from Zealy, with plans to keep the team posted once a response is received. + +### FAQs +- Robert Del Rey discussed the addition of FAQs to the Zealy documentation, covering common questions about Zealy. +- Explained that the FAQs now include queries about Zealy's purpose, mission review times, AKT prize payouts, and more. +- Mentioned that the FAQs are compiled in a document for easy access and can be update by anyone. +- Shared the [link](https://docs.google.com/document/d/1rG9-pxlV0K0gCQYTroePCwj_zT2STPsMO_XGKGIdJEU/edit#heading=h.ifkbhvrif0b1) to the FAQ document for the team's reference. + +### Reviewing Process +- Robert discussed comments received on the review process, addressing a recent Discord query about immediate mission checks. +- Explained the reason for not reviewing and approving missions immediately due to time constraints, especially since the team is not working on Zealy full-time. +- Highlighted the importance of avoiding mistakes during the review process and mentioned plans to discuss insights with Benjamin. + +### Post-Pilot Plans: +- Robert expressed focus on post-pilot plans, considering extending the pilot or introducing a pilot 2.0. +- Emphasized the need for clearer and more specific missions based on feedback received during the pilot. +- Mentioned the intention to conduct a poll in the Discord chat to gather more comments and feedback. +- Teased the idea of new types of missions and leveraging Discord integration for specific roles based on mission types. +- Acknowledged that detailed discussions on new mission types would be reserved for a later call. + +### Discussion on Extending the Pilot: +- Tyler Wright suggested the idea of extending the pilot or introducing a Pilot 2.0 due to the slower pace during the holiday season. +- Mentioned the possibility of allocating additional AKT to extend the program until January 5th. +- Acknowledged the need for further discussion on the idea and opened it up to the group. +- Robert Del Rey expressed interest in extending the pilot and asked about the remaining AKT and handling pending missions. +- Robert questioned the number of AKT remaining and how to manage resources for pending missions. +- Robert acknowledged the need to address concerns from community members taken the missions, about the potential waste of resources . +- Scott Hewitson inquired about the number of people ready for payout. + +#### Benjamin B's Response: +- Benjamin addressed the comment about considering it a waste of resources, noting its subjective nature based on individual goals, such as creating a personal website. +- Provided an estimate that around 50% of the budget was allocated to rewards, taking into account the potential distribution of large sums for regular missions. +- Acknowledged the need to review all missions for an accurate assessment of remaining AKT and mentioned the plan to run a script after receiving an updated CSV file from Robert. +- Scott indicated a willingness to add more AKT to the prizes as needed, emphasizing the importance of compensating the team adequately for extended efforts. +- Robert Del Rey thanked Scott for his input and deferred to Benjamin to continue the discussion. +- Benjamin agreed with Scott's perspective, stating that it makes sense to consider compensating the team for extended efforts, especially if there's a decision to push for a pilot version extension. +- Benjamin suggested reviewing all missions after the meeting, requesting an updated CSV file from Robert. + +### Considerations for a Pilot Extension: +- Benjamin expressed reservations about doubling everything without further analysis, suggesting that with a new pilot, they could apply new knowledge and potentially make adjustments based on their recent experience. +- Scott Hewitson proposed a hybrid approach, suggesting that after the meeting, if they decide to extend, they can announce it and run the script to pay out participants who completed existing missions around the 15th. +- Scott proposed the idea of extending the current pilot rather than stopping and restarting, emphasizing the continuity and potential benefits of using the existing momentum. +- Robert suggested extending the current pilot until December 29th, followed by the rewards payout from January 1st to January 5th. +- Tyler suggested a three-week extension, expressing satisfaction with the current progress and momentum. +- Robert agreed with the three-week extension and proposed announcing it on December 15th to provide users with early information. +- Benjamin B proposed revamping missions after the 15th, providing users with a new set of missions for the latter half of the extended pilot. +- Scott suggested running the script on the 15th to pay out users up to that point, providing clarity for those expecting completion on the original end date. +- Scott Proposed a semi-pivot with a script run on the 15th and a continuation with revamped missions for the extended period. +- Benjamin B supported the idea of announcing the extension as soon as it's confirmed, enabling users to adjust their expectations. +- Participants agreed with Scott's suggestion of a script run on the 15th and expressed openness to revamping missions for the latter part of the pilot. +- Decision to announce the extension of the Zealy pilot for three more weeks until January 5th. +- Deliverables for the next week's call include the announcement, payout for AKT rewards, and introduction of new missions for the pilot extension. + +### Other matters Discussed +- Robert Del Rey raised the question of scheduling the last Zealy call of the year. +- Tyler suggested having the last call next week, using the full hour to finalize decisions and prepare for the new year. +- Tyler mentioned that the following Monday would be New Year's Eve, proposing an extended discussion next week. +- Agreement among participants to schedule the last Zealy call of the year next week. + +#### Acknowledgment of Compensation: +- Scott addressed the compensation concern, suggesting a fair amount for the additional three weeks. +- Open discussion on determining an appropriate compensation for the extended period. +- Robert suggested discussing compensation details offline and expressed gratitude for the consideration. +- Scott agreed, and Robert Del Rey confirmed sending a message post the call to further discuss compensation. +- Participants noted the serendipity of the program's timing, aligning with the community's needs and market conditions. +- Highlighted the positive outcome resulting from collaborative efforts. +- Robert reflected on the philosophical lesson that things fall into place eventually. +- Encouraged open communication and expressed readiness for improvement. + +## Action Items +- Benjamin to review missions and calculate payouts post the pilot phase. +- Robert to initiate a poll in the Discord chat to gather feedback on mission clarity and potential improvements for the post-pilot phase. +- Robert to discuss and plan new mission types in future calls +- Group to schedule a follow-up meeting to discuss the extension of the pilot program +- Benjamin to review all missions and provide an updated AKT estimate for further discussion in the next meeting. +- Group to announce the extension of the Zealy pilot for three more weeks until January 5th. +- Group to pay out AKT rewards for existing missions and introduce new missions for the extended pilot. +- Offline discussion for compensation details between Robert Del Rey and Scott Hewitson. +- Robert to Schedule an announcement for the pilot extension on December 15th. + + +# **Transcript** + +_This editable transcript was computer generated and might contain errors. People can also change the text after it was created._ + +Robert Del Rey: All right everybody. And happy Monday. We are here in the fourth silly working group call. Really nice. It's great that we have this column Monday. It's the beginning of the week. We kind of feel like motivated. We rest on the weekend and during this call we can focus on what we did last week. And what is the plan for this week and going forward? It's crazy. How the time flies We had the pilot call where we set everything up and now this pilot is gonna end this Friday the 15th. + +Robert Del Rey: So four five days until the Pilot ends at least the missions and submissions period after that week Benjamin, I will go ahead and review the missions and calculate the akt prices that are gonna be given out paid out. So really excited times. We also learned a lot. So in my agenda, I got a few things but I gotta ask guys. Do you have any special topics you want to discuss so I can add it to the agenda? + +Scott Hewitson: The only thing I was gonna ask about is any metrics we have but I know you're on top of stuff. So you're probably already in your agenda. + +Robert Del Rey: Yes, I do have a list of the metrics we want to consider. So yeah. Hey better you go. + +Tyler Wright: Hey one item. I was thinking about over the weekend is based upon how much participation we've had in this initial pilot. I was wondering and this is this question for Huey, too. + +Robert Del Rey: I just added to the agenda. Thank you so much. So let's just start with the beginning the silly Quest board Mission updates. + +Robert Del Rey: As you may know the first mission was like a gatekeeper. If you didn't do that mission first, you couldn't access the other missions in a cash, silly. but something happened Benji brought to my attention that If there was a way that this Mission could verify themselves so people can just click get access and then they can do the other missions. And the point was that. we didn't want to make people wait until they could start doing missions. So the first mission was set up in a way that Benji had to review the missions. So that could be 10 hours 12 hours apart 24 hours apart. So when we accepted the missions, we noticed that + +Robert Del Rey: those members didn't do any more missions, so that is possibly because They just forgot about it and drop this so we made a change in the first mission to get access to the cash silly is out of claimable. Meaning that when I go ahead and get that tested talking. I just gotta visit the page. And the mission is gonna be claimed right away for you. So that's gonna happen automatically Benji doesn't have to review this now and that way if someone step across a cash, silly. They can try it out faster than it was before because now it's gonna be okay. Let me do the first mission. It was review right away, and I can have access now to the other missions. + +Robert Del Rey: And before it was let me do this Mission and now I have to wait until this guy review the missions so I can start doing the other missions. So I don't know if I'm making sense to you guys. But this was a small thing that added to the experience because now like I said, Benji was right be a few people got in now and I started doing the missions right away instead of waiting to start doing the missions. So that is a big update that we had in the quest board. I like it that can be configured to all the missions at the moment only. This one is how to claimable the other ones. We need to review them manually. So I guess Robert time nations are gonna evolve and we're gonna discover. What is gonna be the best + +00:05:00 + +Robert Del Rey: Reviewing process and the best submission type depending on the mission, right? + +Robert Del Rey: If you guys have any questions about the outer claimable Mission now, it's a good time before I go to the next update that we did. Go ahead. + +Scott Hewitson: So it's the auto claimable is it's obviously not like sending out akt. It's just the XP points. Was that correct? It's Okay. + +Robert Del Rey: Yes, you're right. Yeah, let me show my screen real quickly. Let me know when you guys can see it. + +Robert Del Rey: okay. You were never gonna see it because I had click on share. All right. So we have the city here. So yeah, the first one it's Auto climbable and it gives you 100 XP points. And since you completed the mission now, you would have access to the other missions. The other missions are They have to still be reviewed manually just but yeah you guessed right if I do this Mission now, I visit this page. And then I click on claim my reward you can see a few seconds. I'm gonna pass first. And then I can claim the reward. + +Robert Del Rey: It only gives me the XP point. I'm not gonna click on it. But yeah, it's gonna get through the XP point. No akd it's gonna be sent out almatically to anybody, right? + +Scott Hewitson: Sounds good. No, I think that's a good adjustment all made trying to reduce friction as much as possible. + +Robert Del Rey: Yeah, absolutely. It was a great spot on buying another thing with it the FAQ. See if I can opening up. I have a link here. Yes, I do. Okay. Can you guys see the FAQ? No, just the C, okay. I'm good sharing this stuff. I missed up sharing it's fine. Let me share the link for the document instead. But by the end of the document we added the most freaking questions now the FAQs. With questions, like what is silly? How long does the missions take to be reviewed? When are the akt prices Fade Out? + +Robert Del Rey: Do the emissions have to be done on testnet? So all those common questions. We got them now in the proposal document. I just put them there. So if anybody wants to update them, they can update them. I had them on my notion, but I just moved them to this document now, so everybody can see them. But this is just a compilation of the most common questions. We have received since we launched the pilot plus a few more if I need more hair, where do I go? You can ask in their cash CD Discord Channel inside their cache Discord, for example That's a quick one. Collaboration updates about Seeley. I said, I sign up for the newsletter so I can get more information of their plans and the automation stuff. + +Robert Del Rey: But I haven't got any answer yet. I will keep you guys posted as soon as I get an answer. That is what remember that if we want to access analytics it since we need a special plan, whatever. I noticed that they do have a paid plan, but it seems that it's not available for everybody. It's just for for a handful of people so I just sign up for the waiting list. I needed a few months back. I just did it again. I tried with another email also. So let's try our look this time. + +Robert Del Rey: They also have a collaboration request that you fill out a form and in the form you write things like hey, I just sign up for silly. I open up this community. I'm doing missions this way. I would like to be featured in your pages. So I sent that request also because that way we can get more eyes in the cash Quest sport. I haven't got any answer on that yet. But when I do that what that happened last week, so let's give them more time who know maybe they get a lot of requests. Who knows but as soon as I get something I will let you guys know. + +00:10:00 + +Robert Del Rey: yeah moving On the reviewing process we have had many comments on the review process. I need to chat with Benji so he can let me know how he feels about these. but yeah, we mostly get comments. for example the one we had on Discord early this morning. + +Robert Del Rey: That basically the question was why can't the missions be checked in mediately, and what I thought that I didn't send this message, right? I'm telling this to you guys and those who listen to the recording. But the reason why we don't like reviewing and I prove the missions right away, it's because we are not doing this full-time. And especially Benji he's working in his own proposal, and we want to have enough time so we can sit down review the missions and Grant the prices Wasting or without making mistakes on who will give the prices right? That's the reason why we started as a pilot based on your suggestion guys. and yeah, I guess at the moment. This is a learning. + +Robert Del Rey: I guess what I wanted to say was our plans for the upcoming Pilots instead of the reviewing process. I need to chat with Benji so he can let me know more insights about it. But what I'm more focused now is that What it's gonna happen after the pilot and I guess This is a great time to talk about extending the pilot or the pilot be 2.0. Like you say some things I wrote down after the pilots is that we have to make sure missions are even clearer + +Robert Del Rey: and a specific error, right more specific. we review the missions we did the missions, We thought we had them right but when the missions were out in the field, we start getting those good comments on how to make the missions more clear. So I'm paying attention to those comments and fixing some of the missions accordingly, but one of the things we have to look out for upcoming Pilots, it's making the missions as clear as possible. That's gonna help us in reviewing missions. And that's helps the builders because they're gonna have a clear thing to do instead of guessing what to do. so yeah, that's something for the upcoming pilot. I'm thinking of doing a poll also. + +Robert Del Rey: And drop it in the chat so we can gather more comments and more feedback that's gonna happen when we decide to finish the pilot. I guess. It's mandatory to do that. And new type of missions but I'm gonna keep this for another call because this is gonna be long but basically I'm thinking that we can have more missions and we can take advantage of the Discord integration to Grant specific roles to a specific people that do a specific kinds of missions. So it's something I have on my mind and yeah, I guess that we have to discuss this. + +Robert Del Rey: In a later time because it's too broad right now for this call. I would like to focus on the reviewing how we're gonna review those missions and I'm happy that when you joined this call, no worries, It's fine. I guess you do jumping in a great time. But the long story short. I was just updating Tyler and Scott on what we've done with the missions. I told them that The first mission is autoclaimable. You don't have to review them now and people can start do the missions right away. I talk about the frequently asked questions. I had those to the + +Robert Del Rey: to the Google Document so you can see them by the end of the document. These are the most asked questions that I've seen and I have them all in one single place. So you can see that by the end of the Seeley document Okay, the silly Google Document, I guess that's better. + +00:15:00 + +Robert Del Rey: And the last one that we were talking about is that what we happen after the pilot and Tyler gave us an idea And is that since the holidays are kind of slow on the developer side. Also, the working group calls are slower on during this time of the year Tyler suggests that we should either extend the pilot or do a pilot 2.0 and that way we can give more people more time to complete the missions. I guess. That was the main idea right Tyler. You can correct me if I got it wrong, but that was basically + +Tyler Wright: wondering if we could figure out a way to extend the program maybe I don't know if there's any more akt we could theoretically put behind the program to get us another two weeks, but I just want to float the idea. Maybe we can discuss this more next week around having their program at least in this pilot phase continue to January. + +Tyler Wright: Fifth, maybe. Yeah that Friday. But yeah, just want to throw that out there to the group. + +Robert Del Rey: Thanks, I do like the IM before you go Scott. Let me write the dates down. I have two questions, maybe a Scott. You're gonna talk about that. and the question I guess gonna be for Benji. How many akd we have left. To know if we could continue with the pilot. I'm down to extending the pilot of course and your points Tyler are super spot-on like you say, so yeah, I'm down to extending this and using this downtime to have more people even get more chances to get involved with akt with a cash. So the question I have is how many Kitty we have left and How can we go about the missions? + +Robert Del Rey: That are pending for review because there are some main missions that are still running some deployments that are still running. and that can take some resources that is related to the comment. We had this morning someone put this is a waste of resources or something like that. I kind of understand where he coming from even if the wording wasn't the best. So I guess those will be my two questions in case we want to extend this program how many we have left and how can we go around the missions we have to review now. Is Scott you had the hands up? Let me… + +Scott Hewitson: I'll defer to Benji. + +Robert Del Rey: if you don't have any other question. + +Scott Hewitson: My question was basically do we have left? How many people do we have ready to be paid out or whatever. But yeah. + +Robert Del Rey: So Benjamin it's your turn man. Thanks for jumping in. + +Benjamin B: I want to start by I believe that referring to it as a ways to resources is just dependent of what they want to do if they actually want to create a website of Their Own. They would not treat it as a ways to resources. For the budget my loss. Estimate was that we had around 50% to the rewards And this was a high number at the time because I All as if they were going to give out the largest some of the regular missions, so I believe this was to make it cheaper that I counted. the unreviewed missions, however To know for sure how much AKC we have left. We have to review all the missions. And then we need an updated CSV file so I can run the script again. + +Benjamin B: So I would say that. after this meeting, I could go through all of the missions while some of the missions should Like the rough idea start we want may not missions to go until the Pilot is over, but if we need to count everything. I think it makes sense to just review them at once then I request the CSV file from Robert. I run the script that I created and I can give the current estimate so we can talk around this for now. how much akt do you think is needed for a pilot version to? + +00:20:00 + +Scott Hewitson: so I guess my thought is if we still have akt left over from the prize pool perspective, then it's really just making sure you guys are compensated for your time. So I know you're putting a lot of effort into this, I don't know if you guys think we need to add more akt to the prizes. I feel like we can kind of do that. As it comes up, but if we're gonna push the effort longer than I definitely want to make sure you guys are compensated for your time and effort that you're putting into it. + +Robert Del Rey: Thank you, go ahead Benji. + +Benjamin B: Here to what? You said Scott's I think that it makes sense if you guys want to push a pilot version, too. I'm not quite sure if we should just double everything I think that's kind of done without looking into it more. But basically with a new pilot, that's essentially what we're going to do. We have some new knowledge so that we can apply that. we may have some fun over but besides that I think that It's up to you how large you want to create it? We have some stats now available as soon as we have reviewed and so + +Scott Hewitson: instead of just Stopping it and then restarting the next one. I mean would it make sense to just extend this one? + +Robert Del Rey: Yeah, I believe you would make more sense if we just go. Hey guys. We got massive support. + +Scott Hewitson: Yet four weeks. + +Robert Del Rey: Can you hear me guys? Okay. Okay. + +Scott Hewitson: Yep. + +Robert Del Rey: I just gotta like a warning. Saying that I sound low anyway, so what I was saying, yeah, I guess it makes more sense. if we extend the pilot instead of passing delivering rewards and then starting again, especially during this time, which is the holiday time so to make it frictionless as possible. I think we could extend the pilot until December 29th, which is roughly two more weeks. Then we can pay out the rewards the following weeks, which is going to be from January 1st until January 5th, which is Friday the 5th. + +Robert Del Rey: About this Friday, which is the 15th. I guess it's a great day to make the announcement. We could announce. I mean since that the pilot it's ending of on these 15th. I guess the 15 is gonna be the best day to let everybody know. It's gonna be extended for two to three more weeks. I don't mind can we do three weeks Tyler says if we can do three weeks until January 5th. + +Robert Del Rey: I don't mind. I like how things are going. Like you say, I believe there is momentum going on and like you say Benji. We also learned a few more tricks about silly and what other things we could do. So if you don't mind Benji, if you don't mind Scott, I'm happy to extend this three more weeks until January 5th, and then we deliver the rewards by I don't know mid January any of the day that we can discuss about. Go ahead Benji. + +Benjamin B: I think it would be better if we just announced it as soon as we know for sure because that means that the users are not ready to no, it's complete now. We want a rewards but basically the sooner you can give out these use the sooner people will know and can make adjustments accordingly. And then I also want to say that I believe that. Maybe off to the 15th. We could revamp the missions completely. So the first half of the pilot we had some missions. And then we disabled those so people can't complete them at least some of them. And then we have the new ones instead that people could. not create but complete + +Robert Del Rey: Or someone. Thank you so much. Hugo is good + +00:25:00 + +Scott Hewitson: Would it be too much effort to so after this call we say all right, we're gonna extend we can do the announcement whatever but then on the 15th when it was originally supposed to end run the script pay out anybody who up to that point and then we know what we for sure have left over and we can use the revamped Mission. So it's an extension with a semi pivot in the middle of it. But then the people who came in and they're expecting it to be done on the 15th and expecting get paid soon after we're still keeping them happy too. + +Robert Del Rey: I like that. we can do that and basically do A bill cut and pay whoever is due. We pay them those rewards but they can continue to do the new missions. when you say about revamping the missions,… + +Scott Hewitson: Yeah. What do you that Benji? + +Robert Del Rey: it's great. It's great. + +Benjamin B: Before what was that final thing Scott? I didn't interior. + +Scott Hewitson: I was what do you think of that? So essentially, after this call, if we decide we're gonna extend we let people know we're extending but then anybody who's done missions on the existing missions we can run the script and get people paid out shortly after the 15th and then we can kind of pivot tweak or whatever add the New Missions and let it keep going but then we also know how much akt is left over and so it's kind of a mix between a V2 and just an extension, but then s also people are getting paid out on time when they're kind of expecting to + +Benjamin B: I think that's a great idea. I could definitely modify The script so that I can get a kitty numbers as well for Robert. + +Benjamin B: and then Robert can do the payouts. + +Robert Del Rey: I will send you the file right away also. so I had + +Benjamin B: Yeah, but we will need the updated one as well later. So. After I've done the reviews today, I will do all on all pending reviews. And after this we can run the numbers again. + +Robert Del Rey: German I don't know how you are on time, but I think that if we can get that done between tomorrow Tuesday and Wednesday, is it still gonna be fine? Because I don't know how your agenda looks like today. So don't feel rushed to complete that today. I don't know if you're Scott and Tyler agree, but I guess that reviewing and determine. The akt rewards can be done between tomorrow and Wednesday and we still have enough time to make the announcement and to pay out the rewards what you guys say. + +Scott Hewitson: I think that's fine. + +Robert Del Rey: Yeah. + +Benjamin B: Their worst case scenario. It's still the 21st where the payouts are due. So. + +Robert Del Rey: he so yeah, I will go ahead and send you that file right away. As soon as we get those numbers ready. We're gonna make the announcement that we're extending the silly pilot for three more weeks until January 5th. Pay whoever is due for akt rewards and a new missions for the pilot extension. So I guess those are gonna be the deliverables for next week call. + +Robert Del Rey: Since we're extending, I guess that's another question. I know you guys gonna go on holiday help me too when I go on holiday. So when should we have the last silly call of the year? + +Tyler Wright: I think we have one scheduled for next week. Hopefully we'll make all the decisions this week. We can finalize anything next week and then we can just work async… + +Robert Del Rey: e + +Tyler Wright: until we might have a full agenda next week in terms of things. We need to cover but Beyond that I think the following Monday after that is New Year. + +Robert Del Rey: New Year's Eve Wright + +Tyler Wright: Yeah. Yeah. So my boat would be next week and we just take the whole hour and we just make sure we have everything we need heading into the new year because it's like working there. + +Robert Del Rey: I agree with that. If you guys agree do some thumbs But where I agree? Hey, George. Thanks for coming So yeah guys besides that any other topics you guys want to go over. + +00:30:00 + +Scott Hewitson: So just want to say so that you guys are adequately compensated. I think it was 250 a piece for the pilot. So I guess we're just trying to figure out a way to come up with a good number that compensates you guys for extra three weeks. So I don't know how long the original Total start to finish would have been I mean if you guys have any ideas on that. I'm all for making, people should be compensated for the time and effort that they put into things but, we don't need to go too crazy with it. + +Robert Del Rey: Absolutely, If you don't mind, I can go ahead and send your message offline. And we can take him from there. Yeah. Yeah,… + +Scott Hewitson: Perfect. + +Robert Del Rey: this is great Thank you guys for your time. I also noted that down to make sure I don't forget about the compensation for the extending time. and yeah, I guess I'm not forgetting anything for now really good call if I can say a little something is that Yeah, it's crazy how things been evolving since we seriously wanted to do this baby. I got to thank you man for pushing me a little in going forward with this. I honestly was kind of like + +Robert Del Rey: Gave up, I guess because the first time we didn't have an old support so I didn't want to continue with that. But then I saw how you guys wanted to do it and that inspire me again, and it's crazy how things have people since we again started with this program. It's just a pilot, but we learned so much in these two weeks that I can wait to see how this can complement a cash community and how this is going to look like in the next. I don't know three six months, right? It's exciting. Just wanted to share that with you. + +Robert Del Rey: we + +Benjamin B: Yeah, thank you for all the kind words Robert. I just want to say that the community program like this is something that I've wanted for a long time for Coach. I didn't even know that Siri was a thing before I talked to Rodrigo. and after that I was thinking in my head this channel has been dead for one or two or three months. How can this be fixed and I help in any way. Can I get + +Robert Del Rey: Yeah, it seems like the planets align. this was the time to do this not like the middle of last year in the bottom of the Burr market, right? + +Scott Hewitson: It all works out in the end, right? + +Robert Del Rey: Yeah, yeah. At the end everything falls into place. It It's very nice. guys, I guess the lesson and that for today the philosophy lesson and but thank you all for joining. Thank you for your time. I wish you a great week. It's just getting started. It's just Monday. I'm pretty sure we're gonna chat during the week. So let's do that. And yeah, if there's anything we can do we can improve if you want to share it publicly. There is That cash CD Discord Channel. Yes, but if it's something more private, you can also send me at the end and I'm more than happy to chat with you for anything doesn't have to be silly necessarily. + +Robert Del Rey: But yeah, let's move forward if you have any other comments now it's the right time. If not I say goodbye to you and see you on the flip side, right? + +Scott Hewitson: Already have a good one everybody. + +Tyler Wright: Thank you. + +Benjamin B: Thank… + +Robert Del Rey: Thank you guys. + +Benjamin B: everyone. Bye. + +Meeting ended after 00:35:04 👋 + diff --git a/wg-zealy/meetings/006-2023-12-18.md b/wg-zealy/meetings/006-2023-12-18.md new file mode 100644 index 00000000..faf7ae73 --- /dev/null +++ b/wg-zealy/meetings/006-2023-12-18.md @@ -0,0 +1,319 @@ +# Akash Network - Zealy Working Group (WG) - Meeting #6 + +## Agenda +- Overview of the Zealy platform. +- Discussions of Zealy missions and the overall pilot phase +- Progress Updates + +## Meeting Details +- Date: Monday, December 18, 2023 +- Time: 6:00 AM PT (Pacific Time) +- [Recording](https://efn65ve3e5sebv7bhpgilvvzv23zx3ln6goskfwwrhj5rsmbludq.arweave.net/IVvu1JsnZEDX4TvMhda5rreb7W3xnSUW1onT2MmBXQc) +- [Transcript](#transcript) + +## Participants +- Benjamin B +- George Pro +- Robert Del Rey +- Scott Hewitson +- Tyler Wright + +## Meeting Notes +### Progress Updates: +##### Robert Del Rey: +- Acknowledgment and gratitude to Benjamin for creating a script to determine winners. +- Benjamin's script: Analyzing participant data - number of participants, missions, XP points, and AKT rewards. +- Mentions having an Excel file with participant details. +- Discussion on publishing the document, addressing privacy concerns, and missing addresses in the published link. +- 20 participants earned AKT prizes in the two-week pilot period. +- Mention of participants who won 45 AKT each; average winners received around 20 to 25 AKT. +- Overview of the distribution of AKT rewards, with the highest earner receiving 45 AKT and the lowest earner receiving 10 AKT. +- Discussed the review process for missions and ensuring deserving participants receive rewards. + +#### Benjamin B +- Reviewing missions was straightforward for Benjamin, leveraging his knowledge to assess deployments. +- Criteria for approval included checking for an active deployment through provided links and correct screenshots. +- Identified challenges in the provider mission where unclear specifications led to difficulties in evaluating submissions. +- Some users faced issues with outdated software installations or improper provider setups, requiring clarification on expectations. +Feedback for Extension: +- Proposed having more advanced goals in the pilot extension rather than repeating the same missions. +- Discussed the need for clearer instructions for missions, especially those related to providers. +- Encouraged a variety of missions to enhance the learning and experimentation experience for participants. +### Winner Reward Claim Process +- Robert shared that he received 19 private message requests related to the winners of the first phase of the Zealy pilot. +- Proposed two ways to handle winners claiming rewards: manually reviewing DMs or creating a new mission for winners to submit their addresses. +- Benjamin suggested incorporating address submission in the first mission to avoid complications later. +- Robert agreed with Benjamin's suggestion and highlighted the simplicity of modifying the existing mission for address submission. +- The group agreed on the approach of integrating address submission in the initial mission. + +### New Missions Discussion +- Robert Del Rey emphasizes the need to raise the bar and introduce more challenging missions for participants. +- Benjamin proposes continuing existing missions with modifications and introduces new, more specialized ones to engage active community members. +- Benjamin's First Mission Idea: Participants create and deploy a project from scratch, moving beyond using existing deployment templates. +- Benjamin's Second Mission Idea: Create a new validator, aiming for a top 100 position or at least being active on the GitHub discussions page. Acknowledges the need for further refinement. +- Tyler Wright supports the idea of encouraging validator participation but suggests refining the timing and details of the second mission. +- Mission 3: Detailed mission on becoming a provider, including specs, GPU, and uptime requirements. +- Mission 4: Rewarding users for active participation in GitHub discussions, encouraging research posts and engagement. +- Mission 5: Creating well-edited short videos demonstrating how to deploy specific topics (e.g., React apps, Python projects) to Akash. +- Tyler suggests an "Integrations Mission" as a more open-ended challenge. Participants could figure out an integration into a storage solution, with rewards ranging from $300 to 500 AKT. It would essentially be a small hackathon. +- Tyler raises a concern about incentivizing comments on GitHub discussions, suggesting it may lead to insincere or unnecessary contributions. +- Tyler emphasizes the importance of encouraging providers to consider features like IP lease and persistent storage. + +### Ideas for "Integration Mission": +- Tyler Wright supports the idea and adds to it by suggesting future missions that encourage building integrations with other projects like Filecoin, storage, and other decentralized infrastructure projects. +- Tyler envisions creating missions that simplify workflows and provide references for integrating Akash with various storage solutions, contributing to a more streamlined and user-friendly experience. +- Robert Del Rey confirms Tyler's suggestion, summarizing it as creating missions that encourage building storage solutions on Akash for projects like Filecoin, with specific rewards tied to the integration. + +#### Closing Comments +#### Robert Del Rey: +- Affirms the plan to extend the pilot until January 5th. +- Highlights the urgency to finalize new missions, rewards, and communicate the extension to the community. +- Thanks the team for their contributions and participation. +- Encourages members to reach out for questions or discussions on Discord or Telegram. +## Action Items +- Group to explore the possibility of an "Integrations mission", defining criteria and potential rewards. +- Benjamin to refine and finalize the proposed mission concepts +- Robert to focus on shaping and refining the proposed missions into actionable tasks for implementation. +- Robert to explore the possibility of attaching rewards to successful friend invites, considering feasibility and tracking challenges. +- Group plan to run the extended pilot until January 5th. + +# **Transcript** + +_This editable transcript was computer generated and might contain errors. People can also change the text after it was created._ + +Robert Del Rey: Alright guys GM and welcome to the last silly Community call working group of the year. My name is Del Rey. So happy to have join today guys And also we are recording in case people can't join right now. So I was saying before studying they call. Yeah, it seems that people was busy doing the wicked asking questions about the prices. so I guess what we're gonna discuss on the agenda today is the selection or determining the winners for the akt prices. I want to go over that and also here you guys thoughts about Gathering the winners addresses. So basically those two are the main topics. I have a mind. + +Robert Del Rey: and yeah, then we can talk about extending the pilot to which is a whole other story. about Gathering the winners and the addresses thanks to Benji bendy created a script. I just needed to send him a file with all the participants on a cash, silly. and after he run this the script we were able to determine how many people participated? How many missions they did how many XP points they earn and more most importantly how many akt rewards we should send them which is super awesome tool. Thank you so much bendy. You really were the MVP just because of that tool I can tell you that. So let me open up the document. + +Robert Del Rey: I have it in an Excel file in my computer. I don't know. That's another question. Maybe how can we go about publishing this? I believe I publish. One document one link already, but this one doesn't have the addresses people use to sign up and On the document I sent you have a hash. for the user you have the XP points. You have their Discord username that Twitter username and the username they have four ceiling. So the only thing that is not showing up in the link I sent on Friday. It's gonna be the addresses that people used to First login or just add any random address for City because Celio also asking for address + +Robert Del Rey: So yeah, I believe that was a good privacy measure. But yeah in total, There are 20 people that earn akt prices which I believe was super nice big bigger Plus for that. Is gracing it over two weeks we had that amount of participants And also these 20 winners are after being you review the missions because if I understand right there were people that participated but the missions were in good enough to earn the points. At the end we had more people signed up to see than more people that got the rewards and that makes sense. I just believe that in just two weeks. This is a great number to have any people. + +Robert Del Rey: There two that won around 45 akt each and were two people. And after that if you take an average. + +Robert Del Rey: On average everybody want around 20 to 25 AC for the 20 participants. If you take the average now the highest earners 145 and the lowest earners are one just 10 akt which I believe it's also good. I don't know but if you want to go over this and maybe tell me your experience about running the tool getting the winners. + +Robert Del Rey: And yeah, overall, how do you feel about the prices we did? And the missions to earn those prices and maybe you can add some insights about reviewing those missions. Yeah. + +Benjamin B: Yeah, So let me start with The script I created basically just goes through the leaderboard for every user. And they click the linked basically and I'm explaining the money process. So if you go to leaderboard page. You will see all the users there. If you click on user profile there you will see the missions completed. in the script, I don't have any information of the attempted measures only the ones that were reviewed and that passed. so after doing this for each and every user with the script It compiles it to a total number. And to help Robert. I also created it so that + +00:05:00 + +Benjamin B: it showed the individual equity and for the missions, I think that some of the missions were really easy, but + +Benjamin B: We got kind of what we wanted. We wanted to get users to experiment with and we did exactly that so people who never used a coach before were able to create deployments and while they didn't create something of their own they got to Try out the network and experiment. I think that for the extension we should try to have some more goals than just make them experiment. I don't think we should do the same thing. + +Benjamin B: For every part of the pilot, I think we can have some more advanced ones. We could have more rewards etc for the individual Rewards. + +Benjamin B: besides this I think it was only the reviewing part The reviewing of each mission was easy for me because I knew how to look for everything so for them deployments I had to open one link first and then in that link, usually there was a link that led to an active deployment. and if that active deployment was Correct. I let them pass for the screenshots. That was easy. Also, I saw some people installing very old software like the Akash CLI or whatever to say instead of provide your services. So those have to be denied but I still explained what he did wrong and what it had to do. to pass + +Benjamin B: and the only one that was kind of hard was the provided one because we did not really specify. What we wanted the deliveries to be like so some providers quit instantly. and I think all providers that actually set up their provider for even a few minutes were collected by two such as the provider Explorer there, but then I saw some people They went through the freight to wrap installation, but unfortunately, I couldn't let them pass because what they wrote was the screenshot that they showed. Did not show anything detailing about the provider. So it was like + +Benjamin B: the page where they set up the DNS and they did it for the main they didn't even own so. I couldn't really help them. + +Robert Del Rey: That's okay, Thanks for sharing. It wasn't quite experience. I was sending a message this morning and something I was thinking about is. all the + +Robert Del Rey: Learn using ceiling after we kind of started running the pilot and I'm pretty sure that over time we're gonna keep on improving the process and how clear are the missions with the instructions. Because I remember the questions on Discord. I Should this mission go on testnet to distribution go on Main should this Mission stays open for three weeks can I close it right away, right so though those little details I guess it's good that now we have them and we can use those three details to make the missions better and more clear for the future. Thank you so much Benjamin for that. I have nineteen private message request on this score + +00:10:00 + +Robert Del Rey: and the reason why is that I'm guessing is because on Friday I sent the message that we have the winners for the first phase of the city pilot. and to claim the reward they have to send me at the end the winners have to send me a DM. I got 19 requests. So I'm going to filter now wish out of those are a scam request which are legit. After I'm done with those I will go ahead and review the winners list again and see who has sent me any message yet and try to tag them in the public chat in the seal in public hey, thanks for why you haven't sent me a message Send me your message so you can claim your Rewards. + +Robert Del Rey: So yeah, that's one way to do it. But there is another way I'm thinking and is That We could create a mission. It can be called. + +Robert Del Rey: a cash Pilot One winners submit your address and we can create the mission in a way that people can click and submit an address and then We can review those submissions and pay out the rewards space on that. Now you might be asking how can we avoid? + +Robert Del Rey: Not how can we make sure that only the winners to meet their addresses? That's a great question. I guess we can do a condition. Making that the only people that can come complete the missions are the ones that have X amount of points or have done this amount of missions. That way we can make sure that the only people that can do this missions are the one that actually won the + +Robert Del Rey: the equity rewards go ahead and you + +Benjamin B: I don't think there's any point in limiting which people can turn in their akt address if it's not on Sealy because we know which users and one we just don't know their address yet. I think that for next time if it's possible. We should have a mission it's the first mission that you have to do. And they have to create an ATT address and write down that address in that mission, but then once that's done, it's all to complete so they can continue. And if they mess up without it's their own fault, and of course we can try to help but then we should have their address. + +Robert Del Rey: Dude, that's so a smart man. I love it. Thank you so much. I just wrote it down. So if I got it, right basically would be same that the first mission that we have get access to a silly Community. We can add another mission or another field asking them to submit their address beforehand so that way we have their address right away, right or is something we get into that, right? + +Benjamin B: Yeah, I don't think we need to create another one. We could just modify the existing one, but either way works. + +Robert Del Rey: Yeah, I like that one better. Thank you so much. It's simpler and like you say it wouldn't make point to have them I mean to do the condition and try to filter the winners from a scammers because we already have the winners. So it's gonna be a question of matching who is writing and The user is writing us to us. So yeah, Okay, so I guess we can do that. All right, guys, do you have any questions or comments so far before I move on to the next topic I have online. + +Scott Hewitson: No, sounds good to me. + +Robert Del Rey: highest court assignment, thanks for jumping + +Scott Hewitson: All right. Yeah. I was a little late. My daughter was a little unruly this morning, so I had to deal with that, but I'm here. + +Robert Del Rey: New Good Men. Thanks for young Penny. I don't know if I heard correctly, but are you sick. Also, I'm having some weather sick. I don't know. + +00:15:00 + +Scott Hewitson: I'm sick, every other week just because of the stuff that my daughter brings home. But now I'm okay. I'm on the mend. + +Robert Del Rey: Got him, and thank you. All right. + +Robert Del Rey: Okay, so up next. bangi And the rest of course. I want to expand on what other missions can we bring to the table? when you were saying in the beginning that the missions were great because there were simple enough to make people try to cash even people that haven't done a cash. Ever they did it for the first time and were able to do the missions and earn some Rewards. So now I guess the question is how can we level up that? How can we raise the bar? How can we give them people another challenge they feel challenge enough to do it, but don't feel like a skirt to give it a shot, right? + +Robert Del Rey: So, yeah, I guess I'm gonna open the station now what other kind of missions could we bring to the table to keep the ball rolling I guess. + +Robert Del Rey: I like to brainstorm but for now because since we're extending the pilot, I honestly don't have any idea. I try on Saturday coming up with ideas for New Missions for extending the pilot, but I couldn't come with new challenges I guess we can do the same similar missions that we had but I like to bring different missions. But when you have his hand up, let's see what he can say about that. Go ahead and + +Benjamin B: So first of all, I think that we should continue with the existing once we could modify them a little bit. and use the previous budget for that if we're allowed for the extension. I also think that we should have New Missions. I want this to be more specialized. I want to be able to get the community members that are really active Or I really engaged so. The first mission that I was thinking of I would write all of this in the shot later. includes rating in a culture up From scratch so you have a project on your PC? You created documents. Upload it create L unemployed to my coach. Right now we have only made them deployed templates. + +Benjamin B: then for the second mission, I'm thinking that this is a really hard Mission by the way, but + +Benjamin B: but some validators are not really active. So when you're wondering if it's possible to Try to create a mission that Create a new validator and make the top 100 sets. or at least create a new validator and be active on the GitHub discussions page. + +Benjamin B: This one still needs more refining because a lot of Tyler go ahead. + +Tyler Wright: I'd like this idea. I think something that Scott and I are trying to do is make sure that all the validators are participating more. So I think a lot of we're meeting with a number of folks and just connecting with folks because that's relationships that previously we weren't owning and managing. So as we move into New Year, I think that's going to happen. I don't and I think that might be a mission that might be too soon for right now. I also think that the part about getting them into active sets. It's really just down to Dallas and sense. And so I'm not sure that's a mission. I really like the first couple of missions, but only thing I was going to add it. I was wondering if there's a possibility to do an Integrations mission that might be a little more open-ended and be something like worth $300 to 500 akt and it's just + +Tyler Wright: basically I can small hackathon, figure out an integration into a storage solution, that other users can use or something like that. That's other people can benefit from and maybe somebody from the community might be having interest in doing over the holiday. + +00:20:00 + +Benjamin B: They can try to continue on this topic and… + +Robert Del Rey: awesome + +Benjamin B: right now and if you're aware of what the Sierra Network is. Or if you're not it's a storage Network where you can From different so you rent from maybe 30 or more hosts. And if your data gets lost you can replicate it and always have this a great redundancy. Anyways right now they have a hackathon in their Discord Channel. Let me Called the render the hacker phone and basically what this is about is. renting storage from the network and I think that integration with a car share with the very possible so they could earn both a hackathon if they win and they could also earn something from the Sealy mission if they create something. + +Benjamin B: Yeah, I think this is until the end of the month. I don't see it. + +Tyler Wright: I think that's a great idea. + +Robert Del Rey: That's cool. Yeah, so next time idea. + +Tyler Wright: I think just speaking out loud and this is very much off the Record while we're on the record. So anybody listens to this later don't hold me to this, but in terms of Partners like file coin, stored storage a storage. However, they're pronounce SEO RJ currently the team. + +Tyler Wright: Uses our weave for saving videos in the cloud perpetually, so I think figuring out ways to build Integrations with these kinds of projects and see being another one other web free projects. I really love the idea of building on the back of a hackathon that's already happening, but any of those kinds of projects building in Integrations and workflows that use a cash and those Storage Solutions I think those be great addition to the network and things I know that people are asking for. + +Benjamin B: Yeah, so let's write this down. I'll save all the properties. + +Robert Del Rey: I wrote some then already. Thank you so much Tyler, and just to confirm I got it right Do you mean creating missions that encourage building Integrations with other projects like file coin they have? Another storage solution you suggesting that we do hey build this storage Solution on a cache for file coin for 500 akt and put that as a mission on Siri, right? + +Tyler Wright: Yeah, it's like a whole bunch of people that I know are trying to be decentralized as a principle right and to try to figure out workflows and wish they could use things like a cops and other decentralized infrastructure right now. It's very fragmented. So everybody is doing their own thing and building their own one solution. It would be great. Even if those one-on-one solution continue to exist if there was a simpler way. That maybe could be reference and… + +Robert Del Rey: + +Tyler Wright: documentation or elsewhere. It's like If you're trying to do this kind of workflow just use a cache and X storage solution, and putting these commands and do this thing, and it'll just be easy, and I think that's what we're trying to do make the user experience easier for folks. I'm an integrate with other projects where we can + +Robert Del Rey: Really? The species open today, I guess. So if you're gonna say something guys use young green. + +Benjamin B: All So from what's Scott said here? I actually think that makes a lot of sense to create some of these workflows to be boundless instead of and rewarding them for silly. What we could do is that we create a mission on silly but we don't write the rewards there. We say that you can get involved with the bounties and you can get involved with this hackathon. but We're not gonna waste any of the budget from the ceiling what do you think about that guys + +Robert Del Rey: Yeah. Absolutely. + +Scott Hewitson: Yeah, it's like a call to action to earn more or try more. + +00:25:00 + +Tyler Wright: Yeah, that makes sense to me. + +Scott Hewitson: yeah, I think I mean,… + +Benjamin B: Let's continue that often. + +Scott Hewitson: I know everyone's got a bunch of great ideas, not shooting any down, but I think if we stay within the scope of zilly zealy for now, I like all those ideas like we've got the Bounty funds and something that I'm trying to I want to happen more in 2024 is as cigs and working groups. they have ideas. It's like this would be cool and it's a small effort. It's like let's throw it up as a bounty. So I want people like the groups to be coming up with Bounty ideas and stuff. So it's all good stuff in my mind. + +Benjamin B: Let me jump back into what I was talking about earlier. I was talking about some of the missions. I was thinking of and the third mission is that I think that we could have more detailed mission on what it means to be a provider so we could have a mission for creating a provider. Maybe we should have specs as a requirement Maybe. a GPU and not only the specs but of course, let's Force some uptime as well. We didn't do this last time and we had to reward someone who had it up for probably a few minutes. + +Benjamin B: the fourth mission is kind of similar to what I was. I started mission to the validator one including this one already and I was thinking that maybe we should reward users and the guide them to the GitHub discussions. I think the more people were getting involved there and if they were to create research posts on GitHub discussions or getting engaged in a lot of discussions I think that we should be able to reward that as a mission. The last one that I was thinking of is creating a well edited short videos that shows either how to deploy a specific topics maybe react apps or python products to a coach. or + +Benjamin B: showing how to just deploy dockering much in the course. I think that if you were to Get a short video out that's well edited and shows how to use a coach the full process in a minute or two. I think this would be really valuable and if we're lucky a lot of people could see that. And that could be some great marketing. and so for my ideas + +Robert Del Rey: appreciation brother + +Robert Del Rey: you cannot cover a lot of different missions that we can start playing with. This is good stuff, man. Thank you so much. + +Tyler Wright: Yes, I love all those ideas and they're very specific and really meant Focus. the GitHub discussions idea while I like my only hesitation is now we're just incentivizing people to just leave comments where maybe they wouldn't be inclined to have such a strong opinion before and now we're just for the sake of money to just putting something up there. That's my only hesitation with incentivizing comments. All the other ideas. I think are great. The only thing that I would add is for the provider side if we can get Folks at least think about IP least it's a person's storage. I know that those are underutilized features on the network for providers set up. So I just want to add that but I think those ideas are great. I love the video ideas as well. + +Robert Del Rey: Yeah, me too. I also like that providers Mission specifically we focus more on having developers and builds done in this pilot, but I guess we can expand and have providers missions. Like they say provide this amount of resources or stay up for this amount of days. I guess those will be good missions, too. + +Robert Del Rey: and I believe Tyler we agree on the GitHub discussions participations. I guess it's good to have those missions in case people want some extra XP points, but we shouldn't attach akt rewards to those kind of missions and it's the same for retweeting Missions following inviting friends those missions. I mean, it's nice you can do them, right but they shouldn't pay you akt because then as soon as we run out of we progress stop doing those things. + +00:30:00 + +Robert Del Rey: Go ahead and you? + +Benjamin B: first of all, I want to say that I agree with what Tyler says I think that comments could be created even though they don't have an opinion. I think that posts could still make sense. But even then people could just try to find something very minor that doesn't really affect anything.'re so some pros and cons to this one. We could also have it be attached to the + +Benjamin B: support issues But I'm not quite sure. For what you said there at the end Robert. I think that it could actually make sense to have those invites payout Equity. not only if their friend were to actually complete submission. I'm not sure if this can be tracked but if you can invite people and get akt it works until it doesn't kind of like yourself, but it's also a great way to get more people involved. Now. We have 20 people if I remember correctly. + +Benjamin B: if those 20 people were to get another 10 people. That would be a great difference. + +Robert Del Rey: Thanks, I love to work on this week. Thank you for dropping those ideas guys. I guess I have enough material now to expand and reassure again. not think of some I already have the mission's ideas, I will just shape them up in a way that you can see them as missions on ceiling and then we'll send that and go from there. But yeah, I will focus on three areas. + +Robert Del Rey: In not any particular order, but just three areas for the new nations. I want to focus on network Integrations and tools missions like Tyler was saying if we can make people build Solutions on a cash that they other people can use that's great for the network validators And providers missions. Go ahead Tyler. So your head? + +Tyler Wright: so, yeah, the only thing that I'll add is I think can you hear me? + +Robert Del Rey: Yes. Yes sir. + +Tyler Wright: okay, I was just gonna say I think both Benjamin and… + +Robert Del Rey: Goodies are clear. + +Tyler Wright: Huey said that my idea about Integrations with stupid for zealy and it's better use for the bounties and they said that I should stop talking and I'm an idiot and I think that we need to focus our time on the Provider missions as well as the video and something the ideas that Benjamin so you don't have as much. To do that again. I think they said that it was an idea. They're trying to this pity me and say all right. This is a decent idea, but we'll have to use that for Bounty. So just we can focus on the provided Missions at Benjamin outlined and then yes and also the videos of how to deploy or dockerize something. + +Robert Del Rey: Okay. Thanks that thanks for that. + +Scott Hewitson: It's Tyler. You matter don't let any of us tell you you don't you matter. Okay? + +Scott Hewitson: And we love your ideas. + +Robert Del Rey: Thank you so much guys, I'm pretty sure that maybe we heard the same words, but we understand something different. I didn't get but they were saying that your ideas were stupid tighter, but thank you for saying that. + +Robert Del Rey: No, It's fine. Let me rewrite that again then. and the content creation missions like creating short videos about I guess the I guess Benjamin. I'm going to send you some messages in the DM so I can have more specifics and we can make those missions and we're gonna share those missions in the cash silly so guys can see them and maybe have people to start doing those missions right away. Let's see how we go. But yeah, I might keep you posted throughout the day. I guess a good way to start off the week. Like I said, I got 19 messages requests on Discord. I will go ahead and verify those filtered those. + +00:35:00 + +Robert Del Rey: Take the scammers out and keep the legit ones and then go from there. And guys any other common you want to bring up before we're up? + +Robert Del Rey: Okay, I'll see s Okay, those thumbs down. It's because you don't want to end the call now or because you'll have something else to say. + +Scott Hewitson: I don't have anything to say to add. + +Robert Del Rey: That Just You're scared. Thank you again so much for joining. This is the last see me working group called all the year. We started I later over a month ago, and we have these from just a concept in our minds to an actual thing on silly page, but I can tell you there's still a lot to learn a lot to do. but I'm pretty we're going to find a way to make this beneficial not only to a cash but also the people that participate in the missions because many said this and for what would you say baby? This was the biggest part for me was getting people that never tried a cash before getting people. + +Robert Del Rey: Tried on cash for the first time and on top of that air needs to make a tea and I guess that sets them up for a good initial experience when I cash or a good beginning in the cash Community because this people might just join randomly to this silly initiative, but maybe in the course of three four months six months we can have one hell of a contributor that came randomly because of these campaign and they just gonna drop that thought I literacy your hand up Go ahead. What's up? + +Tyler Wright: Yeah, just real quick. again much appreciates Robert your leadership and it's also Benjamin your leadership. I know that as next steps you guys are gonna be talking via direct message to finalize some of the next missions after that. I'm guessing you'll agree on with those missions are post them and then start sharing messages to let people know that over the next couple of weeks. There's around two and based upon the success of the pilot version one going to be extended and then extended I guess through that first week of January, is that the idea and you're all said, have it run until January 5th or something where that we couldn't transform. + +Robert Del Rey: Yes, I want to have this ready ASAP… + +Tyler Wright: Okay. + +Robert Del Rey: because yeah,… + +Tyler Wright: Okay. + +Robert Del Rey: the plan the planets have it running on to January the 5th. So right now I'm more like pressure to coming up with a few. + +Tyler Wright: Perfect. + +Robert Del Rey: Maybe two more missions, Finalizing these rewards pain the required stuff with initial winners. and having that announcement out as soon as possible hey guys, you can still continue doing some missions and earning some extra akt So that is like the order. + +Tyler Wright: amazing + +Robert Del Rey: Awesome guys anything else before we run this up for the day? + +Robert Del Rey: All right. Is not guys remember… + +Scott Hewitson: Think we're good. + +Robert Del Rey: if you have Thanks Ben you thank you all for joining. Thank you for listening the recording also in case you have any other questions thoughts courses are requests feedbacks drop by the cash working group City channel on Discord. You can also send me at the end on this score if you have me on telegram And without being said when I see you guys stay safe for the holidays. Enjoy the time with the family, whatever you're gonna do enjoy it and let's reflect on this year and come stronger for the next year in case we don't talk again. I just letting you know These Guys these are my wishes for you for next year. Okay. + +Tyler Wright: Amen, happy holidays. Yes. + +00:40:00 + +Benjamin B: Thank you very much, Robert and everyone. ability + +Robert Del Rey: Happy holidays everybody. + +Scott Hewitson: Have a good one. + +Robert Del Rey: Thank you. + +Scott Hewitson: okay by + +Meeting ended after 00:40:20 👋 +