| Topic | Presenter(s) | Summary | Duration | Tags | Certification Quiz | Captions |
| ----------------------------------------------------------- | ----------------------------- | ------------------------------------------------------------------------------------ | -------- | --------------------------------------------------------------------------------------- | ------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| How to Organize a Project's Wiki Section in Microsoft Teams | Chris Black and Eric Weathers | Explains protocols for how to populate the Wiki section of a client's Teams channel. | 31:46 | #MicrosoftTeams, #TrainingVideos, #FridayTraining, #Wiki, #Organization, #BestPractices | N/A | Organize Protocols for Teams Wiki_AutoGeneratedCaption.txt |00:00:01.920 --> 00:00:08.758 - What? It's very powerful for like a course integration. 00:00:09.280 --> 00:00:12.784 - Last week's then we can just throw in a car power versus 00:00:12.784 --> 00:00:14.536 - trying to load the whole entire 00:00:14.536 --> 00:00:18.870 - Commerce. Platform onto their side, which could split on their 00:00:18.870 --> 00:00:23.310 - side right? You'd only have to load a module that include those 00:00:23.310 --> 00:00:27.010 - components. Could you still have to have the modular cells 00:00:27.010 --> 00:00:30.710 - instead of just like that? That's another thing is that 00:00:30.710 --> 00:00:35.150 - with how we have angular JS setup currently with DN is it's 00:00:35.150 --> 00:00:38.850 - not a true single edge single page application because we're 00:00:38.850 --> 00:00:42.550 - running it through DNN, so you'll notice that our routing 00:00:42.550 --> 00:00:46.250 - also can interfere with demons routing, right? So that's a 00:00:46.250 --> 00:00:48.840 - whole other thing, so we kind of 00:00:48.840 --> 00:00:53.163 - like. Piggyback on their routing while still having our own 00:00:53.163 --> 00:00:57.970 - routing. And then we're able to put those components, fuel or 00:00:57.970 --> 00:01:01.029 - directives HTML module, so that's pretty interesting. 00:03:03.930 --> 00:03:07.410 - So as we don't notice. 00:03:07.410 --> 00:03:10.947 - Definitely have better sprucing up 'cause I think everybody 00:03:10.947 --> 00:03:15.663 - confused as to what square and what other things go too. So 00:03:15.663 --> 00:03:19.200 - we're doing moving forward is since Microsoft team doesn't 00:03:19.200 --> 00:03:23.523 - have templates like you know office product has Eric and I 00:03:23.523 --> 00:03:28.632 - kind of went through the details of what needs and we took all 00:03:28.632 --> 00:03:33.348 - yalls input as well. Kind of built that out and see what 00:03:33.348 --> 00:03:35.706 - needs to go into a wiki. 00:03:36.250 --> 00:03:40.102 - And this can be mutated going forward if we need to add 00:03:40.102 --> 00:03:43.633 - anything. But this is the basics. And then Eric spent a 00:03:43.633 --> 00:03:47.806 - lot of time actually making this basic one with all of the input 00:03:47.806 --> 00:03:49.411 - yesterday 'cause he's very hard 00:03:49.411 --> 00:03:55.130 - working man. Eric, he weathered the storm now just as a Side 00:03:55.130 --> 00:03:59.924 - Story. Does not show any client specific ones, since we're 00:03:59.924 --> 00:04:01.828 - recording the screen absolutely 00:04:01.828 --> 00:04:05.316 - so. Basically, it's gonna have three different folders or three 00:04:05.316 --> 00:04:08.990 - sets. Honestly, if you don't have a connect portion or Seth 00:04:08.990 --> 00:04:12.998 - portion of a site, or maybe it's moving forward aside from the 00:04:12.998 --> 00:04:16.672 - site, DNA is going to be replaced by Sitefinity and then 00:04:16.672 --> 00:04:20.346 - you wouldn't have the session. Slower connect info just to add 00:04:20.346 --> 00:04:24.020 - confusion. Going to keep that there, but so you'll have your 00:04:24.020 --> 00:04:27.694 - general which everyone will have an end. If you have DNN 00:04:27.694 --> 00:04:31.702 - sitefinity, if not if you have it connect. If you have it 00:04:31.702 --> 00:04:33.038 - pretty pretty basic stuff. 00:04:33.120 --> 00:04:37.164 - So I'm jumping in the first one here. You'll notice that this 00:04:37.164 --> 00:04:40.871 - whole it's marked down, so you can just insert prison whichever 00:04:40.871 --> 00:04:44.915 - you want there. So your first going to have your points of 00:04:44.915 --> 00:04:48.285 - contact. That's for the client. It's pretty basic, just their 00:04:48.285 --> 00:04:52.329 - name, email, and position. Most the time is probably going to be 00:04:52.329 --> 00:04:56.373 - a project manager, or in smaller projects it could be like the 00:04:56.373 --> 00:05:00.754 - CEO or CEO or somebody like that. You could have like a tech 00:05:00.754 --> 00:05:04.798 - guy or gal that you have to work with on the project. 00:05:04.850 --> 00:05:10.020 - So all that's going to go there. Obviously the environments, so 00:05:10.020 --> 00:05:12.370 - where QA, staging and production 00:05:12.370 --> 00:05:17.070 - live. And then you'll notice the user environment URLs are going 00:05:17.070 --> 00:05:21.450 - to be subdomains of clarity client com. We also have a wiki 00:05:21.450 --> 00:05:26.560 - written up on this which we can get into at a later date for 00:05:26.560 --> 00:05:30.940 - setting up a new because we're going to have an SSL certificate 00:05:30.940 --> 00:05:35.320 - that will cover the wild card for all of our subdomains for 00:05:35.320 --> 00:05:39.013 - clarityclient.com. You go, so it's going to. Those are going 00:05:39.013 --> 00:05:43.784 - to be able to run basically in Port 443 type HTTPS running at 00:05:43.784 --> 00:05:48.922 - the end of the day, so there will be set up like that moving 00:05:48.922 --> 00:05:52.592 - forward and then you'll have your username and passwords for 00:05:52.592 --> 00:05:55.895 - those environments and then client server information if if 00:05:55.895 --> 00:05:59.565 - it's applicable. So these are just obviously like examples, so 00:05:59.565 --> 00:06:04.336 - you have your name, which you know the IP to go to, username, 00:06:04.336 --> 00:06:06.538 - password and then the VP info. 00:06:06.560 --> 00:06:10.954 - VPN info would be like you know you notice here there's IP with 00:06:10.954 --> 00:06:15.010 - the support so it could be something like that, or it could 00:06:15.010 --> 00:06:19.404 - be like a specific VPN client that you know a client uses. So 00:06:19.404 --> 00:06:23.798 - like we use sonicwall or some of our previous clients, how to use 00:06:23.798 --> 00:06:28.192 - a specific VPN client to get in there and then you can add 00:06:28.192 --> 00:06:32.586 - anymore of the script that you want. Did you have a question? I 00:06:32.586 --> 00:06:36.642 - was going to say probably linked through the software in the wiki 00:06:36.642 --> 00:06:40.858 - so. So making going to grab it real quick, absolutely. and I 00:06:40.858 --> 00:06:45.034 - can show you how to do that really quick period. There are 00:06:45.034 --> 00:06:48.514 - plans we have that have users with different login information 00:06:48.514 --> 00:06:52.774 - either for. Baby can any of that type of information? How do we 00:06:52.774 --> 00:06:56.662 - handle that? That is exactly what this is, so this is if 00:06:56.662 --> 00:07:00.874 - you're doing RDP, so this would be a client server to RDP into 00:07:00.874 --> 00:07:04.438 - that machine. So you have your IP, username and password that 00:07:04.438 --> 00:07:08.650 - one would use to get into that client and then you or that 00:07:08.650 --> 00:07:12.214 - client server and then you would have your VPN info if 00:07:12.214 --> 00:07:16.755 - applicable. The debate two at the client requires that user 00:07:16.755 --> 00:07:21.405 - specific you don't have those general like clarity client that 00:07:21.405 --> 00:07:23.265 - can get in there. 00:07:23.280 --> 00:07:27.048 - I ate every single person that has access to anything in there. 00:07:27.048 --> 00:07:30.816 - It is client if it's specific to one single person you weren't 00:07:30.816 --> 00:07:33.956 - allowed to share information, what do you do in that 00:07:33.956 --> 00:07:37.724 - situation? I think it would still be applicable to put it or 00:07:37.724 --> 00:07:41.492 - post it in here and still have your username and password. I 00:07:41.492 --> 00:07:45.574 - mean you would just it would be. It would be known that you 00:07:45.574 --> 00:07:49.342 - wouldn't log in as another person. I mean if they if they 00:07:49.342 --> 00:07:53.110 - requested if they requested we don't share it with us that we 00:07:53.110 --> 00:07:56.564 - don't share it, then we won't share it in the wiki. 00:07:56.590 --> 00:08:00.739 - And then so there's going to be miscellaneous credentials. 00:08:00.739 --> 00:08:04.888 - Obviously like user snap, anything like that and then 00:08:04.888 --> 00:08:06.732 - necessary files and links. 00:08:06.740 --> 00:08:09.141 - You kind of get into this I 00:08:09.141 --> 00:08:11.986 - think. These links don't work 00:08:11.986 --> 00:08:15.568 - alright. Like if you go to files 00:08:15.568 --> 00:08:18.480 - right now. Let's do that really sick. 00:08:20.780 --> 00:08:28.180 - Let me let me help with file so. 00:08:30.950 --> 00:08:34.274 - This actually works cool. So what you can do, and whenever we 00:08:34.274 --> 00:08:37.598 - make a link like that, this is really cool markdown syntax, so 00:08:37.598 --> 00:08:40.922 - I can copy link instead of copying link. It'll pop up with 00:08:40.922 --> 00:08:45.077 - the model, so just make sure you get that bit. It will add it to. 00:08:45.077 --> 00:08:47.570 - Your clipboard, will go back over to our wiki. 00:08:48.160 --> 00:08:52.065 - And then for how these links work? Basically, if that wasn't 00:08:52.065 --> 00:08:57.510 - IW. You'll just do a single bracker double brackets like an 00:08:57.510 --> 00:09:02.850 - array or just hard brackets for pins, and then you will have 00:09:02.850 --> 00:09:07.300 - your open parentheses and then paste your Lincoln and then 00:09:07.300 --> 00:09:09.525 - close parentheses. I think you 00:09:09.525 --> 00:09:14.258 - just. Backspace and then you know not all the way, in any 00:09:14.258 --> 00:09:15.422 - type of game. 00:09:15.430 --> 00:09:20.220 - Well, that's better than no, no. You have to space. 00:09:20.720 --> 00:09:27.879 - Yep. Perfect, but anyway, you'll notice since I made my 00:09:27.879 --> 00:09:30.684 - link, if I click here. 00:09:32.220 --> 00:09:36.372 - I hope you're actually. If I click here it'll it'll take me 00:09:36.372 --> 00:09:40.870 - to my file, it download it for me, which is really cool. So 00:09:40.870 --> 00:09:45.368 - that's been and will move on to another section. Will have a lot 00:09:45.368 --> 00:09:50.212 - more of these links, but if you want a link to not be complete 00:09:50.212 --> 00:09:54.018 - like crazy, you are I or whatever encoded stuff you can 00:09:54.018 --> 00:09:55.748 - just make it that way. 00:09:56.300 --> 00:09:57.710 - Hum. 00:09:59.020 --> 00:10:01.462 - And then moving onto the set 00:10:01.462 --> 00:10:04.790 - info. Here in a minute. 00:10:05.580 --> 00:10:09.376 - Alright cool so um all the basic information is also going to be 00:10:09.376 --> 00:10:13.464 - here. I mean this is all the stuff I think is pretty much no 00:10:13.464 --> 00:10:16.092 - brainer, but obviously we want to have everything very 00:10:16.092 --> 00:10:19.888 - structured and we want every Devon every PM to be able to hit 00:10:19.888 --> 00:10:24.268 - all these every time. So I think a lot of us came up with that. 00:10:24.268 --> 00:10:28.064 - Great so with the clone URL it's obviously going to be the clone 00:10:28.064 --> 00:10:32.444 - URL for stuff info so I can just go here and click that link. It 00:10:32.444 --> 00:10:36.532 - will take me to it and then I can just get cloned whatever I 00:10:36.532 --> 00:10:37.700 - want. Same syntax. Square 00:10:37.700 --> 00:10:41.720 - bracket. Past the Lincoln or past. The name of the Lincoln 00:10:41.720 --> 00:10:46.491 - and then the Prince season. Pass to link in there and then. These 00:10:46.491 --> 00:10:50.161 - would be linked to the different branches. Obviously would be 00:10:50.161 --> 00:10:53.464 - what we talked about before with support clients. Client 00:10:53.464 --> 00:10:57.501 - abbreviation or acronym. I should say in the QA, staging or 00:10:57.501 --> 00:11:01.905 - prod moving down to the database information. This is going to be 00:11:01.905 --> 00:11:05.208 - the environment name, the hosting location and then the 00:11:05.208 --> 00:11:08.878 - actual database name, so there's no more guessing on that. 00:11:08.920 --> 00:11:12.720 - And I change this one. I've actually improving this into 00:11:12.720 --> 00:11:17.187 - like I. Having the username and password in here is 12. I added 00:11:17.187 --> 00:11:18.872 - to calling for username and 00:11:18.872 --> 00:11:24.040 - password. Yet but after hosting location and TV name will be 00:11:24.040 --> 00:11:26.455 - username, password to get into 00:11:26.455 --> 00:11:30.492 - that. Hey, uh, so yeah, you can just basically open up file, 00:11:30.492 --> 00:11:34.034 - share and steal your DOT pack file whenever you're setting the 00:11:34.034 --> 00:11:37.254 - local environment just based off these names, they're going to 00:11:37.254 --> 00:11:40.474 - beacon of truth. Obviously if anything ever changes for any 00:11:40.474 --> 00:11:44.338 - kind of Configs or anything like that, or if like, say, some 00:11:44.338 --> 00:11:48.524 - crazy event happens and you know we have to change the clone URL. 00:11:48.524 --> 00:11:51.744 - Obviously whoever does that wants to update this wiki, so 00:11:51.744 --> 00:11:55.930 - it's still the beacon of truth. Same thing goes for DB names or 00:11:55.930 --> 00:11:59.624 - anything like that. We're going to list posting info. You know 00:11:59.624 --> 00:12:03.620 - this would be if it's on, you know, Azure or something like 00:12:03.620 --> 00:12:07.616 - that. Or maybe it doesn't have like an on Prem database that 00:12:07.616 --> 00:12:11.612 - you're hosting it out of Azure like for the database. Or if 00:12:11.612 --> 00:12:15.275 - it's an app service, whichever you obviously want to post that 00:12:15.275 --> 00:12:18.605 - information here and then, this is all your basic information 00:12:18.605 --> 00:12:22.934 - and I think another huge thing is like what set version is this 00:12:22.934 --> 00:12:27.263 - client on. So not only that this is going to be the bootstrap 00:12:27.263 --> 00:12:30.794 - versions for stuff. We know that the front end thing, but 00:12:30.794 --> 00:12:33.611 - obviously how stuff is structures that's going to be, 00:12:33.611 --> 00:12:37.054 - you know, very much entrenched with stuff. Since it's a project 00:12:37.054 --> 00:12:40.810 - in it, so that's going to be here as well. Enabled providers 00:12:40.810 --> 00:12:44.566 - that are going to be in app settings config, so UPS great. 00:12:44.600 --> 00:12:48.417 - You know, taxing you know all your providers there John. So 00:12:48.417 --> 00:12:51.540 - then you'll have your primary deployment. Does your secondary 00:12:51.540 --> 00:12:55.357 - deployment dev tickets will be obviously given to the Devs by 00:12:55.357 --> 00:12:58.827 - the PMS for those and then the internal project manager. 00:12:58.827 --> 00:13:02.991 - Obviously these are no brainers, but we just want to put it 00:13:02.991 --> 00:13:07.155 - there. So if somebody just got on boarded or just got thrown 00:13:07.155 --> 00:13:10.972 - into the project or something crazy happens, you have all the 00:13:10.972 --> 00:13:14.789 - information and you don't need to go to anybody to ask 00:13:14.789 --> 00:13:19.610 - questions. And then all the testing credentials. You know 00:13:19.610 --> 00:13:22.670 - four stuff, so you have like 00:13:22.670 --> 00:13:25.940 - generally. You know environment name, description and then your 00:13:25.940 --> 00:13:29.390 - username. So with the current clients with different kind of 00:13:29.390 --> 00:13:34.220 - users you would want to say hey this is a user with admin rights 00:13:34.220 --> 00:13:38.705 - or this is a user with just steps user rights or if they 00:13:38.705 --> 00:13:42.500 - have specific client user roles you put that information here as 00:13:42.500 --> 00:13:45.687 - well. And then other testing information. So just you know 00:13:45.687 --> 00:13:48.817 - successful credit card declined credit card address to test tax 00:13:48.817 --> 00:13:51.634 - rates. All that good stuff, unnecessary files that you're 00:13:51.634 --> 00:13:55.703 - going to have to have. So yeah, all this stuff is really great. 00:13:55.703 --> 00:14:00.398 - Or like if you have to have like some kind of like you know PDF 00:14:00.398 --> 00:14:03.841 - or something whenever you click on a link to get something 00:14:03.841 --> 00:14:07.284 - that's going to obviously be here and then as we discussed, 00:14:07.284 --> 00:14:11.979 - those will be in the files and then this is going to be a link 00:14:11.979 --> 00:14:13.231 - to the file so. 00:14:13.240 --> 00:14:19.612 - Go search. Link to website that has any link wherever you 00:14:19.612 --> 00:14:24.540 - want to go into any kind of information that you want. 00:14:24.540 --> 00:14:26.332 - People with resources anywhere. 00:14:26.350 --> 00:14:32.002 - Now, one thing which one something like really bloated. 00:14:32.010 --> 00:14:36.091 - Is when people look like a paragraph of how to test 00:14:36.091 --> 00:14:40.543 - something. If that's the case, we will create a text file or 00:14:40.543 --> 00:14:45.366 - dot file in the files and put other testing info like how to 00:14:45.366 --> 00:14:50.560 - put a member roll on a user or whatever and link that link that 00:14:50.560 --> 00:14:55.012 - file so that if they click which description on there rather than 00:14:55.012 --> 00:14:56.867 - looking to scrolling through a 00:14:56.867 --> 00:15:02.982 - wiki. I have any on how to do something, sure. 00:15:02.990 --> 00:15:08.048 - Yes. Yeah I would. I would say Let's not have to meet other 00:15:08.048 --> 00:15:09.966 - tabs going in the wiki. I would 00:15:09.966 --> 00:15:15.656 - just do. What is scription? I just know that there's a lot of 00:15:15.656 --> 00:15:19.384 - clients that do have very specific information, specific 00:15:19.384 --> 00:15:24.510 - roles that specific attributes that you have to have this field 00:15:24.510 --> 00:15:25.908 - that they've defined. 00:15:25.940 --> 00:15:30.032 - You think that would you speak something that you put into a 00:15:30.032 --> 00:15:31.737 - file at means there, yeah, 00:15:31.737 --> 00:15:35.858 - right. Fields that need to be said. You could put it in like 00:15:35.858 --> 00:15:39.312 - extra info or you know basic import, whatever. What do you 00:15:39.312 --> 00:15:44.873 - mean like? I need not to call out specific clients, but if you 00:15:44.873 --> 00:15:46.888 - have any turns code that. 00:15:47.590 --> 00:15:53.024 - Dictate what type of payments you're allowed to do. Sure, go 00:15:53.024 --> 00:15:56.892 - back. Under like there for that, if you Scroll down to live with 00:15:56.892 --> 00:15:59.702 - this testing, credit cards are everything. So there I spent 00:15:59.702 --> 00:16:03.355 - like address to test tax rate. So in there you could say net 00:16:03.355 --> 00:16:07.008 - terms that have to be you know or whatever needs to be like. 00:16:07.030 --> 00:16:10.399 - Codes for whatever. 00:16:10.400 --> 00:16:14.720 - There's also the information. Sometimes they need to add in 00:16:14.720 --> 00:16:19.040 - who made the payment for their specific peo number, first 00:16:19.040 --> 00:16:24.224 - restrictions, or if there are. If you need to make sure you 00:16:24.224 --> 00:16:28.976 - include a email with all a CHP like there's some specific 00:16:28.976 --> 00:16:33.286 - things. Go to downloads into a file. Yeah, if it's like if it's 00:16:33.286 --> 00:16:36.193 - like required things for connecting or required things to 00:16:36.193 --> 00:16:40.069 - create a customer. Yeah I would. I would do the necessary files 00:16:40.069 --> 00:16:43.945 - and direction and put it in files. Yeah, we don't want to 00:16:43.945 --> 00:16:48.144 - blow this up with too many sections. We want to be as I 00:16:48.144 --> 00:16:52.666 - just can see how this could be a lot of information so sure. Well 00:16:52.666 --> 00:16:56.219 - it's going to be a lot of information no matter what. 00:16:56.260 --> 00:17:01.129 - Allowing it to link with its smaller windows short 00:17:01.129 --> 00:17:06.490 - description. Sure. Yeah, well, I think I think this is this is 00:17:06.490 --> 00:17:09.735 - the start of a solution to something we don't have already, 00:17:09.735 --> 00:17:12.980 - so I think this is like structuring. You know our wikis 00:17:12.980 --> 00:17:16.520 - that you know we don't have all this information. You know in 00:17:16.520 --> 00:17:21.717 - current teams. I know we spoke briefly about the like the 00:17:21.717 --> 00:17:24.960 - stuff. Uh. 00:17:24.960 --> 00:17:31.430 - App settings. Well, not like the solution areas. No, it's the in 00:17:31.430 --> 00:17:33.670 - the configuration file like the 00:17:33.670 --> 00:17:39.420 - specific. Except config dot. Here's something that we haven't 00:17:39.420 --> 00:17:42.270 - gotten there yet. OK, yeah. 00:17:42.270 --> 00:17:45.298 - That's the stuff configurations. 00:17:45.300 --> 00:17:48.516 - I skipped it because I don't think we had that table in 00:17:48.516 --> 00:17:52.536 - there, but I will. I was going to hit it on this one. Yeah, so 00:17:52.536 --> 00:17:55.752 - basically this will be links not just to the folder, but you'll 00:17:55.752 --> 00:17:58.968 - upload all your files like we did with that one app settings 00:17:58.968 --> 00:18:02.184 - config earlier and then you'll link him here in this table so 00:18:02.184 --> 00:18:05.400 - the stuff config files will be here and then all of your. 00:18:05.430 --> 00:18:09.582 - Front end like Sept stuff will be in the DNA inside since 00:18:09.582 --> 00:18:10.966 - that's where those go. 00:18:10.970 --> 00:18:14.520 - It makes a change to the responsible for updating the 00:18:14.520 --> 00:18:18.425 - file and teams, and you could have one 428 staging and 00:18:18.425 --> 00:18:21.265 - production with necessary Christian Eric, y'all. See what 00:18:21.265 --> 00:18:24.815 - their schedule is like and they literally put this core 00:18:24.815 --> 00:18:28.720 - structure in place. There will be some things that like this 00:18:28.720 --> 00:18:32.625 - will need to explore together what you're proposing for now is 00:18:32.625 --> 00:18:37.240 - to do this, but I think Garrett and James both have brought up 00:18:37.240 --> 00:18:41.145 - some really good points that will have to dig into more. 00:18:41.200 --> 00:18:46.117 - And possibly iterate on, but for now this is the proposed 00:18:46.117 --> 00:18:51.034 - solution and then based on feedback and it sounds like my 00:18:51.034 --> 00:18:54.610 - husband immediately back and just validating the suggestions 00:18:54.610 --> 00:18:56.845 - that we get for alternative 00:18:56.845 --> 00:19:01.370 - solutions. Big wiki actually. I did break it out into separate 00:19:01.370 --> 00:19:05.534 - ones in. Look, we know. So if you know find it, you can 00:19:05.534 --> 00:19:09.486 - comment on there and we can have a discussion on their of what 00:19:09.486 --> 00:19:13.134 - looks good and what does it. That way involved in one place 00:19:13.134 --> 00:19:16.782 - and we can look to make any changes necessary. Not post that 00:19:16.782 --> 00:19:22.216 - week after. The big thing, but I think if we. 00:19:22.220 --> 00:19:25.260 - Something like that in the future. You obviously would have 00:19:25.260 --> 00:19:28.604 - all this changes, but you know obviously if you make changes 00:19:28.604 --> 00:19:32.252 - yourself, you want to do a probably a win merge to make 00:19:32.252 --> 00:19:35.596 - sure you're not going to. You know 86 somebody elses changes 00:19:35.596 --> 00:19:39.244 - and then only bring up yours. Yeah 'cause then stuff will be 00:19:39.244 --> 00:19:42.892 - broken. That would be nice and let me jump in with another 00:19:42.892 --> 00:19:45.932 - comment slash question. Did you guys go through the files 00:19:45.932 --> 00:19:50.188 - portion of this at all? Just out of curiosity I just want to make 00:19:50.188 --> 00:19:53.532 - sure that the files section in if there's a separate project 00:19:53.532 --> 00:19:55.052 - where we've been housing that 00:19:55.052 --> 00:19:58.793 - template. Let me know, but we ought to just make this our 00:19:58.793 --> 00:20:02.126 - default and put those files because we have a really nice 00:20:02.126 --> 00:20:05.459 - folder structure that it sounds like VM team put into place. 00:20:05.510 --> 00:20:08.720 - File share, so 00:20:08.720 --> 00:20:14.352 - yeah yeah. There's a template, alright, so the DM stuff is 00:20:14.352 --> 00:20:18.620 - pretty much on face with the stuff info. You'll notice that 00:20:18.620 --> 00:20:22.500 - there's just a couple of different fields here, so Dean 00:20:22.500 --> 00:20:26.768 - Inversion. Obviously we're going to have same devs on here as 00:20:26.768 --> 00:20:31.424 - well. Config file so that will be your web configs and then 00:20:31.424 --> 00:20:35.692 - your typescript configs and all that good stuff there and then 00:20:35.692 --> 00:20:40.736 - your list of desktop modules and then these links are going to be 00:20:40.736 --> 00:20:42.288 - to the zip files. 00:20:42.290 --> 00:20:46.742 - Uhm, and then we can. Also, you know, throw in like a version or 00:20:46.742 --> 00:20:50.240 - something like that so that we could get confused. But we're 00:20:50.240 --> 00:20:54.374 - going to have to zip files in the file structure as well, so 00:20:54.374 --> 00:20:58.508 - it will Lincoln Beach. That zip of the module used for the sites 00:20:58.508 --> 00:21:01.688 - moving forward. And obviously in practice you probably won't have 00:21:01.688 --> 00:21:04.550 - different versions of dev staging and it would probably 00:21:04.550 --> 00:21:09.002 - get it if we can for the DM modulus how to log into the 00:21:09.002 --> 00:21:11.864 - developer site if it's applicable? Sure, so you might 00:21:11.864 --> 00:21:14.090 - want to have a column for that 00:21:14.090 --> 00:21:16.280 - or. A couple of columns to make 00:21:16.280 --> 00:21:22.280 - a note. Camping came into my account and make that little so 00:21:22.280 --> 00:21:23.738 - we also suggest. 00:21:23.750 --> 00:21:28.339 - On the very top for the unit has a child expiration date. I've 00:21:28.339 --> 00:21:32.222 - been. Yeah, I've been putting that. Yeah, but yeah, yeah I 00:21:32.222 --> 00:21:36.458 - just I shelving like everywhere. I don't see how it can spice 00:21:36.458 --> 00:21:38.720 - inside. Very bad. 00:21:38.720 --> 00:21:41.640 - That's another number then. 00:21:41.640 --> 00:21:47.950 - Site login Look at what the expiration advent of 00:21:47.950 --> 00:21:54.000 - very top of everything, and I was encouraged by reminders on 00:21:54.000 --> 00:21:55.670 - your calendars. Sport. 00:21:56.470 --> 00:22:01.215 - I'm already in the last one is something I know so much about 00:22:01.215 --> 00:22:03.405 - since I'm back in developer is 00:22:03.405 --> 00:22:09.710 - connect. And basically it's just all the same information here is 00:22:09.710 --> 00:22:14.579 - that your Rico information obviously goes to that. Connect 00:22:14.579 --> 00:22:20.530 - jobs can be a separate repo. All the different branches, their 00:22:20.530 --> 00:22:24.858 - database information, posting info, basic info, config files, 00:22:24.858 --> 00:22:28.000 - WooCommerce credentials. Where? 00:22:28.000 --> 00:22:29.370 - My foot. 00:22:30.520 --> 00:22:34.924 - You're talking about wanting to do like like your P login stuff 00:22:34.924 --> 00:22:40.620 - like that. Yes, that means to happen for you to be able to 00:22:40.620 --> 00:22:42.420 - gain access or position. 00:22:42.430 --> 00:22:46.473 - Sure, so I would do that. May be here. So like say WooCommerce 00:22:46.473 --> 00:22:49.583 - credentials to say you got your URL. Your consumer Keenan? 00:22:49.590 --> 00:22:55.358 - Requires you to be on this VPN during this time of day and make 00:22:55.358 --> 00:22:59.890 - sure you're standing on your left foot. Put that into a 00:22:59.890 --> 00:23:02.710 - fiber. Secondary. 00:23:02.710 --> 00:23:08.744 - Under 8. You could do like URL, consumer key, consumer 00:23:08.744 --> 00:23:12.416 - secret login steps and then link through the instruction. 00:23:13.030 --> 00:23:17.775 - I had, I think a very important question. We need to ask is 00:23:17.775 --> 00:23:19.235 - who's responsible for updating? 00:23:19.240 --> 00:23:23.972 - Weather change, so that's that's part of like CB. My job is. It's 00:23:23.972 --> 00:23:28.704 - not going to be as regularly is probably it should be, you know, 00:23:28.704 --> 00:23:32.344 - based on our bandwidth. Let's let's talk about it though. 00:23:32.344 --> 00:23:36.712 - 'cause That's a good question. Should we also say the PM as 00:23:36.712 --> 00:23:40.716 - well? And then maybe should we deputize a team member? That's 00:23:40.716 --> 00:23:45.812 - like you guys in the PM are the default, but there is a team 00:23:45.812 --> 00:23:50.180 - member who's deputized. And then we can give him a shellac. I 00:23:50.180 --> 00:23:53.460 - mean, feedback. Good job. 00:23:53.460 --> 00:23:58.062 - Our job to do an audit of this regularly. Yeah, we're not gonna 00:23:58.062 --> 00:24:01.602 - be able to catch every little thing for every project. 00:24:01.620 --> 00:24:04.650 - Regular regular yeah, let's deputize a team member and then 00:24:04.650 --> 00:24:09.195 - we can put their name at the top of it and then everyone can give 00:24:09.195 --> 00:24:11.316 - 'em stink eye. If they do about 00:24:11.316 --> 00:24:16.690 - you. I thought we could put the last touch date down too. 00:24:16.700 --> 00:24:19.988 - Patrick MM Garrett think 00:24:19.988 --> 00:24:23.989 - Patrick? Location like this that we could have a like a history 00:24:23.989 --> 00:24:27.168 - or sort of tracking 'cause I've seen were like somebody acting 00:24:27.168 --> 00:24:31.214 - waves in the whole entire thing. And how do you know? How do you 00:24:31.214 --> 00:24:34.971 - get to it other than through share point? But it does have a 00:24:34.971 --> 00:24:36.127 - history or got it? 00:24:36.660 --> 00:24:42.094 - I I feel like a better ways of doing that instead of deputising 00:24:42.094 --> 00:24:44.184 - one person for an entire 00:24:44.184 --> 00:24:49.014 - project. Would be to me, they go through each individual part and 00:24:49.014 --> 00:24:53.262 - say what could be updated by PM. What could it be updated? 00:24:53.450 --> 00:24:57.674 - Dinner and then the primary front end or back after on each 00:24:57.674 --> 00:25:01.546 - of these projects would then be responsible for those parts of 00:25:01.546 --> 00:25:05.770 - the project. I'm not opposed to that, but I want someone's next 00:25:05.770 --> 00:25:06.826 - touring or someone. 00:25:06.830 --> 00:25:10.862 - Either way, 'cause ideally when we set up the project it gets 00:25:10.862 --> 00:25:14.558 - set up really well and that's something that should be pretty 00:25:14.558 --> 00:25:19.262 - easy to do. But then as we go along, it's all the Devils in 00:25:19.262 --> 00:25:22.286 - the details with us, with policing and properly and 00:25:22.286 --> 00:25:26.318 - managing it. And it really will make a difference, having it be 00:25:26.318 --> 00:25:29.678 - really nice. I mean that will increase morale for everyone 00:25:29.678 --> 00:25:33.710 - here, right? I mean, it might be fairly significant. This is a 00:25:33.710 --> 00:25:36.398 - big source of frustration and it's just silly. 00:25:36.410 --> 00:25:39.090 - So ultimately my theory would 00:25:39.090 --> 00:25:42.937 - be. Number one, everyone can voice their concerns. I don't 00:25:42.937 --> 00:25:46.270 - think that we're going to know, even regardless of how strong 00:25:46.270 --> 00:25:49.300 - different folks opinions might be, we will not know was 00:25:49.300 --> 00:25:52.936 - absolutely going to be the best way to handle this. OK, let's 00:25:52.936 --> 00:25:56.875 - just agree that that's the fact I don't know the answer and I 00:25:56.875 --> 00:26:00.814 - would suggest that no one here does. We need to kind of test 00:26:00.814 --> 00:26:05.056 - this and see if it works so we could also take a couple of 00:26:05.056 --> 00:26:08.389 - projects and do the police method where you have one person 00:26:08.389 --> 00:26:12.862 - who owns it. And then they kind of work with different team 00:26:12.862 --> 00:26:16.798 - members and then we could have a couple projects where we have 00:26:16.798 --> 00:26:19.750 - multiple people owning their sections and see what wins. 00:26:20.300 --> 00:26:24.525 - I am responsible for it. That doesn't mean that I have to know 00:26:24.525 --> 00:26:28.425 - it all. It means that I would collaborate with people that you 00:26:28.425 --> 00:26:33.291 - know it. The other thing that's to me that's going to happen is 00:26:33.291 --> 00:26:39.006 - if that person is not doing a good job. That to me would go up 00:26:39.006 --> 00:26:43.578 - to Eric and Chris Daniels rolls and then we would just politely 00:26:43.578 --> 00:26:48.912 - ask them to kind of step aside. and I mean, make sure if you're 00:26:48.912 --> 00:26:50.055 - making that commitment. 00:26:50.090 --> 00:26:53.951 - Yeah, make sure if you're making that commitment that you're that 00:26:53.951 --> 00:26:57.461 - you're serious about it, but we need everyone to participate. 00:26:57.461 --> 00:27:02.024 - and I don't mean it to sound so negative. It is a key 00:27:02.024 --> 00:27:06.474 - responsibility though. Yeah, I was gonna say already notice. 00:27:06.480 --> 00:27:11.563 - Lenin event I was gonna say Um I've taken a couple minutes for 00:27:11.563 --> 00:27:15.864 - a couple different projects and have updated on to like this 00:27:15.864 --> 00:27:19.383 - standard which I've asked for using tables and everything 00:27:19.383 --> 00:27:20.556 - 'cause it's visually. 00:27:21.130 --> 00:27:25.090 - Doing everything it was it. It allows you to find information 00:27:25.090 --> 00:27:26.530 - with it anyways, um. 00:27:27.120 --> 00:27:30.936 - The the dev that touching it usually knows what's up to date 00:27:30.936 --> 00:27:35.388 - and if you just spend that time a little bit extra time in Czech 00:27:35.388 --> 00:27:39.204 - something it's not up to date and just update it real quick. 00:27:39.204 --> 00:27:43.020 - That makes the most sense, you know. So the other thing that 00:27:43.020 --> 00:27:46.836 - I'll point out is there probably will be some mistakes. That is 00:27:46.836 --> 00:27:50.970 - OK. OK guys, let's just relax, it's OK. Let's do our best and 00:27:50.970 --> 00:27:55.104 - one of the things that I can tell you is my perspective. This 00:27:55.104 --> 00:27:57.330 - is way better than what we have. 00:27:57.400 --> 00:28:01.756 - OK, the other thing that person who's the kind of police or 00:28:01.756 --> 00:28:05.386 - person or whatever deputized or whatever they can probably go 00:28:05.386 --> 00:28:09.742 - through a quick little thing so they can see what history of 00:28:09.742 --> 00:28:13.009 - what's changed in just occasionally. Go check it and 00:28:13.009 --> 00:28:16.276 - make sure that something hasn't broken. Typically is something's 00:28:16.276 --> 00:28:20.269 - broken. Someone's going to say something and like I said, You 00:28:20.269 --> 00:28:22.084 - know, share that feedback, also 00:28:22.084 --> 00:28:28.868 - known as. And then teams or individually or whatever. 00:28:28.870 --> 00:28:32.485 - The very top of the 00:28:32.485 --> 00:28:36.345 - owner. Yeah, but it fell through 00:28:36.345 --> 00:28:42.536 - PM project. And they write last touched on the 13th. 00:28:43.120 --> 00:28:48.760 - And then during our weekly would be checked in here the more 00:28:48.760 --> 00:28:51.290 - projects. Right, right? 00:28:51.290 --> 00:28:57.890 - Check the wiki changed on their wiki for 00:28:57.890 --> 00:29:01.190 - master graphics in 2018. 00:29:01.200 --> 00:29:06.513 - OK there, yeah log into all the same. It's all good. 00:29:07.300 --> 00:29:10.740 - That provides for us 00:29:10.740 --> 00:29:15.407 - at management. That layer of accountability, Dino with how 00:29:15.407 --> 00:29:20.459 - much work every single person in this room done all the time. 00:29:20.459 --> 00:29:21.722 - It's very easy. 00:29:21.730 --> 00:29:26.500 - That that seems that the Eric. Or did I put it in the wiki page 00:29:26.500 --> 00:29:28.726 - that I just write that down on 00:29:28.726 --> 00:29:29.680 - scrap of paper? 00:29:29.690 --> 00:29:37.314 - Program. Yeah, and we need that. I need that 00:29:37.314 --> 00:29:38.928 - I didn't do. 00:29:38.930 --> 00:29:42.890 - I'm sorry just looking like it's also like. I think it's also 00:29:42.890 --> 00:29:46.520 - beneficial, like if you find something is not correct on the 00:29:46.520 --> 00:29:50.480 - wiki like please fix it, but you don't tell anybody just like. 00:29:50.480 --> 00:29:53.290 - Market like hey visiting Craig like striking hours. They put 00:29:53.290 --> 00:29:56.943 - some markup on it. Just strike it out so that we just pulled 00:29:56.943 --> 00:30:00.700 - away. Oh, I know Christians like looking through his testing is 00:30:00.700 --> 00:30:02.776 - like Yeah 50 log is mental. 00:30:02.790 --> 00:30:07.088 - So what I don't want to have happen is I don't want anyone in 00:30:07.088 --> 00:30:11.079 - here to hesitate to go update the wiki. If you know that it 00:30:11.079 --> 00:30:14.763 - needs to be updated. OK, if somebody is giving you flak over 00:30:14.763 --> 00:30:18.447 - that, please come, please allow them to review that with me if 00:30:18.447 --> 00:30:21.546 - you. Just one 00:30:21.546 --> 00:30:26.781 - person. Like this person is the manager of this and they will 00:30:26.781 --> 00:30:30.753 - come down on you if you didn't update your stuff like you're 00:30:30.753 --> 00:30:32.739 - still at the dev responsible for 00:30:32.739 --> 00:30:35.170 - updating fasting. Responsible for a pinpoint contact 00:30:35.170 --> 00:30:39.042 - information? You're still as a front end out of responsible for 00:30:39.042 --> 00:30:42.210 - updating CNN version or whatever. Whatever it is it 00:30:42.210 --> 00:30:45.730 - still your responsibility. We just have one major person that. 00:30:46.270 --> 00:30:50.380 - Check to make sure that everything is there, love it, 00:30:50.380 --> 00:30:52.846 - and let's see how it goes. 00:30:52.850 --> 00:30:56.612 - And we can add that there's Corps or some other integration 00:30:56.612 --> 00:31:00.716 - or implementation if we can add in like a little white listed 00:31:00.716 --> 00:31:05.504 - URLs. But to be added, or if they make that as well for them, 00:31:05.504 --> 00:31:08.924 - definitely, I think that would mostly be enough settings config 00:31:08.924 --> 00:31:12.686 - which was already being there, but we could definitely had a 00:31:12.686 --> 00:31:17.530 - separate. We could also add that in movies definitely not able. 00:31:17.530 --> 00:31:21.790 - Do any request to put any kind of information into this? Yeah 00:31:21.790 --> 00:31:24.985 - yeah, if you need to put something in there. 00:31:24.990 --> 00:31:27.834 - You don't have to work, it starts to be a situation where 00:31:27.834 --> 00:31:29.493 - it's like we need to add some 00:31:29.493 --> 00:31:34.408 - more tabs. Um, that's fine by me. Yeah, I think the idea is 00:31:34.408 --> 00:31:38.346 - we're trying to keep it all within these tabs or pages 00:31:38.346 --> 00:31:42.284 - were over there called. We're trying to keep it within these 00:31:42.284 --> 00:31:45.148 - pages specifically so that it doesn't become unstandardized 00:31:45.148 --> 00:31:46.580 - storage of the information.