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..cbddd8a9 --- /dev/null +++ b/sig-design/meetings/011-2023-11-08.md @@ -0,0 +1,386 @@ +# Akash Network - Design Special Interest Group (SIG) - Meeting #11 + + +## Agenda + + + + +## Meeting details + +- Date: Nov 08, 2023 +- Time: 08:00 AM PT (Pacific Time) +- [Recording](https://mctlnmdevhysanes52tbok6kbc3mgbsgnn6qemc35xhanfc2x67q.arweave.net/YKa2sGSp8SA0ku6mFyvKCLbDBkZrfQIwW-3OBpRav78) +- [Transcript](#transcript) + + +# **Attendees** + +- Benjamin B +- Denis Lelic +- Emmanuel Arthur +- George Pro +- Max +- Robert Del Rey +- Taiwo Omoyeni +- Tyler Wright +- Zach Horn +- Zeke E + +## Meetings Notes (notes from Denis Lelic): + +### Video Tutorials for Onboarding +- (Short, basic videos for new users ) +- Proposed topics: wallet setup, AKT purchase, cloud node intro, and first deployment + +### Swag and Merchandise +- Care packages for insiders and community members +- Explore new swag items (e.g., embroidered sweatshirts, sweatpants). +- Use print-on-demand services for merchandise. +- Share swag ideas on Discord. + +### Marketing Assets +- Utilize the marketing repository for assets +- Suggest additional assets if needed + +### Content Creation +- Seek community input for content topics +- Encourage short-form content creation (videos, blogs, etc.) + +### Website Development +- Invite community members to join website development meetings +- Provide feedback and insights on the Akash website + +## Action Items: + +# **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-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/wg-akash-website/meetings/012-2023-10-12.md b/wg-akash-website/meetings/012-2023-10-12.md new file mode 100644 index 00000000..67e3b436 --- /dev/null +++ b/wg-akash-website/meetings/012-2023-10-12.md @@ -0,0 +1,567 @@ +# Akash Network - Akash Website Working Group (WG) - Meeting #12 + +## Agenda +- New Website Section Proposal: "Development" +- Progress Update on the Website Revamp +- Update Discussions ( Current Website ) + +## Meeting Details +- Date: Thursday, October 12, 2023 +- Time: 6:30 AM PT (Pacific Time) +- [Recording](https://5gn7dg3s3faifxnf6w5uqoabieslbqre2ywps2nyhotoc54tvsiq.arweave.net/6Zvxm3LZQILdpfW7SDgBQSSwwiTWLPlpuDum4XeTrJE) +- [Transcript](#Transcript) + +## Participants +- Daniel Moore +- Denis Lelic +- Emmanuel Arthur +- George Pro +- Tyler Wright +- Zach + +## Meeting Notes +- Tyler provided an update on the most recent version of the revamped Akash Network website. +- Tyler Mentioned of Piyush seeking Docs 2.0 from Luna from the previous meeting. +- Tyler mentioned he has shared the Docs Docker image in the AKASH website working group chat on Discord. + +### Progress Update on the Website Revamp + +#### Denis Lelic: +- Provides an update on Human HQ (Piyush and team) working on the ecosystem page. +- Mentions technical features allowing users to filter deployed projects on Akash. +- Explains the delay in the weekly update on the page due to ongoing work by Piyush. + #### - Content Requirements + - Zach mentioned that Piyush needs content for around 15 pages. + - Denis provided insights based on Piyush's previous mentions and identified homepage as the top priority. + - Denis acknowledged that the homepage content provided by Zach is a work in progress and needs integration into the design. + - Zach emphasized the importance of coordinating with Piyush directly to discuss content requirements, urgency, and potential challenges. + +### Updates (Current Website ) + +#### Denis Lelic: +- Arthur's work on the "get started/deploy" page. +- Integration of Cloudmos and presentation of two deployment options on a single page. +- Denis shares the link in the chat for everyone to view Arthur's work. +- Mentioned that everything is functional, and the only outstanding item is the deployment tutorial. +- Emphasizes the need to find a way to embed the video in two tiles without overcrowding the page. +- Commits to creating mock-up options to determine the best approach to embed the video. +- Assures Arthur that once the videos are ready and uploaded to YouTube, he will be notified for page updating + +### New Website Section Proposal: "Development" + +#### Denis Lelic: +- Denis introduces a new concept called "Development." +- Presents a rough concept where the user can click on "Development" in the menu, offering two options: "Network Development" and "How it Works." +- Mentions including general information on providers, tenants, and options for adding network activity. +- Denis expresses uncertainty about where to integrate this new concept, considering the existing community section. +- Discusses the potential impact on the community page and suggests the idea of freeing up space for more focus on projects and meetings. + +#### Tyler Wright: +- Tyler expresses enthusiasm for the idea. +- Supports the idea of simplifying the user experience. +- Suggests the possibility of having more navigation headers if needed. +- Raises a concern about the delay in updating information from the community repo to the website. +- Proposes working with Piyush and the team to ensure more real-time updates, especially for meeting notes and other relevant content. + +#### Zach Horn: +- Appreciates the concept of the development page and suggests tracking conversions to assess effectiveness. +- Expresses support for the idea of making it easier for people to discover working groups without direct promotion. +- Highlights the opportunity for downstream discovery through calls to action on the website. +- Emphasizes the importance of minimizing clicks for user accessibility. +- Proposes brainstorming ways to visualize the interconnected information, such as using diagrams or visuals. + +### Calendar Module Exploration: +#### Denis Lelic: +- Suggests considering a classic calendar option for a good overview, citing examples like Airbnb. +- Explores the idea of leveraging a familiar user experience from well-known platforms and incorporating it into the website. +- Suggests consulting with Piyush and exploring the possibility of using a plugin to implement a module similar to the one seen on the Adobe Max page. +- Expresses the need to determine if such a feature is feasible within their current capabilities. + +#### Zach Horn: +- Inquires about the literal module, expressing willingness to look into it. +- Mentions Kubernetes as a potential reference for calendar structure. +- Inquires about the feasibility of implementing a module similar to the one observed on the Adobe Max page, questioning if it's within their scope and if it requires a plugin. + +#### Tyler Wright +- Shares insights on how Kubernetes manages calendars using Google Groups. +- Acknowledges the less-than-optimal communication in Google Groups. +- Highlights the shift to Discord as a more dynamic communication tool. +- Proposes the idea of having individual calendars for each special interest group or working group. +- Raises the need for people to easily sign up for specific meetings and suggests having a dedicated calendar for each category. +- Discusses the idea of breaking up content blocks, potentially using visuals similar to those seen on the Adobe Max page. + +### Other matters discussed +- Tyler suggests the idea of posting working group meetings on YouTube to increase visibility and participation. +- Tyler mentions the potential for a better user engagement on YouTube, similar to other organizations like Adobe and Kubernetes. +- Decided to explores the possibility of creating a distinct category on YouTube to highlight working group sessions. + + +## Action Items +- Denis to mock up options for embedding the video tutorial. +- Denis to Notify Arthur when videos are ready for updating the current website page. +- Tyler to collaborate with Piyush and the team to address the delay in updating information from the community repo to the website. +- Denis and Zach to consult with Piyush regarding the feasibility of implementing a module similar to the Adobe Max page on the Akash website. +- Tyler to explore the option of posting working group meetings on YouTube for increased visibility and better user engagement. +- Zach, Denis and Piyush to plan the next steps for implementing content on the homepage. +- Group to explore on how to make it easy for users to sign up for specific meetings. + +# **Transcript** + +_This editable transcript was computer generated and might contain errors. People can also change the text after it was created._ + +Tyler Wright: All right, welcome everybody. To this week's edition of the Working Group for the Akash website it's October 12th 2023. The Akash website meets on a weekly basis Akash website, working group, rather meets on a weekly basis to talk about the current Akash website as it stands today. I mean, there's also been a successful proposal from Piyush and the human HQ team where they're working on a complete revamp of the Akash website. As previously mentioned on a number of occasions Greg Started off this process by creating V1 of the Akash website where it was designed using github pages and designed to be something that can be open source and can be maintained by many members of the community. + +Tyler Wright: in that vein and based upon again, what Greg started Peters and his team are working to Take the Akash website to the next level by structuring some things a little bit differently. So it's easier for folks to contribute, they're adding tailwind CSS. And again they're optimizing some of the pages that Dennis Zach and others have been looking to optimize for some time. I could see Arthur on this call and Arthur again, was one of the first contributors from the community to help with the website. So we want to shout out Arth he'll always have that title of first contributor. And again Arthur has been helping, not only with the current website but we'll continue to help with the revamped website when it's available. + +Tyler Wright: I know Peers who I also want to shout out again represents the human HQ team. He is not going to be able to be here today at the meeting here at the conflict, but did put a message in the discord where again, many members of the Working group for the Akash website, discuss things between these weekly meetings. I'm going to put an update in the chats of the most recent version of the Akash Network revamped website. But without further ado, I'm gonna hand it over to Denis before hand over to Dennis. I know that there's one thing that Bold Panther It was looking for out of the last meeting, which was docs 2.0 From Luna. I've dropped that docker image in the working group AKASH website, chat, so that + +Tyler Wright: Be pierced to this team have access to it and then again, we can start to implement the docs 2.0 into the revamped website. So that was an action item. That was on me coming from last week and after some challenges getting it I was able to get it to him again, have shared it in discord inside the working group AKASH website. Discord channel. + +Tyler Wright: So again with that further ado, I'm going to hand it over to Denis to see if there's anything we want to talk to talk about related to the current website. Or if we want to talk about anything related to the website, read the app. So Denis, take it away. + +Denis Lelic: Thanks Yeah, you're pretty much summarize everything we did. And what happened previously? and thanks for sharing the link for + +Denis Lelic: Human HQ, aka Pierce and his team and to be able to check the recent updates on the website. As far as I know, they are working on the ecosystem page. which has + +Denis Lelic: some maybe technical features there where users are going to be able to Filter all of the deployed projects on Akash and everything that's happening around the Akash and so on. So maybe that's why we're not seeing The weekly update on the page. They probably need some more time to do that, which is Of course, reasonable. And one thing Arthur. + +Denis Lelic: Did last week is the get started, slash deploy. Your ad, where we present two products. One is cloudmose, and a previously. We had two tabs where users were able to switch between those two and now we have one page and two tiles to presentation of those two options to deploy. I'm just gonna, The link in the chat to everyone can see. What Arthur did? So, thanks. Arthur. Here, it's functional works and so on the only thing we owe you is the deployment tutorial. + +00:05:00 + +Denis Lelic: Yesterday, we talked about one option, where we would embed the it's not working. + +Tyler Wright: Maybe it's just me, but I just try to click on that link and I didn't work, so it could just be a meeting. That's why I didn't want to interrupt you. + +Zach Horn: Link Works. + +Denis Lelic: Anyone else has that issue? Okay, it works for… + +Zach Horn: the link works for me. + +Denis Lelic: So I don't know. Maybe try incognito. + +Denis Lelic: yeah, yesterday we talked about an option where we would embed that video tutorial which is in the making at the moment we have automatic 1111 for console and we have another example for cloud nose, and we just have to figure out Away. To embed that video in these two tiles. So we're not messing up everything and making it overcrowded. So I'm just gonna mock up a couple of options and see what works best. So yeah, Arthur we owe you those videos and as soon as they're ready and they're uploaded to YouTube, I'll let you know so you can update that page. + +Denis Lelic: Otherwise. Pretty much covered the progress from the last week. There's one thing I'm thinking about which is still kind of a rough concept. And I'm just going to share my screen. + +Denis Lelic: Here it is. + +Denis Lelic: So at the moment, it's called development. So this part here, + +Denis Lelic: there's also a menu option here In the Menu section here. So when the user clicks development, it's presented with two options. One would be like network development and the other one would be like how Network development is pretty much what we have at the moment with a couple of new things in the sidebar. Where we could? Present meetings roadmap and stuff like that and the other one how it works. is just like an overview of How? Akash network actually works. And we can talk about in general information providers, tenants and there's options to add Network activity, and + +Denis Lelic: Yeah, it's just a rough concept and all of the content here. Is taking out of bosses presentation, a news presentation, Greg's presentation where they talked about how the network works and what are providers, who are tenants and so on. And + +Denis Lelic: a while ago, me and Bob were just talking about how great would it be to Have that on the website. So it's not just Part of some close conversations, close presentation's, but something that anyone who visits the website, I can just read through and maybe it's gonna provide some information. And to provide some clarification for users to see what's actually behind it. And Yeah. What do you guys think? + +Tyler Wright: I love that idea. + +Denis Lelic: The only thing, I personally didn't know where to include it because we have the community section. and if you paid attention community page, is where everything ended up like everything that community wanted or internal team wanted from the overclock kind of ended up there. So just providing some new pages would kind of free the community page where we can focus more on the projects on the meetings. + +00:10:00 + +Denis Lelic: And stuff like that. So, + +Tyler Wright: Yeah, I think to your point, we should be moving some stuff off the community page and even if we have to have more nav headers, unless again, someone like Zach disagrees. I think that. I don't like for the user experience to be a little bit easier so that people can just one or two clicks to this kind of information as opposed to having a click into community page, and from there click into someplace else and just creates too many clicks. While I'm thinking about it and maybe this is something that I'm going to put in working group for the class website. + +Tyler Wright: but on the community page, I think it was their original attention of Greg to have things from the community repo inside the Akash Network organization automatically be added to the website right now, the way that it's being written the information from the community repo, Does not come to the website in any amount of real time there's a great deal of delay. So something I want to make sure that we talk about with Piyush and Team is making sure that again as working group. + +Tyler Wright: As the things get merged into the community repo for meeting notes etc. Hopefully those can get merged pretty quickly into the active website so that anybody that goes to the website and wants to learn more about Diggs and working groups can have the most up-to-date information as opposed to a dated experience. So that's something that I certainly want to work on with peace and for future meetings. + +Denis Lelic: Yeah, yeah. I agree. Zach, you have any thoughts. + +Zach Horn: I think this sounds great and I think one of the biggest things we need to do right now is make it easier for people to discover our things and working groups, without promoting them directly because I think we've exhausted the direct promotion we can do. But I think there's lots of downstream opportunity for people that are coming through. our calls to action when they land on the site that they might discover those groups and want to participate. So anything we can do to closer to the top level of the website the ties point about multiple clicks I think is good. Outside of that, I do like the idea of the development page in general because One thing we can do as we start building this out and getting, our analytics all the way set up is start tracking how we're converting on this pages, which would be interesting to me, if we start trying to drive traffic to them directly in blog posts and other assets. + +Zach Horn: Would you mind Denis real quick just zooming in on the development page? + +Denis Lelic: So, one thing I have to mention, why we don't have dropdowns in the menu is something that Greg didn't like and he tried to avoid it. But as the website grows, we're kind of keep adding stuff here. And Sooner or later we're gonna have to think about adding a drop down or something, for example. That's why. When you click Development, You have two options one. The other option would be like development and you click down or you just hover and then you're presented with these two options. Now you have to click this page is going to load and then you see, okay, network development, how it works. So network development, Is this thing? + +Denis Lelic: So we have the product strategy, community groups, current projects meetings Roadmap could actually be part of the other one. Or this one so because it's kind of overlapping. But did you had any question or something like really specific you wanted to see here? + +Zach Horn: No, I'm just taking it all in. we don't have to reinstall right now but One thing that has jumping to mind when somebody lands on this page is that we make it really easy for them to understand what they're seeing. I don't have a super great suggestion for that right now, but we can definitely brainstorm on that. Maybe it's something like a visual or a diagram or something like that, just something to visualize how this stuff all interconnects and Maybe it looks like a quick start or a summary section towards the top, just something to say, Okay, if you want to, what is Akash where we headed? maybe it's just as simple as a roadmap diagram. That just gives them … + +00:15:00 + +Denis Lelic: Yeah. We have. + +Zach Horn: where we are. And what's coming soon. + +Denis Lelic: We had a roadmap somewhere here. This is the latest one. So we had the mainnet 6 and… + +Zach Horn: + +Denis Lelic: the GPU and Multi currency support. So we are basically here. And there's another updated version of this, which pause I created for bus, but anyway, + +Denis Lelic: yeah, so I agree, we could kind of visualize This thing in a better way. And you're + +Denis Lelic: yeah. I'm just thinking, is it part of + +Denis Lelic: This community development of the project or is it about Akash or which is basically how it works. + +Zach Horn: Yeah, that's a good question. So on that product strategy and execution, I think that was the page that you're just on. + +Denis Lelic: Yeah. + +Zach Horn: What is the? I'm just reading really quickly. + +Denis Lelic: This is something that's on the current website as well. + +Zach Horn: So, this is that document, that lays out the entire product strategy. Right. Okay. + +Denis Lelic: Yeah. + +Zach Horn: I think this is great. I mean, it's obviously a really really build out document that gives people everything. + +Zach Horn: Summaries and high level. points would be something I would look to pull out of this. Could I just + +Zach Horn: It's something that maybe we can make a little bit quicker for people to consume. That would be My one immediate thing you go back to the top of that page real quick. + +Denis Lelic: And there's one thing like AI ml Workloads is at the bottom, maybe we could. Talk about that sooner in the upper section. + +Zach Horn: what tab is? I'm on my laptop screen so everything's a little small over on the left side. this. Document is under community groups. + +Denis Lelic: One can. + +Zach Horn: Right. Okay. + +Denis Lelic: So I'm just gonna share a link here. + +Denis Lelic: So, this is core groups and pro products that strategy, and it's pretty much the same content as on the current website. + +Zach Horn: Got up, okay. + +Denis Lelic: the way it's structured as you see those tabs on the left, + +Denis Lelic: it's just offered right away. There's no need for one, click on the Core Community groups and then a second one for the current groups and the current projects. And so on you basically just click through Strategy Groups Projects, Without additional drop-down menu. + +Zach Horn: The got it, okay? + +Denis Lelic: And then, of course, we have the Community contributions and insiders and Akashi edu. which, Could be part of the, classic not Community Development page, which kind of goes into different directions, still close to each other but + +Denis Lelic: I have a feeling like we could separate that just to provide a little bit more clarity and for users to consume all of this information. + +Zach Horn: Yeah. Yeah, that makes sense. + +Denis Lelic: because if we're talking, if we have a look at the community page, We have contributions so we can have I don't know, an article from George, Arthur, Robert Pierce. And so on and we can have events so we can post photos there from the recent conferences, for example. We could have. + +Denis Lelic: Bounties maybe, but still Bounties could be up here. + +Denis Lelic: And then we have Akash insiders, maybe a contributions board, where we list all of the recent contributors and we can pull that data from GitHub, whoever created a PR and we can just list those people here. + +00:20:00 + +Denis Lelic: Of course, The upcoming events for example. + +Denis Lelic: here we have cosmovers I'm sorry and we can include others as well. And of course we can provide a link for a car swag shop. This is more into. Community and community building and events and everything that's happening. And it's kind of like connecting with community and the other one would be still community but I would call it differently like development or something, because it's more focused around the projects product meetings and six working groups. + +Denis Lelic: Like roadmap, what's into plan? Or which meetings are happening today this week and so on, + +Zach Horn: Yeah, I'd like the vision of it. I think one of the things that Paige could do really well is This is just my theory. but that when developers come to Akash, If they're deciding where to spend their finite time and skill and all that they want a quick way to see Okay where are you guys like? What can I work on? what's the workflow? And this feels a lot like what that page would be, it's like Wait for developers just land to be like,… + +Denis Lelic: Yeah. + +Zach Horn: Okay I see where the project is today. I see what you guys are working on. They can get a quick overview of public working groups and all that. And then decided whereas the best place to jump in as we're, So if I'm thinking out loud, Developer lands on the development page. what's the top level page? They see when they hit that button in the NAV. + +Denis Lelic: so, the first starting from the homepage, You have development. + +Zach Horn: Yeah. + +Denis Lelic: And then you're presented with two options. One would be like how it works or about Akash or something. And then we talk about these different tenants general information network activity maybe pricing and then we have Something that I still don't know how to call it, but it's + +Denis Lelic: network development and everything. That's happening around the projects meetings working groups CIGS and so on, but I just don't find the right wording for it. So I know you're gonna do a better job than me here. + +Zach Horn: We can definitely iterate on that. So if they click through on network development, where do they go? + +Denis Lelic: Then they're presented with this product strategy,… + +Zach Horn: God, + +Denis Lelic: community groups, current projects meetings roadmap, we could add bounties here. We could add. Governance propo Guidelines here. + +Zach Horn: Okay, so okay, I see now. So The flow The UX of all this looks great. I see Greg's position on the dropdowns of the Nab. I also see your position that maybe it just be easier. If this was a drop down the nav and not have the Intermediate landing page where they have to see that. + +Denis Lelic: Yeah, this one. + +Zach Horn: It might also be good to have it. I could see that I'm here nor there on that but + +Zach Horn: So they land on the page, that drops them on product strategy. So, We have a content, not problem, but we have a content opportunity. We need more content for that page and probably a high level page that gives them an overview. Because I can imagine a developer landing on that page and + +Zach Horn: maybe not wanting to dive into all of the information. So they land on something that's like an overview page that quickly is here, I'm just thinking a lot, top three initiatives. Here's what we're working on in the next couple months. If you wanted to jump in today, here's where we need developers currently. + +Zach Horn: And then here's our second working group structure. And probably those things would be connected. So it's like, if you want to contribute to X, here's the working group the corresponds to that. So, here's the next meeting. Etc. Etc. So it's a quick start guide almost like, Here's what contributions. in this direction. Here are associated bounties here. The working group. That's the info. I think that a developer would need it, they land. And when I get started right away, + +00:25:00 + +Denis Lelic: So we need something which is Get started with Akash which presents options for becoming a provider deploying or just joining a community. So here we need something to get started. With your user's contribution or community members contributions. + +Zach Horn: definitely. Question for you. And we can sink offline if this is out of scope for now. But is there a way to show the calendar? On the website in a way, that's embedded without slowing things down and causing a bunch of problems. + +Denis Lelic: I think we could provide a list of + +Denis Lelic: of meetings. And then we could add a filter option, weekly monthly. so, we have Basically a button like a drop-down where you just switch between Show me, daily meetings, weekly meetings, monthly meetings and we basically just list them. + +Denis Lelic: Maybe something in this form. + +Denis Lelic: let's say this is working group. + +Zach Horn: Yeah. + +Denis Lelic: Our website. And then we have a small intro and add to calendar. + +Zach Horn: I see so it's not embedded, it's not programmatic, it would just be static content but we could still outline what they are and then have the Add to Calendar button, okay? + +Tyler Wright: We could because dar is a Google calendar with all the working groups in special interest groups. We could theoretically, just embed the entire calendar into the website. I do like that. I like Denis what you're putting forth, but I do like, The Zach's point of having more visual elements site wide. But specifically here something that people to look at and be like, all right, Monday Tuesday, Wednesday and no, + +Tyler Wright: And yeah and no. … + +Zach Horn: Yeah. that was my thought,… + +Tyler Wright: all right, cool. + +Zach Horn: is that when somebody's coming in, they just want to quickly, see what's coming up this week or next week, does that am I gonna be available all that? + +Denis Lelic: That sounds good. I'm just making notes. So that's something we can discuss with peers as well. And just explore different options. + +Zach Horn: Sure. + +Denis Lelic: It's either providing a list. + +Denis Lelic: Just having a good overview but I'm just thinking from other projects. What's out there? + +Zach Horn: Yeah, I'm definitely flexible on how it gets implemented. just my initial thoughts on this. I think that the high level goal is just to make these things less opaque because I feel like they may be a little opaque right now. If you're not already first where the stuff is, and how it happens and all that. + +Denis Lelic: Yeah, I for sure agree. We need to improve that Just to find a better form to present meetings, working groups, maybe we encourage people to join. And we'll just have to explore what's possible here. + +Zach Horn: Definitely. + +Denis Lelic: they have, just maybe something to think about. An example, it doesn't have to be like a Web 3 or something. I'm just thinking a classic calendar option where you can with a good overview, maybe like airbnb or something, or skyscanner or something. That's Out there that's familiar to users that has a familiar user experience and something that we could leverage maybe and just basically copy and put it here. + +Zach Horn: you mean the literal module? Yeah, let me take a look. The + +Zach Horn: so, if you're thinking about website flows and all that, obviously The airbnbs of the world are. Super smooth. The thing that is. So the one that always comes to mind is + +Zach Horn: Not for a calendar module, but Kubernetes in general because they have a similar working structure. I wonder how they do their calendar and that's what I'm looking for it. + +00:30:00 + +Tyler Wright: They do Google groups. obviously Kubernetes is out of Google and… + +Zach Horn: Do that, okay. + +Tyler Wright: so when I originally started and this is something I tried to basically copy early on when we're doing this open model, they do Google Group. So each stick and working group is a Google group and so basically they're individually maintained. So when you sign up to George, go to a meeting, you're only signing up for that specific Google group, they have conversations between meetings in that Google group. I think it was less than optimal. and where I think maybe not discord specifically but I discard tool beat it is just like it allows for more constant communication where I feel like we're falling short right now is I have everything in one Google calendar. and so it's either people can download everything or nothing and so it's about thinking art does each + +Tyler Wright: Special interest group or working group need its own specific calendar. So people only signing up for that and they're only getting added to a specific kind of meeting. Theoretically right now You can do that by just messaging me and be like, Hey I want to be added to only the working group for the Akash website and I can add you directly to the invite but people aren't taking advantage of that. So we got to think of That People can easily click and just have it and have one, maybe specific special interest group meeting, which I think is less likely. But at the very least have one special interest group category that they can kind of sign up for if that makes any sense. + +Zach Horn: It does make sense I'm looking at Kubernetes right now. That's their community group age. It's very, very similar to our current version. + +Zach Horn: I'm trying to sign up for a meeting right now just to see how they do it. Okay, so they use zoom links directly. So if you go to that page and you click one of the meetings like Thursdays at 10 am Pacific it literally just launches you right into. + +Zach Horn: that's good context. I think we probably need to. Maybe find a different way to do it. The Kubernetes is obviously, but a bigger than we are. But + +Zach Horn: It's good to see that they do it, as simply as that. + +Tyler Wright: Yeah, that's one thing I was actually thinking about doing was having the next meeting be at the top of the Readme file and people would just click right into Google, but because I'm only one person a Neil and others were like, We can't do that at scale, we can't do that for meeting every week. + +Zach Horn: Yeah. + +Tyler Wright: Which I don't know if I agree with especially if I have support from folks like George Pro and others, But again we decide not to go out direction the short term. + +Zach Horn: Sure yeah my high level point on scalability and all that as we may need to do things that don't scale until we reach scale but yeah I don't strongly disagree. + +Tyler Wright: Yeah, I like that and I think that makes sense. + +Zach Horn: Yeah. + +Denis Lelic: Yeah, I think this is a good example. I saw it a while ago, but I kind of also, some of the other content that provided care, code of conduct and stuff like that, which I'm seeing, we could have. A menu option here for. Governance Proposal Guidelines And stuff like that. But because I'm a designer, of course, found another example. which is this one and I kind of like This module here. Which is upcoming. and you can present three options that are happening today, and the others could be just Sessions all sessions and you can filter them just like Kubernetes Has it there. + +Denis Lelic: and we can just provide a headline, a short description, the time when it's happening, and a button to So, either Join or to add to calendar. + +Zach Horn: that this looks great and, no disrespect to the fine folks of Kubernetes but this is definitely a bit better designed + +Tyler Wright: I would agree with that. And again, I think I kind of said this three minutes ago. part of me for saying it again. But I do want to echo Zach's point. I did put a plus, 100 in the chat. I love the content on the current website. I do think that there's way which we can break up the content with some more visuals. I know that we want to be content heavy but I think Zach made a good point of even if it's big things up a boxes or similar to what we see on the page with Adobe Max here. I think we can do a better job of just breaking up content blocks so that it's a little bit easier to digest. + +00:35:00 + +Zach Horn: Yeah, definitely. + +Denis Lelic: And they have a great calendar actually here. + +Zach Horn: Yeah, this is very good. + +Tyler Wright: Yeah. + +Zach Horn: I'm taking it all in right now. What? filter by day and then by the Segment of meeting, and then each meeting is on its own track with the time. + +Denis Lelic: Yeah. + +Tyler Wright: I love this and hard You can add to calendar. do by region,… + +Denis Lelic: Yeah. + +Tyler Wright: we wouldn't have that necessarily but we can do it by Kind of SIG or working group or something, + +Denis Lelic: Yeah, and then you have details details for each of the either working group or six. + +Zach Horn: Yeah, this is excellent and if you go back into any of the meetings into that meeting detail page. It calls out the featured products that they're going to talk about which in our world could be roadmap initiatives that are being worked on. So you could filter that way as well. this is very good. + +Denis Lelic: Yeah, I like this one. It's kind of easy to track for what's happening for example today. And there's filtering options. + +Zach Horn: And you get localization, too. Wow, that's a little ahead of where we are, but yeah. I'm always thinking down the line like that. If we get to have meetings in different regions,… + +Tyler Wright: Yeah, we do need. + +Zach Horn: that would be excellent. + +Tyler Wright: Yeah, that would be amazing. I would even say before that we do need and discord does a good job of that right now but I do think we need timing localization. Because again, we have people all over the world even right now and so when meetings get assigned they see Potentially. it's gonna be nine, am Pacific having to do that math all the time. It's kind of sucks for people. But if it just localizes for them then that would be I think ideal + +Denis Lelic: yeah, even for the past meetings, for example, If you would go to the previous day you can just watch on demand and you just click and watch the recording? Yeah, we're kind of working only dreaming. + +Zach Horn: Yeah. + +Tyler Wright: Yeah. + +Tyler Wright: Yeah, exactly. switching 90 links per day, I'm about it, + +Zach Horn: A Denis. Could you Click View on one of those videos? I'm just curious what the actual player module looks like. So it's synthetic YouTube, okay? + +Tyler Wright: Yeah, I love the + +Denis Lelic: Yeah, something like that. + +Denis Lelic: or at least, just I don't know where it is, but if I saw it somewhere, + +Denis Lelic: At least having a detailed page for the sake or for the working group. Something to explain Who's the leader of a certain group or something like that. + +Tyler Wright: I are we as a tool? But I do wonder if we posted The working group meetings on YouTube if that would cause more people to know, they exist and then participate. I mean, if Adobe's doing it, I know Kubernetes is doing, or maybe the Kubernetes using zoom, but I know that other organizations are like, all right, they keep the content alive on YouTube, really going anywhere. and then it lets people know okay, I can watch these meetings without having to go to Github. And, yeah, I just think it's maybe a better experience, but + +Zach Horn: The UX is definitely better. My only thought on that is For something like Adobe Max. you can see these videos they're very produced. It's not a,… + +Tyler Wright: Yeah. + +Zach Horn: I'm not opposed to putting them on YouTube. I do, We really have to think a little about how that blends in with our other content though. Because they're working groups so they're not produced, but + +Tyler Wright: Yeah. Yeah I think that's a good point Zach. I was thinking maybe making its own category again, people just know they exist because slide it down but again we're not doing it right now. I'm not saying we have to do it anytime soon but I wonder If enough people come to YouTube and be like, wait they have these working group sessions with a talking about things and I'm interested in and maybe they would watch that faster than they would watch it via the read me and go to. Are we etc? + +00:40:00 + +Zach Horn: Yeah, I think that's definitely true. + +Denis Lelic: yeah, we could try and see + +Zach Horn: For sure. + +Denis Lelic: the Kubernetes. + +Zach Horn: so, obviously this is a very built out module lots of development and Lots of stuff happening behind the scenes for that. Adobe Max module, excuse me. + +Zach Horn: What is within our scope to do something? Even close to this direction? Is this possible for us? + +Denis Lelic: I mean we would have to talk to Pierce and… + +Zach Horn: Would it? What do you think? + +Zach Horn: Yeah. + +Denis Lelic: to see If this is, Maybe some sort of a plug-in. + +Denis Lelic: That we can use. If it… + +Zach Horn: + +Denis Lelic: would be great. So, just having a look here, + +Denis Lelic: If it's a plugin, it's great. + +Zach Horn: Yeah. + +Tyler Wright: Yeah, maybe we can either talk about this next week or drop it in discord and What? Piercings, that? It sounds like this is the Perfect, inspiration for us as late at least the highest level. Of what we like and maybe we can do some sort of version of this, possible. + +Denis Lelic: Yeah, I mean and what would be here then? working groups and six. + +Zach Horn: Probably the categories of what they fall into is the first thing that comes to mind. So could be website,… + +Denis Lelic: Yeah. + +Zach Horn: or network or something. Whatever. + +Denis Lelic: Yeah. + +Denis Lelic: It's good. + +Zach Horn: Yeah. Yeah, good find. + +Denis Lelic: I'm gonna have a look at maybe a different conferences. And if someone is using something that we could use as well, some sort of a plug-in or maybe it's like an open source solution or I don't know. We can hope for so we'll see. + +Zach Horn: Sounds good. + +Denis Lelic: And that's what live Here the right window. + +Denis Lelic: and this would live somewhere here under network development or some whatever we're gonna call it later. And we could provide that in the overview upcoming Meeting sessions, whatever. + +Zach Horn: Yeah, that makes sense. I like the development page a lot. I think we should Thank Richard, move forward with that. Definitely if you should. On board. + +Denis Lelic: yeah, and then we couldn't then we have space just dedicated for community and community contributions the proper community page where we're not talking about project and project building But just more, connecting and events and kind of the More loose version of that. more relaxed and I hope I made it clear. And I lost. + +Zach Horn: Yeah. + +Denis Lelic: I spent all of my English vocabulary. There's a limit limited characters per day and I guess I lost them all. + +Zach Horn: That's funny. you're on the free plan, you get limited use it. + +Denis Lelic: And I'm in a minute or so there's gonna just be a button to pop up like upgrade now. + +Denis Lelic: And about Page. This is something we could play around. I just grabbed those presentation that are floating around. And something basically just to cover from a high level what Akash is and how it works. + +00:45:00 + +Denis Lelic: yeah, I think that's something I personally wanted to discuss and to see your guys opinion on But thanks for the feedback. I wrote down some notes, and I'm gonna try and see what can we do here, especially, with this module for, and the overview page and how to Provide. More engaging content. Including the calendar and visual stuff you've mentioned. but, + +Zach Horn: Sounds good. I'd be interested, as well, as to hear what that calendar module. Looks like in terms of getting on the website One thing really quickly. + +Zach Horn: Piyush mentioned last week that he's in need of content for several pages. I think it was like 15. we can reach out to him directly and just see from him, but from your perspective, Denis what is the prioritization on those pages which ones are needed? Most immediately? + +Denis Lelic: Last time he mentioned I made notes so just one second. homepage would be the Priority number one. and then we have + +Denis Lelic: The token page. I think just one second. + +Denis Lelic: And pretty much The. Rest of the pages. + +Denis Lelic: Working on, for example, the Akash ecosystem page. We don't have much content here because we're just listing the projects that are currently living in the air table. And so, yeah. The first one would be the home page which you already provided some of the content. But I see you've marked it as a working progress. So some of it, it's not applied into the design yet. So whenever you have time, have a look at the homepage for example, and then we will take it from there and Find. What are the next steps? + +Zach Horn: Got it, that sounds good. Hey, Welcome. + +Tyler Wright: Go ahead, Daniel. + +Tyler Wright: Then your mic is on, you're not muted but we cannot hear you if you're speaking. + +Tyler Wright: sure, as to why Daniel. + +Zach Horn: You may be audio issues, Daniel but feel free to type in chat if the mic isn't working. + +Tyler Wright: Yeah, if you can hear us this is a working group for the Akash website. Again as previously mentioned this working group meets every single week of anybody from the community or anybody that cares about Akash Network wants to join and contribute. They're more than welcome, this working group is happening in two phases. There is a current website right now, which I'm sure you've seen access or you've seen network. There are some small changes being made to that website. And then there is a team that's successfully. Got community funds to develop a revamped website, that's built in Tailwind CSS, and it's going to be optimizing gonna have some more of the pages that have been discussed by this team right here. And that's being worked on right now by Push and his team. And you can kind of see the updates here. So again during these weekly meetings, we talk about various pages that need implementation or need design development, or copy development, from folks like Denis Back and others as well as + +Tyler Wright: where we are with the current revamp and making sure that again, it's optimized for folks so that when it goes live in a month or so it's a kind of user experience that everyone's looking for but Daniel we would love your contributions whether it's today or a future meetings. So feel free to jump in to discord and give any feedback, thoughts questions concerns or again, feel free to join these meetings and you're more than welcome to talk. I know you still have your hand raised. Have you been able to fix the audio issues at all? Daniel can you hear us at the very least? Can you give us a thumbs up if you can hear us? + +00:50:00 + +Tyler Wright: That's all right. again Daniel if you or anybody else on this call or who's listening to this, when the recordings made available, once wants to feel free, to join any future meetings, that happen weekly at 6:30 am Pacific on Thursdays, or again, feel free to get involved via SIG design or the working group for the Akash website. This will throw a message in discord and then again, we can make sure that your messages are heard and added to the agenda. Or again, you can join future meetings and contribute live. I do want to shout out George who've been helping out with note taking for this working group and some others. So again, thank you George for your help there. And we'll continue to again, merge, all the work that you're doing behind the scenes again. Just reminding you to update the readings as well. + +Tyler Wright: Daniel I don't want to cut you. But again we finished at 6:30 am Pacific on Thursdays every week. Yes, Daniel. And then again, addition at that time doesn't work, we can adjust that time. But again, we do have folks everywhere from the West Coast to Europe, New York Africa, so it's like India so it's like, folks all over the world and so 6:30 a.m. Pacific with the best time for everybody. I know it's like night for Denis. I think it's night Very late for folks in the end early morning for folks in America + +Tyler Wright: But again, if you have any questions, thoughts, etc. Feel free to drop those in discord where, again, we stay pretty up to date. You can see messages from push as recently as today and others? And you can again look at the current website. Leave notes, you can look at the website, revamp and leave notes and again, continue to contribute. It also be great Daniel if you could throw in a little bit about yourself and there, I know that Denis myself and Zach are from the Core team and Overclock Labs. George Pro is an insider based in Africa, and I think he's going to be coming to America soon for graduate school. Shout out And then again there's a couple of other members that are software engineers and web developers base all over. + +Tyler Wright: Anyone else have any Comments concerns before we wrap up this working group or cash website session? + +Tyler Wright: again a much appreciate everybody's time and discussion today we have a lot of next steps. Again, we can continue to talk online. Daniel, it'll be great to have you at future meetings or just again at the very least contributing in discord we're always looking for more folks that are interested in Shadow shout out everyone here again. We'll have another meeting next week and we'll continue to work in the meantime. So please let me know if you need anything, there will be a SIG analytics monthly meeting happening at 12 pm Eastern time, 9 am Pacific. But again, shout out everybody here and let me know if you Eating place, you can reach out to me. Tyler Core team and discord if you need anything else. Hope everyone has a great rest of the day and we'll talk online for Appreciate everyone. + +Zach Horn: Thanks, Kevin. + +Denis Lelic: Thank you. Bye-bye. + +Zach Horn: Thank you. + +Tyler Wright: All right, bye. + +Meeting ended after 00:54:10 👋 + diff --git a/wg-akash-website/meetings/015-2023-11-02.md b/wg-akash-website/meetings/015-2023-11-02.md new file mode 100644 index 00000000..6d36f59e --- /dev/null +++ b/wg-akash-website/meetings/015-2023-11-02.md @@ -0,0 +1,569 @@ +# Akash Network - Akash Website Working Group (WG) - Meeting #15 + + +## Agenda +- Website Revamp Progress +- Discussion on Website Revamp: + - Docs Integration + - Get Started Page + - Community repository integrating workflow + + +## Meeting Details +- Date: Thursday, November 02, 2023 +- Time: 6:30 AM PT (Pacific Time) +- [Recording](https://5yiuwpekrvtf2cbtg7nlfoox2nccndvl5iydxvqzbv2ppfyomvia.arweave.net/7hFLPIqNZl0IMzfasrnX00QmjqvqMDvWGQ1095cOZVA) +- [Transcript](#Transcript) + + +## Participants + +- Denis Lelic +- Emmanuel Arthur +- Piyush Choudhary +- Tyler Wright +- Piyush Choudhary + + +## Meeting Notes + +### Website Revamp Progress + +##### Denis Lelic +- Mentioned a discussion on cosmetic changes and UI polishing. +- Focused on using the latest Tailwind components to avoid previous issues. +- Denis had a question about the impact on build time when hosting the website on Akash Network. +- Denis requested Piyush for a short update on the progress made on the website. + +##### Piyush Choudhary +- Piyush dropped the link in the chat for everyone to see the live website. +- Significant progress reported on almost all pages except for docs. +- Docs page to start after receiving approval from the group. +- Minor design changes to be made based on Denis's directions. +- Real-time APIs are being implemented for the open metrics, and other real-time data updates every 10 seconds. +- Piyush explained that the build time would likely remain the same when hosting on Akash Network. +- Raised concerns about the feasibility due to the need for frequent updates to the Docker file and SDL file on Akash Cloudmos. +- Provider page also being worked on, with two audited providers already on the live website. + +### Docs Integration + +##### Denis Lelic +- Mentioned a discussion on the integration of the docs page. +- Noted the transition from Hugo to Astro, with Piyush and his team taking responsibility. +- Aimed for a longer-lasting and better user experience. +- Emphasized the importance of gathering crucial touchpoints in one website. + +##### Tyler Wright +- Tyler expressed the importance of considering the structure and frontend elements, particularly the sidebar, in the migration process. +- Emphasized the need to reference the existing structure and mentioned Greg's preference for it. + +##### Piyush Choudhary +- Piyush suggested asking Luna's team to deploy the structure to make it visible for reference. +- Mentioned ongoing work on the official website and proposed collaborating with Luna's team on the migration. + +### Community Repo Integrating Workflow +- Piyush explained that the displayed content, including meeting notes, is generated from Markdown files. +- New notes can be added or updated in real time by modifying the relevant Markdown files. +- Clarification sought by Tyler about the process of updating notes. +- Piyush clarified that updating the Markdown files is done within the website repository. +- Tyler inquired if updates also pull from the community group repository. +- Piyush confirmed that updates are specific to the website repository and offered to discuss the details after the meeting. + +### Inquiry about Pricing Page Design +- Zach praised the inclusion of tools for budgeting and expressed their significance for marketing purposes. +- Zach inquired about the design of the pricing page for hosting on the website, expressing the need to share it more broadly during external communications. +- Zach inquired about the real-time nature of the data and how it is queried. +- Denis shared a Figma drawing of the pricing page, explaining the two stages for calculating prices, including GPU options and a comparison to other cloud providers. +- Piyush explained that the Pricing data is real-time and dependent on Cloudmos APIs. +- Piyush mentioned an issue with the GPU part, as it's not implemented in Cloudmos's price calculator. +- Denis acknowledged the concern and explained the two options, one with GPU included when possible and one without for now. + +### Launch Strategy and Walkthrough Video +- Zach suggested recording a video tour of the website upon launch, showcasing its various features. +- Zach inquired about the timeline for the website launch. +- Piyush provided an update on the timeline, stating that the functionality part would be completed within a week or two, with final design adjustments to follow. +- Mentioned potential blockers related to content but expressed confidence in a three to four-week timeline. +- Denis emphasized taking the time to ensure everything is working and looking as intended before the launch. +- Tyler suggested considering testing strategies and planning for a walkthrough video to highlight the website's features. + +### Other Matters Discussed +- Tyler brought up Anil's suggestion to use a visual roadmap and inquired about embedding GitHub project boards. +- Shared the link to the GitHub project boards in the chat. +- Piyush expressed the need to check the GitHub API to determine if embedding project boards is possible. +- Tyler reiterated Anil's preference to sunset the old project list in favor of the new one he shared in the chat. +- Piyush confirmed willingness to explore embedding the GitHub project boards on the new website. + +#### Twitter Image Previews +- Denis raised a question regarding Twitter image previews, expressing the need for multiple images based on the content shared. +- Piyush acknowledged the need to explore Twitter's handling of links and image previews to determine if multiple images are possible. +- Zach suggested using graphics as social images for blog posts, incorporating some version of the headline in the graphic, and establishing a universal standard for post graphics. +- Proposed adding a label or badge to the graphics to quickly convey that it's a blog post. +- Denis agreed with the suggestions and expressed a willingness to explore the implementation. + + +## Action Items +- Group to discuss testing and launch plan for the new website in the next meeting. +- Tyler to collaborate with Piyush to understand and clarify the update process, especially regarding the community group repository. +- Piyush to collaborate with Luna's team on the docs migration process. +- Piyush to investigate the GitHub API to determine if embedding project boards is feasible. + +# **Transcript** + +_This editable transcript was computer generated and might contain errors. People can also change the text after it was created._ + +Denis Lelic: Hey everybody. Welcome to today's working group meeting for Akash website. We meet every week on Thursdays where we discuss. everything website related from content design and for the last couple of weeks. We've been working on website revamp. We got designs ready and we're discussing. + +Denis Lelic: Weekly updates with piyush and his team. They got a proposal. I think one and a half months ago. At least what's appears told us yesterday on the Syrian Community where he presented? + +Denis Lelic: Couple of pages and the progress there. They're making on the website. + +Denis Lelic: But for today's agenda, I'm not really sure where the start since piyush is not here to check on the update if anyone has that link of his I think it's been the same all the time. Please drop it And the chat section here. + +Denis Lelic: One thing we would like to discuss is the docs page integration where we had previously had a different team Luna and quo search starch. team Health transitioning dogs to who go and now since we're switching from Hugo to astral build piyush and his team are going to take care of another transition and hopefully it's going to be one that's gonna last longer. We're hoping for a better experience. and basically to have all of those crucial touch points gathered in one website. So I've good cohesive experience + +Denis Lelic: starting from docs ecosystem page, which is currently not part of the website and it's hosted somewhere else. + +Denis Lelic: yeah. That's about it a short retrospective and the current. Things we're working on me and piyush talk yesterday on. a couple of cosmetic things just polishing UI making sure we're sticking with Tailwind components + +Denis Lelic: me personally, I'm gonna try to make sure we're using the latest components. From the Tailwind Library we had some issues Console as everyone knows so I don't want to repeat that mistake, and I'm just going to keep an eye on those things, so they're implemented properly. + +Denis Lelic: Hey piyush. + +Denis Lelic: Hey piyush. We are already starting a meeting. But you didn't miss much just a short introduction… + +Piyush Choudhary: Yeah. + +Denis Lelic: if you would like to present. I know we talked yesterday during steering committee, but Maybe just a short update on the progress you've made on the website. Could you please drop that link of yours in the chat section? + +Piyush Choudhary: yeah. + +Piyush Choudhary: So yeah, I dropped in the link in the chat to see it live. So we have made a significant progress on almost all the pages except dogs. So we will be starting the dogs after getting a green signal. So I think they were certain discussions my own so I will chat. But that is to find those things on our dogs and then we will start. The dog space as well most mostly rest all the things are mostly done only they'll be some minor changes to the design as per the directions defined by Denis and we'll be looking for those. so the progress is good. And also we are implementing the real time apis. So it was still the real. Nuclear motor for the page. You see the open metrics. These are all real time. + +00:05:00 + +Piyush Choudhary: the data is being updated every 10 seconds that is best from the one you have and then we'll be implementing rising and network activity page. So it's real time data, of course, so we see the darkness and then we also have a provider page and Akash system, which will also have that to audited providers today. It's on the live website. So yeah, that's a + +Denis Lelic: Sounds good. I know you had some blockers from last week and week before that regarding content. + +Piyush Choudhary: he + +Denis Lelic: Is there anything that's not clear enough? Or blocking your progress. + +Piyush Choudhary: so we have implemented most of the condom you proceed. I want to development page. We saw that in the file and they get the welcome and Community groups always bring a spine but I need updated content on for these three pages sages wgs and ugs and I saw that There might be some work groups as well. Let's say there are total 500 overview. So + +Piyush Choudhary: yesterday I was seeing that an answer was presenting a momentum file related to sigs or dedicated sizes as well. So I think it would be good if we can create some MD files for a particular side you update or let's say there is a signal light X, So again, it's going to belongs to the Sig so we will have the meeting links and all Etc. Then what we can do is we can have the sub section. So all dedicated sigs. Let's say seeing light it's so we have second this. Then we have seen documentations lines. I mean those amplifiers we can have the latest update and latest Etc and the leadership and the team who is working there. + +Denis Lelic: Yeah. Tyler go ahead + +Tyler Wright: No, this looks beautiful. The only question I was going to ask is as new notes get added and updated will this update in real time? + +Piyush Choudhary: If so, basically what you are seeing here, let's take this. This is the meeting link, So this is nothing but md5. So if the new not needs to be added you just have to add you lines to them before and it will be updated in real time under website. so Basically as long as the markdown files are getting changed in the record,… + +Tyler Wright: Does it pull dark do I have to update? go ahead. Sorry. + +Piyush Choudhary: everything will be updated in here then on the website. + +Tyler Wright: Okay, and just for simple clarification sake when you talk about updating the MD files you're talking about in the community group repo or do we have to do something inside the website repo? Okay. + +Piyush Choudhary: website River So it's all a part of a website that you are soon. + +Tyler Wright: Okay, previously. I think that the website was pulling in data that happens in the community group Repro because again, I update all the notes of community group repo. I would have to figure out with you offline how You imagine Is it updating notes in two areas? That is the goal or how do you see it? Yeah, that's Emmy and… + +Piyush Choudhary: If Yeah,… + +Tyler Wright: we have to talk about this right now if you don't want. + +Piyush Choudhary: so basically What's Happening Here is let's say I'm on the development base, So there is a development folder inside the content if I go here. + +Piyush Choudhary: So these folders are nothing but this folder contains all the containing log down files. So even if you are seeing let's say the home page. So whatever you are seeing on the homepage the text and everything is coming from the Northbound 5, so you don't need to be equivalent to change the wings. So you just have to come to this model file and just add it the links or text whatever you want to let's talk about the development page. So this is what the development page is. Let me go to the point of the game. So I'm on the development is right. So this is the development page. So basically What's Happening Here is we have + +Piyush Choudhary: we have five sections as you can see welcome current projects for website and boundaries and similarly. We have all these things like welcome strategies current projects Community groups boundaries. So let's say I want to make a change to the Sig so it's nothing but among down file from which the data is coming. So I like which so I go to Community groups and I have the special interest groups as AGS and I just have to change the model as you can see. I just have to add if I let's see I want to add something. + +00:10:00 + +Piyush Choudhary: So meeting turning, right? + +Piyush Choudhary: if you see there are two datas, So each data we have the meeting then we have the information where we are adding the links and all right. So I just push it I've added one more thing. So it's in the markdown in form of content. you see So here it's visible. It will take two minutes to build so birds in progress previously. It wasn't the case. So basically what used to happen is it used to take around 20 to 35 minutes to actually build the file and here it is going to take only maximum one or two minutes to complete the will and the changes will be visible here. So you just have to make the changes in the markdown quality form of a Content. There is no technically involved by doing this. + +Tyler Wright: Okay, I think. + +Piyush Choudhary: and also we will also create a proper blog defining if someone let's say Jack wants to update so for example, we have a Proper guidelines like how to display this kind of box so we have written a custom thing. So you just have to add a single word box in the markdown file. So it will appear automatically here. So we will have a proper blog on how to update them out on file if something custom is needed what commands to use by updating them all done. So Yes, we can. + +Zach Horn: Hey piyush. Just want to say this is awesome. + +Piyush Choudhary: Yes. + +Zach Horn: I've been working with flat file CMS for a really long time. So this is great to see I mean and especially when we were dealing with PR based updates, over the past year or so, and we're dealing with that 30 to 40 minute build time. It's really tough to do that. So to hear that, it's what you say two minutes. + +Piyush Choudhary: So basically I posted it's already live so it took around 1 minute 5 seconds. So you see the third. + +Zach Horn: amazing + +Piyush Choudhary: Second is visible. + +Zach Horn: Fantastic, that's gonna make our lives much much easier a quick question for you. So on this page, I understand… + +Piyush Choudhary: please + +Zach Horn: what you're saying about, just going into the markdown file and making changes. I think there may be some copy updates that need to be made here that could Theoretically change the formatting of the page if you scroll up a little bit. Where you are? Yep to that light red call to action. I'm thinking that we could use maybe a different headline and some body copy in there. so I could go in and just change the markdown file to add that but I'm wondering if that's gonna Push that div around in a way that changes the structure of the page, if it's a significant amount of copy, what do you think about that? Do you want me to go in and make those changes now so you can have a look at it and restyle before this goes live or do you just want to keep going with development? Maybe we Circle back on this later. + +Piyush Choudhary: So basically as you can see the box that you are seeing here, so we're implemented with custom functionalities for it. and if we go to the markdown for + +Piyush Choudhary: Let me check. So if we go to the mount on file as you can see, this is the blog posts right so that you use to put basically text So basically what we have done here is if you see on the technical side. We're implementing the custom. Code but as a Content creative, you don't have to worry about that. You just have to write call to action banner and the banners this will appear automatically. So even if on the other Pages such Banner is required with this increase in between and the hiding so it is not possible through basic markdown passes, which we have just only the whole life easier and also if I can find + +00:15:00 + +Piyush Choudhary: This is a simple post as you can see. So this is how the code will look we have the copy sections. And also when it comes to the blog posts, we have multiple options. I don't know. + +Piyush Choudhary: this is the block So you just have to write similar to what is written here all to action Banner. We have the guideline on how to make it So. There will be different text even if you don't write it will be simpler one. But if you want to keep it like this, there are other options. I will properly create a block for this how to use such custom functionalities and it considering on the markdown, but even if you use the Current structure of yours, like whatever structure, it will be passed perfectly as in the front end as in different industry. + +Zach Horn: Yeah, this looks fantastic. + +Piyush Choudhary: and also Yeah. + +Zach Horn: To interrupt you Could you scroll back down to the code blocks at any of them? So these are + +Zach Horn: Okay, so you can copy and paste those full sections. that's fantastic. Can you do tabs at the top? just like + +Piyush Choudhary: Richard yeah this one. Yeah, we just have to write in the code would be. + +Zach Horn: Yeah, This is fantastic. I mean we've hit this for a really really long time especially the inline formatting that you've done, where you can see the highlighted text in line. That's really really great. + +Piyush Choudhary: What? I like to see this is the yellow one. We also have a single line word that you just need to add to the glove for and it will be like this or reddish. You just have to write danger for green. I just forgot what yours also I'll properly create and blog where everybody finding how to make the block for being red or whatever. Etc and properly pass things of + +Zach Horn: Okay, sounds good. + +Piyush Choudhary: So yeah, that's awesome. + +Denis Lelic: Up I have one question what happens when we host? The website on Akash Network. What happens to the build time? I saw you're using versa. it's + +Piyush Choudhary: so basically when it comes to hosting on the Cartoon Network, so + +Piyush Choudhary: The build time will remain same mostly but what happens is we just have to create the docker file, right? So after creating the docker file and I think it will not be feasible to post this on Akash Network because what will happen is whenever we make the changes to the record. So we will have to keep on updating the docker file again and again and then also updating the sdl file that is hosted on Akash Cloud nose, so it might be a issue for the developers or if the instant updates are needed. So when it comes to for example, the Cosmetic website is right now hosted on GitHub pages, right? So the version is full time will almost be saying they might be few seconds of difference. So right now as I push the change it took around one minute five seconds, so it may take one minutes 10 seconds. So that's all right. Now if you see the current web + +Piyush Choudhary: if I show you the current website, I'm not. + +Piyush Choudhary: even if the full on lines of code is getting pushed it is taking around 30 to 35 minutes to complete the bill. so + +Piyush Choudhary: as you can see for the build. It's soaked around 24 minutes and for deployment it took around 28 minutes to even build two lines of code. And while when I pushed to our website took around it total one minute five seconds to complete. + +Denis Lelic: Okay, Cool. + +Denis Lelic: and regarding the docs page Tyler you wanted to talk about it any questions or + +Piyush Choudhary: easy + +Denis Lelic: anything you want to share? + +Tyler Wright: No, no, I just wanted to reiterate that when it comes to just the structure. I know that it wasn't just Luna, the migration is one thing and I think it's fine for us to we migrate because I think there's a number of new documents that have been created since Luna's team did the initial migration but from a structural standpoint and maybe we could just reference. Let me see if I can find is real fast, either way the structure and the front end of the sidebar and how things were kind of set up. I know Greg really likes that which is why he had a Neil yesterday. He asked about it earlier in the week and the engineering sink. So I just want to make sure that we take that into consideration so that we don't get slowed down later. + +00:20:00 + +Piyush Choudhary: It's what we can do is we can tell the lunar stream to deploy it and… + +Tyler Wright: Yeah. + +Piyush Choudhary: if it's visible as you said it's already completed right so will not be a big class for them to deploy it and then migrated to the rockstar.com so you can ask their team to migrated if it's possible, but as we are also working on it for the official website, so I just have to ask you questions one is like as you can see in the content directory of dogs. These are the followers that will be visible on the sidebar and Cycles. Let's say I open buildings started. These are the MD files that will so + +Piyush Choudhary: there's one questions is I had a chat with Denis a last time you few days ago. He said that we don't. If I go to the Department. + +Piyush Choudhary: + +Piyush Choudhary: so even if I open the cloud most declared part, instead of having the proper MP5 anyone who I am having to subsections which is the same case here as well. So if you open this index code and We have the subsections. Let me see. if on + +Piyush Choudhary: what's wrong? + +Piyush Choudhary: from being technical support + +Piyush Choudhary: s + +Tyler Wright: So as I'm looking at this and maybe this is what you're saying the subsections are different in these new Docs. as + +Piyush Choudhary: right personally feel or maybe not so I just want Jack to take a look at the fullest structure and then defiles and the way MD files are being implemented here. because these folder structure will be going as if he's on the design. So let's say we have the getting started at first when I for example, let me show you how it will look. + +Piyush Choudhary: Let me open the double Point page, So this is the development page as you can see we have the header welcome Community groups current projects for website strategy roadmap and boundaries. So let's take this as an example. Let's say we have the getting started at first. So let's say this is the getting started that will be visible on the top when I will drop down similar in this case. it opened up the overview right? So when I will drop down on getting started I will have this overview I will have the homepage and then I have the options environment set up funding technical support your first plan. So I just want The content in to take a look at the content if it's hundred percent, correct? Because + +Piyush Choudhary: It is going to be a part of the dogs, right and dogs plays a very crucial role for the whole Akash the system. So I just want the content we make sure that the content that is depending all these prices hundred percent complete and correct. So when we migrate them to the Rock speech, they will not create an issues for the users. + +Zach Horn: Will probably need to pull on someone from our engineering team just to ensure that belt technically correct, but I'll handle that on our end and keep you updated. + +Denis Lelic: what about the let me just check quickly. + +Denis Lelic: I'm just looking at the current website and the working groups. and I'm just wondering if everything there is up to date or it's not building at all. + +00:25:00 + +Tyler Wright: No, it's not building at all. I was hoping ideally and… + +Denis Lelic: Okay. + +Tyler Wright: maybe we can have a separate call about this before next week. I was hoping I like the solution that appears put in and I know that Zach likes the fast build time so I don't want to mess around with it at… + +Piyush Choudhary: it's + +Tyler Wright: My one issue that I'm trying to think about quite honestly is right now everything. But I do from a note- from those taking standpoint lives in the community if we have to then update the community repost so that it's up to date there and then we also have to update. the website repo that might be less than desirable but not the end of the world. So I just have to think that through a little bit. + +Piyush Choudhary: Basically… + +Denis Lelic: + +Piyush Choudhary: if you see in case of the development Community groups this Siz the blue G and U G's are still not complete because I don't have all the details related to the meeting leadership contacts a project supposedly 11 results because it's Etc. So I just want the markdown file for these pages and once I upgrade them out on file into the website right with visible instantly here, so they will not be any major changes. + +Tyler Wright: Yeah, I'm not necessarily talking about major changes from the beginning. I think you all can do a great job of making it look the same my thought processes around me maintenance,… + +Piyush Choudhary: he + +Tyler Wright: I'm going to be maintaining and updating the readme file inside the community repo with all the information and then I'm gonna have to do the same thing inside of + +Tyler Wright: Inside of the website repo again, not the end of the world, but just something I'm thinking about also while we're on the subject right now. + +Piyush Choudhary: Yeah. + +Tyler Wright: I think + +Tyler Wright: Anil alluded to it yesterday that this section with the roadmap. I dropped it in the chat. I think he wants to use a visual roadmap. I wonder can we drop in embed those project boards from GitHub? I know that there is one already for engineering and road map. Yeah, I'll read drop chat, but I was wondering if we could do that versus the project list that you have shown up there. + +Piyush Choudhary: And this one? + +Tyler Wright: Yeah, yeah instead of that one. Look at the chat. There's a projects github.org slash the topic that one. Yeah, perfect. We do we looked at this yesterday a little bit. + +Piyush Choudhary: Really? + +Tyler Wright: And I know that a Neil wants to Sunset that project list board and just use this so I was wondering can this be embedded on that page? + +Piyush Choudhary: So I will have to take a look at the GitHub API. So if you allows us to embed it, so we will be able to generate it. + +Tyler Wright: Okay, cool. I think yeah, that would be better than project list because I believe that project list MD file that you are just referencing is going to be sunset. They're not going they don't want to use that anymore because it's too hard to maintain. + +Zach Horn: For the workflow things that you were just talking about I mean, is there an option where the website repo becomes the source of Truth for these things? So it's just one repo to update… + +Piyush Choudhary: e + +Zach Horn: which is the website repo. + +Tyler Wright: yeah, that's a good suggestion my fear is because so many people are used to community repo and… + +Zach Horn: Mm-hmm + +Tyler Wright: our error maybe wouldn't be an issue because they can just submit a PR on the website Repro. I think it's a good idea. I'm just worried about again people like changing their behavior and… + +Piyush Choudhary: he + +Tyler Wright: some issues going We post some of the project boards go in the community repo again. It's not that big of an effort To copy and paste but yeah,… + +Piyush Choudhary: really? + +Tyler Wright: I'll think about that. That's a good suggestion Zach. + +Zach Horn: Sounds Yeah good. I hear what you're saying on the duplicate effort part. But also yes, the fast Bill times are our ideal. So anything we can do to preserve those. + +Tyler Wright: Yeah, yeah, I will not whatever this I'd rather do duplicative work then sacrifice a build time. So I think what's the same page there? + +Zach Horn: pressure Okay, sounds good. + +Denis Lelic: What if we're not duplicating the work? meaning everything can live in the community repo, but we just add the links to the website repo. + +00:30:00 + +Tyler Wright: Yeah, that's what I'm saying that I don't think and maybe I over exaggerate so I apologize. What I think I would have to do is I would take the content that's on the readme file and that table that has the meeting links the transcript length and the recording and I would just have to copy that over and maybe just add a little bit of syntax on the website where you post I don't think it'll be that big of an effort, to be honest. + +Denis Lelic: or we could basically just link to the Community repo meetings notes and stuff on the website repo So when you let's say you're on the website you're scrolling through those projects,… + +Piyush Choudhary: just + +Tyler Wright: Yeah. + +Denis Lelic: whatever. And there's basically just a link that takes you directly to the GitHub. + +Tyler Wright: Okay. + +Denis Lelic: Community repo let's say I don't know Sig or working group or something. + +Tyler Wright: Yeah, that's a good call out. Basically. It's like a link to the readme file and then you click on that and you open up the readme file. + +Piyush Choudhary: So yeah, we already have that functionalities. So I think I go to implement this in this page, but when it comes to the block page, it will not be a big task. For example, if you want to update this blog. So we have the update post option. So it takes us back into the particularly file. So this will be the case for others as well. So I just lines of code. So when I am the Ducks and when I am on the development page, so let's say this is also coming from the readme file. I will just add update post section and when you will click on the update post people directly into the readme 5. + +Denis Lelic: I guess we'll see. In the next couple of weeks. What's the best way to work with this? + +Denis Lelic: I'm sure we'll figure things on the go so + +Denis Lelic: once back looking for my notes. So we talked shortly about the docs. That's quite clear for I mean, we'll see. when piyush creates The first section so let's say I don't know a home page for the blogs for the docs. + +Piyush Choudhary: he + +Denis Lelic: How that structure behaves the menu on the left and stuff like that. + +Denis Lelic: I couldn't find. the stuff Luna and his team did I just had one screenshot on my desktops living there so I could only refer to that and I shared it in the Discord with piyush and Tyler. But I Think We're Not Gonna Go Far Away from that. so it's going to be the same or better experience Yeah type. + +Piyush Choudhary: so just to give an overview on how the dot special look so we have four variants. So let's say on the left hand side as you can see, we have three sections when the phone get started and this is nothing but a table of content, so when it comes to the above talk to sections the home and get started the continual like They displayed on the whole page that you are seeing right now. It is taking the whole space and similarly when it comes to the website page. It will also taking the whole space as you can see and when it comes to the table of content. + +Piyush Choudhary: This is also. Place you So this is how the table of content will so we have the drop down section similar to what we did with the Development page as you can see we have the drop down options. So we just talked the line it so we will have the drop down options. And then when we click on the files the content will appear in the middle from the markdown by itself. As you can see here. And on the right hand side we have on this space section this similar to work there on the blocks or the customer. So this is how the dog's page will behave and the user experience will look like + +Denis Lelic: Okay, cool. Yeah Ty + +Tyler Wright: It's gonna say I found an old issue for the docs migration. I put it in the chat. It's issue number 86 inside that issue. I think you can find the spec for the hierarchy as well as some images as well for that sidebar. So I just want to have an additional reference. Let me know if you want. Luna's team to establish and we bring up some of those website, but I know Denis you gave feedback on some of these items. But again has that kind of structure. I'm not saying and just want to make it clear pH. Can you go back to the center of this image? I'm not saying doing anything with that middle box. I think that the way that you all have it with the main section is optimized and way better than what + +00:35:00 + +Tyler Wright: What suggesting docs 2.0? I my only concern is this left bar where the zero dot was zero one is because I know that again great has explicitly talked about liking that so I just want to make sure we keep that top of mind about Exactly just a category and… + +Piyush Choudhary: this one + +Tyler Wright: headers and where some of these docs are nestled. That's all I'm concerned about. + +Piyush Choudhary: and also as you said to ask him already completed the thing so it will be better if you can ask the lunar system to make it live and share the link so we can have some Lego view of how you understand. + +Tyler Wright: Absolutely, I'll do that. + +Denis Lelic: cool Sounds good. + +Denis Lelic: Yeah, the issue 86 you've shared Tyler. That's the same images. I found on while I was searching on my computer. So + +Tyler Wright: Okay. + +Denis Lelic: yeah, I don't think that's gonna be an issue. We're so gonna have this menu on the left. Yeah, and hopefully it's gonna be better. Experience than the current website docs and dark 2.0. So basically this is a dark 3.0. + +Tyler Wright: I love it. + +Piyush Choudhary: he + +Denis Lelic: Okay, anything else we have? To discuss anyone wants to share anything. + +Zach Horn: Yeah, really quickly the pricing page that we're thinking about now hosting on the website. How do we have a design of how that's going to look and the reason I'm asking because it's something that I'd like to share more broadly when we are doing external Communications and even designing lightly hands around pricing on Akash. I just saw the link usually click through. + +Piyush Choudhary: + +Denis Lelic: Yeah, I can share the figma drawing we have at the moment. + +Zach Horn: Okay. + +Denis Lelic: Let me know if you can see my screen. + +Zach Horn: I can't. I can't yes. + +Denis Lelic: You can. okay, so there's + +Denis Lelic: What two ways to go? Basically for the first stage, I'm not really sure if we can share the GPU stuff. To calculate prices. So the way it's set up now is you have a couple of options to choose from presets and it's going to change the bottom parameters here and then you just hit calculate price and it's gonna give you a price and the second stage you're gonna have a GPU optimized and… + +Piyush Choudhary: he + +Denis Lelic: you can add different GPU models and also change the parameters for memory and stuff like that and hit calculate price and it's gonna give you + +Denis Lelic: price estimate and Some sort of a comparison to the AVS Google or Microsoft. + +Piyush Choudhary: So yeah,… + +Zach Horn: Right. Fantastic + +Piyush Choudhary: so these one issue with the GPU part we were exploring the cloudmoss and I cleaned their price preparator the GPU. Stuff is still not implementing. + +Denis Lelic: Yeah, yeah. + +Piyush Choudhary: The GPU thing right now will not be possible but others since + +Denis Lelic: that was my concern also, because that's why I said we have two ways one is to include the gpus if that's possible. If it's not we're just leave them out and when it's possible we include them the Arthur other thing. + +00:40:00 + +Denis Lelic: Greg and O'Neill mentioned was the let me see if I have that here. + +Denis Lelic: provider incentives so we would just add a Text field and a call to action for the Prater calculator. So anyone who's interested in becoming a provider they can just hit this button and go to The Prado calculator and see what would their earnings look like? + +Zach Horn: Amazing because from a marketing standpoint, there's two cohorts of people that end up bucketing themselves when they're interested in Akash, and it's exactly what you would think which is how much does it cost if I want to deploy and I have resources how much can I earn so surfacing those two tools? I think it's gonna help us plenty of Thumbs Up from Ty and agreement + +Zach Horn: so yeah, I think would you guys have looked great looks great a question though when You may have just said this I was clicking through the site as you guys were talking. + +Piyush Choudhary: still + +Zach Horn: How are you pulling the data? Is it real time? Or are you querying some interval. + +Piyush Choudhary: So it's realized for example to open the open page. So it's a real time API and it's all more of dependent on how the cloud most is doing. So we have got the access to their apis. So we are implementing the same way the cloud Moses in on the basis. and personally,… + +Zach Horn: Got it, okay. + +Piyush Choudhary: I think + +Zach Horn: Okay, sounds good. + +Denis Lelic: cool + +Denis Lelic: Yeah, and there's also one section and that's called network activity. So I think that's gonna live on the website as well next to the pricing and stuff like that and they're gonna remove it from the cloudmouse. + +Denis Lelic: I think the block Explorer and stuff like that that's going to live on the website. + +Zach Horn: Right, okay. + +Denis Lelic: Yeah, because it's kind of not a deployment. thing so anyone interesting and how much? Akt is spent or something like that or what's happening on the blockchain? What kind of blocks was actions that are going on? You were just go about Akash page and there's gonna be a menu item on the left called network activity with a couple of sub items and you can just go through all of them. + +Zach Horn: This ecosystem page is Excellent, but definitely makes sense. + +Tyler Wright: agreed + +Zach Horn: … + +Denis Lelic: Yeah. + +Zach Horn: I was avoid, brainstorming on these meetings, but As I'm like watching you click through the website. I'm thinking that when we launch this we should have someone record a video of them essentially giving a tour of the website looking around and just showcasing all the parts and hadn't had that thought before right now, but let me draw that up and just see what that might look like. And we can chat about that as we get a little bit closer. what's the timeline a dentist? I think you had mentioned at the other day. But what's the latest to have this launched? + +Denis Lelic: I think piyush management mentioned yesterday three to four weeks. + +Zach Horn: Okay, sounds good. + +Piyush Choudhary: It can be released on not before but there will be lockers related groups the most they are mostly lockers related to the contents. So we are almost done I think within a week or two. The functionality part and everything will be done and complicated and we are going to start the final design. Leave you with Denis. So the things that are not aligned properly with the Tailwind CSS default layouts will be changed a little bit as for the directions defined by Denis and the protein and Currently there are no blockers. We can launch this a lot before but I think three to four weeks would be fine. + +Zach Horn: It's okay. + +Denis Lelic: Yeah. I wouldn't push it let's do it in a week when there's any events ahead of us or something like crucial stuff going on so we can just take our time and make sure everything is working properly everything looks and behaves properly and stuff like that. + +00:45:00 + +Tyler Wright: Yeah, and make sure the links are optimized and all that kind of stuff. So, yeah, I think after maybe a little bit starting next week, but after we should start thinking about my testing strategy and then a path towards I really like the idea Zach of a walkthrough video of all the work that piyush's team have done and just the experience. Go ahead. + +Denis Lelic: Are once one question just something that came into my mind. Let's say someone is sharing the website on Twitter. And there's that image preview. currently I think we have one image and it's called something Soren infrastructure the scales. What's the best way for us to have multiple images so we can switch? + +Piyush Choudhary: we + +Denis Lelic: Based on the content. We're sharing on Twitter, for example, because I know Twitter now is not allowing the headline from the things you're sharing. So basically you just see an image on a short link. So maybe we could leverage that to include some of headlines included in the graphic. I hope I didn't complicate too much. + +Piyush Choudhary: Don't I just have to explore how Twitter is and links? So when we share the link on the Twitter, I just have to look on how process the data while passing that links. So accordingly. I will try it's possible into the multiple images. So if I click on your Twitter on the Twitter. I will see if it's possible to have the multiple images in place, but I haven't explored that yet. So I will just take a look on how the Twitter is doing that and what data needs as + +Denis Lelic: Yeah that Zach. Do you have any thoughts on that? + +Zach Horn: Yeah, I think if it's technically possible sharing the graphic, especially for blog posts as the social images is ideal. And what we could do from a Content standpoint is make sure that some version of the headline is in the graphic. So when we share the link on Twitter and the graphic people can quickly see that it's a blog post and be what the headline is and Denis maybe we can come up with is a universal standard that we use for our post Graphics that includes some copy that says, Akash blog poster, something like that just so that we share the link there's a standard format. So people can quickly see that It's a blog post because they won't have the headline. + +Denis Lelic: Yeah agree, we could label it with some sort of a badge or something. + +Zach Horn: Yeah, definitely. + +Denis Lelic: Yeah, we can explore that. + +Zach Horn: Sounds good. + +Denis Lelic: Okay, cool. + +Denis Lelic: Okay, we have five more minutes left. If you guys have anything else to discuss, please let me know. Otherwise we can wrap it up. I know some of us have another meeting coming up. So. Just to have three minutes of break in between those would be nice. + +Denis Lelic: Thanks for participating Arthur as always it's good to see the progress. + +Tyler Wright: but + +Denis Lelic: We're making and you guys are doing so looking forward To the next meeting and… + +Piyush Choudhary: Also and… + +Denis Lelic: and everything. eat + +Piyush Choudhary: also in the last minute we discussed to update the deploy and application based on Akash network official website. So as you say that we already did it in around 12 days. It's like on this so we have fun. So from deploy page and there is only Cloud nose. + +Denis Lelic: Yeah, good call out. That's something we discussed previously and piyush was kind enough to remove the console from the deployment page. So we basically have just Cloud models there now, so thanks good call out and thanks for taking care of that. + +Denis Lelic: We'll talk offline and see you next week. Thanks again. + +Tyler Wright: Thank you. + +Piyush Choudhary: Thank you, Vermont. Have a good day. + +Denis Lelic: Thank you, bye-bye. + +Meeting ended after 00:50:33 👋 + 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-events/README.md b/wg-events/README.md index 36ecba29..eb261d49 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 | | | | Coming Soon +| #2 | | | | Coming Soon + +## Lead Adam Wozney (Overclock Labs) diff --git a/wg-crew3/README.md b/wg-zealy/README.md similarity index 58% rename from wg-crew3/README.md rename to wg-zealy/README.md index 6521273f..6e112dc3 100644 --- a/wg-crew3/README.md +++ b/wg-zealy/README.md @@ -1,6 +1,6 @@ -# Akash Network Crew3 Working Group +# Akash Network Zealy 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. +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. @@ -11,6 +11,10 @@ The working group is created to work on the proposal to see what support is need | 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)||| +| #3 | Monday, November 27th, 2023 08:30 AM PT (Pacific Time)||| +| #4 | Friday, December 4th, 2023 08:30 AM PT (Pacific Time)||| +| #4 | Friday, December 11th, 2023 08:30 AM PT (Pacific Time)||| ## Leads 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