WEBVTT 00:00:00.000 --> 00:00:09.560 All right, welcome everyone. We do have a quorum present, so I call this meeting of 00:00:09.560 --> 00:00:21.560 the Denton Code Review Committee to order at 1110 on October 19, 2020. I'm going to 00:00:21.560 --> 00:00:25.840 go ahead and because there's one presentation for all these items, I'm going to open all 00:00:25.840 --> 00:00:33.160 the items so that we can kind of interconnect between them. Item A is introduction of the 00:00:33.160 --> 00:00:40.360 Development Code Review Committee and key staff members. Item B, receive a report, hold 00:00:40.360 --> 00:00:48.040 a discussion on the objective of the Development Code Review Committee. Item C, receive a report, 00:00:48.040 --> 00:00:52.380 hold a discussion and give staff direction regarding future Development Code Review Committee 00:00:52.380 --> 00:00:59.640 meeting schedule and item D, receive a report and hold an overview discussion of proposed 00:00:59.640 --> 00:01:05.680 code amendments. Ron, it's all yours. Thank you, Chair. I'm going to start the presentation 00:01:05.680 --> 00:01:14.680 and once I have it up, Scott will go ahead and start the introduction. So give me a second 00:01:14.680 --> 00:01:26.640 here. Okay, I'm turning it over back to Scott. Good morning. I'm Scott McDonnell. I'm the 00:01:26.640 --> 00:01:32.680 Director of Development Services. Glad to be here this morning. Today we're beginning 00:01:32.680 --> 00:01:39.680 the process to review amendments to the 2019 Denton Development Code. In the process of 00:01:39.680 --> 00:01:45.080 doing this, we're going to utilize the Development Code Review Committee, which is made up of 00:01:45.080 --> 00:01:52.440 three of our council members and three of our P&Z commissioners. John Ryan is the Chair, 00:01:52.440 --> 00:02:00.720 Keely Briggs, Vice Chair, Chris Watts, and Andrew Rozell from the Planning Zoning Commission, 00:02:00.720 --> 00:02:05.440 Margie Ellis, and I'd like to welcome Mr. Tim Smith. He is new to the committee. All 00:02:05.440 --> 00:02:11.200 of the previous members served when we went through the process of going from the 2002 00:02:11.200 --> 00:02:19.040 to the 2019. Our goal in this is really just as we've used this for over a year now, we've 00:02:19.040 --> 00:02:24.600 got a good flavor for what's working, what's not. We've got some non-conformities. Ron 00:02:24.600 --> 00:02:30.240 will kind of take us through that. I'd also like to mention we have several staff members 00:02:30.240 --> 00:02:36.760 on the call, some of those being our Planning Director, Richard Canone. Ron, as you'll be 00:02:36.760 --> 00:02:44.360 introducing himself shortly, we have our City Engineer, Becky Davini, Ken Schmidt, and I 00:02:44.360 --> 00:02:49.600 don't know if you can see these faces, but certainly if you can, you can wave, and Ken 00:02:49.600 --> 00:02:55.720 Schmidt is our Development Facilitation Manager. All of these folks have been working through 00:02:55.720 --> 00:03:04.880 and using the code. Our City Attorney is also on the call, Erin Leal, Cynthia Kirchhoff. 00:03:04.880 --> 00:03:10.800 And then I'd like to introduce, we have two new staff members who are working on staff's 00:03:10.800 --> 00:03:16.740 behalf. Planning staff as well as legal staff need a little bit of augmentation as we go 00:03:16.740 --> 00:03:23.840 through this. We have worked through with Borges Law Firm, and we have Robin and Christian, 00:03:23.840 --> 00:03:29.160 which I'm going to allow them to introduce theirself to just help us with best practices 00:03:29.160 --> 00:03:35.020 as we review what we have, where we're going, and what some other municipalities are doing. 00:03:35.020 --> 00:03:37.200 And if you don't mind, I'd like to start with Robin. 00:03:37.200 --> 00:03:43.720 Hey, my name's Robin Miga. I've been a planner for about six years. Most of that time was 00:03:43.720 --> 00:03:48.720 spent on staff with the city. Most recently, I did join the Borges Law Firm, where I serve 00:03:48.720 --> 00:03:52.520 as a planner, and I've been doing this for about two years. I've worked with some of 00:03:52.520 --> 00:03:57.880 the fastest growing cities in Texas, so I have a lot of experience with trying to figure 00:03:57.880 --> 00:04:03.520 out how we're maneuvering through new UDCs and best practices. Christian? 00:04:03.520 --> 00:04:08.520 Good morning. My name's Christian Rosas. I'm one of the attorneys here at the Borges Law 00:04:08.520 --> 00:04:15.120 Firm. I've been practicing municipal law for about seven years. I work at the Office of 00:04:15.120 --> 00:04:21.000 the Attorney General, and also as an Assistant City Attorney with the City of Laredo. At 00:04:21.000 --> 00:04:24.800 the Borges Law Firm, we've helped a lot of municipalities like Battlestrop and Dripping 00:04:24.800 --> 00:04:32.900 Springs review and revamp their development code, so I'm excited to be part of the team. 00:04:32.900 --> 00:04:36.960 Thank you both. Thank you both for being here. While we've got the faces up, I think I may 00:04:36.960 --> 00:04:41.600 just run back through the introduction so people know names with faces. And I'd also 00:04:41.600 --> 00:04:46.760 like to mention Sarah Hensley, our Deputy City Manager, is also on the call and ultimately 00:04:46.760 --> 00:04:52.800 responsible for the work that we do in development services. So thank you, Sarah, for joining 00:04:52.800 --> 00:05:13.560 us. Again, the Chair is Mr. John Ryan, Berkele Briggs, Mayor Chris Watts, Andrew Rosell, 00:05:13.560 --> 00:05:23.980 Commissioner Marge Ellis, and Commissioner Tim Smith. Anyone else that'd like to say 00:05:23.980 --> 00:05:30.680 anything else? If not, I'll let Ron take over and run through, or I guess I have maybe one 00:05:30.680 --> 00:05:51.440 more slide, I'm sorry. I'm pulling it up for you, Scott. Thank you. Okay, so the objective 00:05:51.440 --> 00:05:59.480 of the Development Code Review Committee, DCRC, is that we're looking to get counsel 00:05:59.480 --> 00:06:05.120 in planning and zoning commission direction on what we need to take to the full bodies 00:06:05.120 --> 00:06:11.780 in order to amend the code. So we work through this, staff, professional staff bring forth 00:06:11.780 --> 00:06:18.480 recommendations, reviews other municipalities, looking at some of the legislative changes 00:06:18.480 --> 00:06:23.720 that have occurred, and we'll provide options as well as making recommendations for the 00:06:23.720 --> 00:06:29.240 committee to work through. Once the committee completes their work, they'll be making recommendation 00:06:29.240 --> 00:06:35.760 to again, planning and zoning commission and city council for their ultimate discussion 00:06:35.760 --> 00:06:43.480 and consideration approval. We're going to have these meetings just to continue to get 00:06:43.480 --> 00:06:48.240 that direction and to make sure our direction is as current as possible. Knowing that it's 00:06:48.240 --> 00:06:53.680 been a year of utilizing the code, our planning and zoning as well as councils had an opportunity 00:06:53.680 --> 00:06:59.720 to work through it. They've heard from the development community and our citizens and 00:06:59.720 --> 00:07:03.320 just an ideal time for us to make sure that we're updating and we're as current as we 00:07:03.320 --> 00:07:11.000 can be. So with that, I will turn this over to Mr. Ron Mangida. This is a fairly informal 00:07:11.000 --> 00:07:18.120 process. I want to make sure that any of the DCRC members, if they have questions or comments, 00:07:18.120 --> 00:07:22.360 can either raise their hand or feel free to speak up. I want to continue to try to keep 00:07:22.360 --> 00:07:27.160 this as fluid as possible. We have a lot of material to cover in a short period of time 00:07:27.160 --> 00:07:36.160 and have all the hopes to get it done. So thank you and Ron, take over, sir. 00:07:36.160 --> 00:07:43.040 Thank you, Scott. As Scott mentioned, we do have a lot to cover in a short amount of time 00:07:43.040 --> 00:07:48.360 and we really want to get started. We're excited to get started. But before we do, we wanted 00:07:48.360 --> 00:07:56.280 to have this organizational meeting with the DCRC to get input as far as when our meetings 00:07:56.280 --> 00:08:02.440 are to be scheduled. As you all know, as part of this effort, our meetings will be virtual. 00:08:02.440 --> 00:08:08.640 It will be recorded and it's actually being displayed on our website as we speak. Folks 00:08:08.640 --> 00:08:13.720 will be able to, if they wanted to come back and watch the DCRC meetings similar to any 00:08:13.720 --> 00:08:21.680 other published or recorded meeting, they can. They'll have the availability to do that. 00:08:21.680 --> 00:08:29.180 So again, these meetings will be virtual and recorded moving forward until decided otherwise. 00:08:29.180 --> 00:08:37.960 So the first question to the DCRC, and I'm going to ask Chair Ryan to help with this, 00:08:37.960 --> 00:08:42.040 is weekly meetings. I know that in the past we've had weekly meetings and I think it's 00:08:42.040 --> 00:08:47.720 beneficial if we start with weekly meetings and that may change. But how does everyone 00:08:47.720 --> 00:08:52.840 feel about weekly meetings? Again, because we want to cover a lot of stuff, we feel that 00:08:52.840 --> 00:09:00.600 we need weekly meetings. So I'm going to turn it back to Chair Ryan and kind of get a consensus 00:09:00.600 --> 00:09:03.000 on weekly meetings. 00:09:03.000 --> 00:09:13.080 Any comments? Council Member Briggs? I'm fine with the weekly meetings. 00:09:13.080 --> 00:09:21.880 Anyone else? I guess, Ron, one of the questions I have is since we've gone to this virtual 00:09:21.880 --> 00:09:27.080 where the city's only doing one meeting per week that's being recorded or one meeting 00:09:27.080 --> 00:09:32.520 per day, which means our schedules are kind of all over the place for those of us that 00:09:32.520 --> 00:09:38.200 are on multiple committees. I can't really say I'm always good on Wednesday, but I've 00:09:38.200 --> 00:09:43.120 got at least one day each week that I can do it. Is there a way to kind of work around 00:09:43.120 --> 00:09:46.840 the other committee meetings and have the different days? 00:09:46.840 --> 00:09:53.040 Certainly. I think once we establish that a weekly meeting is something that the DCRC 00:09:53.040 --> 00:09:57.600 is willing to do, we can start to look at the calendar. So the next question that I 00:09:57.600 --> 00:10:04.680 have on the slide is what day of the week we would like for this meeting to occur. 00:10:04.680 --> 00:10:07.320 Let me go back to my screen. 00:10:07.320 --> 00:10:16.720 Ron, and to Council Member Ryan's point, so we do have some restrictions on the when, 00:10:16.720 --> 00:10:24.360 and so it can't conflict with what DTV needs to be able to do. So I think if we can at 00:10:24.360 --> 00:10:30.520 least get the feedback and the input from the committee on preferences, we'll go back 00:10:30.520 --> 00:10:37.920 between the City Secretary's office and DTV and line out what's available. And then we 00:10:37.920 --> 00:10:44.840 may send out a survey monkey or a zoomerang and nail that down to make sure whatever we 00:10:44.840 --> 00:10:50.320 can get that would be static. So it's consistent as to when we're going to have it, it won't 00:10:50.320 --> 00:10:57.080 conflict with what DTV needs. 00:10:57.080 --> 00:11:01.040 And I would say generally speaking, Wednesdays or Fridays are fine, are the best days for 00:11:01.040 --> 00:11:09.640 me unless there is another city meeting going on at the same time or on that same day. 00:11:09.640 --> 00:11:11.640 Which day did you say, John? 00:11:11.640 --> 00:11:24.640 Wednesdays or Fridays? Well, when would these start? I mean, just 00:11:24.640 --> 00:11:30.040 like whatever this week and then if we schedule it to be next week and then so forth, so on. 00:11:30.040 --> 00:11:35.280 Try to do it consistently. Chris, if we can just find it a time that would work for most 00:11:35.280 --> 00:11:42.560 everyone that we could do this and then again, trying to be as static as possible for DTV 00:11:42.560 --> 00:11:48.120 and not bounce around. So just looking for what our best options might be. 00:11:48.120 --> 00:11:57.320 What yeah, Fridays at least, I mean, obviously I'm limited in my scope of so I don't know 00:11:57.320 --> 00:12:05.120 how much y'all want to add me into that. But my next two Fridays are pretty much taken. 00:12:05.120 --> 00:12:18.480 So yeah, I got to get a new draft in 27. Hey Rosa, Rosa, yes, you're unmuted. 00:12:18.480 --> 00:12:25.160 I am so sorry. I was supposed to be muted. My apologies. 00:12:25.160 --> 00:12:32.200 No worries. Yeah, so I and then my Thursdays, I mean, 00:12:32.200 --> 00:12:42.320 I've got big board meeting on the the 20. What is that? 22nd. But the Thursday after 00:12:42.320 --> 00:12:50.600 so I don't know if I'm gonna be much help. And because I said I don't mean I don't but 00:12:50.600 --> 00:12:55.000 November 3rd is coming up so it only be I don't want to impact when y'all meet based 00:12:55.000 --> 00:13:02.000 upon my schedule because it's so so are Wednesdays okay for you, Chris or Wednesdays bad? 00:13:02.000 --> 00:13:08.280 Well, we'll kind of drill into that I guess if if Wednesday gets you to a day versus a 00:13:08.280 --> 00:13:13.360 Friday, john had mentioned Wednesday and Friday being a preference so I don't know if yeah 00:13:13.360 --> 00:13:21.720 Wednesdays Wednesdays are okay in the afternoon. Yeah, I say afternoon, lunch or after. Yeah. 00:13:21.720 --> 00:13:28.600 Yeah. And also saying Wednesdays as I'm going back 00:13:28.600 --> 00:13:34.120 through my calendar a little bit more that's when mobility is meeting on on one of the 00:13:34.120 --> 00:13:41.840 Wednesdays and on the other one. So as I look through it, I'm actually okay on on Mondays 00:13:41.840 --> 00:13:48.200 as long as we're not going past about three o'clock. Councilmember Briggs. 00:13:48.200 --> 00:13:56.080 Yeah, I was gonna make the comment about mobility as well one of those days and then the economic 00:13:56.080 --> 00:14:01.480 development Partnership Board is also on a Wednesday. I think it's the second Wednesday 00:14:01.480 --> 00:14:06.320 of the month the mobility seems to be the last Wednesday of the month. I'm in the same 00:14:06.320 --> 00:14:13.480 boat as the mayor I may or may not have very many meetings with this group but for the 00:14:13.480 --> 00:14:21.440 next few weeks. I'm okay on Wednesdays and Fridays and Mondays we have generally that's 00:14:21.440 --> 00:14:29.000 when our Committee on the environment meets but that's only one time for the month. 00:14:29.000 --> 00:14:37.960 Scott, I'd like to mention every other Monday or at least two Mondays a month PV also meets 00:14:37.960 --> 00:14:44.800 on Mondays. Okay. Thank you, Becky. 00:14:44.800 --> 00:14:52.480 Any other comments or input. The chair, what I think we can do from what 00:14:52.480 --> 00:15:05.000 I've heard is look at the meeting room schedule, obviously, as well as DTV and look at Wednesdays 00:15:05.000 --> 00:15:13.360 afternoon and Fridays as far as availability and then we'll go from there but again, looking 00:15:13.360 --> 00:15:18.040 possibly Wednesdays as a static meeting and or Friday as a static meeting. 00:15:18.040 --> 00:15:26.680 I'll have Charlie Charlie Rosendahl send out a survey monkey to all six of you and we'll 00:15:26.680 --> 00:15:32.040 line out in coordination with the city secretary's office DTV and then kind of the basis of that. 00:15:32.040 --> 00:15:38.540 I think the other part would be length of time or is is the committee comfortable with 00:15:38.540 --> 00:15:45.560 a two hour meeting like we were doing to the past and over lunch is that an issue the 12 00:15:45.560 --> 00:15:53.080 o'clock window is that a problem for anyone. It can be for me if it's on a Wednesday. 00:15:53.080 --> 00:15:58.600 Okay. Yeah, that's fine. 00:15:58.600 --> 00:16:07.920 Margie can't hear you. Okay, sorry. Can you hear me now? Yeah, okay. 00:16:07.920 --> 00:16:14.000 I assume the quorum is made up of the three council people as in the past. Is that correct? 00:16:14.000 --> 00:16:22.740 That is correct. Okay. 00:16:22.740 --> 00:16:28.920 Anyone else? Alright, I guess we'll just watch for that survey monkey to come out and take 00:16:28.920 --> 00:16:34.300 it from there. And then I heard that two hours is fine and 00:16:34.300 --> 00:16:40.120 over lunch is a possibility. Just again, depending on what day but a two hour timeframe, we may 00:16:40.120 --> 00:16:44.920 not use all two hours, but it gives us a little bit more time if we need to pass that first 00:16:44.920 --> 00:16:51.080 hour if we needed to address a certain important topic. 00:16:51.080 --> 00:17:01.080 Okay. Okay. I think that we've basically got what we need as far as the day of the week. 00:17:01.080 --> 00:17:05.700 The start time, it depends on the schedule, but we'll definitely see if we can establish 00:17:05.700 --> 00:17:12.080 a standing meeting if possible and time as well. Looking at a minimum or at least two 00:17:12.080 --> 00:17:17.680 hours, no more than two hours. So agendas obviously need to be posted 72 hours prior 00:17:17.680 --> 00:17:22.680 as similar to the other boards and commissions or committees. Presentations will be made 00:17:22.680 --> 00:17:31.920 by staff and of course discussion with the DCRC. We'll also have minutes as part of these 00:17:31.920 --> 00:17:38.480 meetings so that those will be available if we need to refer back to them. 00:17:38.480 --> 00:17:47.480 The idea is to have a presentation that's consistent so when we bring forward our proposed 00:17:47.480 --> 00:17:53.280 or recommended code amendments, some of you have seen this presentation before, just identify 00:17:53.280 --> 00:18:00.800 what the current rule is or what we have to buy from or buy and at least list the issues 00:18:00.800 --> 00:18:07.640 that we have that are causing the code amendment, what we have currently in the DDC and then 00:18:07.640 --> 00:18:14.760 the options that we have available and then staff's recommendation as we bring forward 00:18:14.760 --> 00:18:21.040 these code amendments, as well as additional slides will be presented during these presentations 00:18:21.040 --> 00:18:28.800 to help illustrate again what we are trying to get input from, from the DCRC. So that 00:18:28.800 --> 00:18:37.240 will be part of the presentation similar to what you guys have seen with past code amendments. 00:18:37.240 --> 00:18:41.960 I know that there were some folks that may have missed this presentation, but I just 00:18:41.960 --> 00:18:47.200 wanted to go through this and just more of a refresher and/or some information for you 00:18:47.200 --> 00:18:54.120 all regarding the DDC amendments. So why are we doing it today now? Obviously, there are 00:18:54.120 --> 00:18:59.300 non-conformities that were created with the 2019 DDC and we want to continue to address 00:18:59.300 --> 00:19:03.960 those non-conformities. We want to align with new regulations or requirements that were 00:19:03.960 --> 00:19:09.920 passed by state law, specifically House Bill 3167. So some of these code amendments will 00:19:09.920 --> 00:19:17.360 reflect that. We continue to provide improvements in our development review process and we want 00:19:17.360 --> 00:19:23.640 to make sure that those improvements are codified in our DDC so that when we are referencing 00:19:23.640 --> 00:19:30.360 our requirements or standards in our process, it is codified for not just the development 00:19:30.360 --> 00:19:37.200 community but the general public as well. And we continue to look and hear from folks 00:19:37.200 --> 00:19:42.680 that have feedback and input regarding DDC, the general public, development community, 00:19:42.680 --> 00:19:50.080 PNZ, and city council. So we want to make sure that we address those issues with a required 00:19:50.080 --> 00:19:59.600 code amendment if that is the resolution. We have identified a list of four categories 00:19:59.600 --> 00:20:06.320 of code amendments. The first one is priority changes. The second one is substantive changes. 00:20:06.320 --> 00:20:12.760 These are ones that we are looking for the DCRC to provide feedback and direction to 00:20:12.760 --> 00:20:17.520 staff. We also have a set of code amendments that are referred to as the criteria manual 00:20:17.520 --> 00:20:22.200 transfers. These are specifically texts and language and standards that are currently 00:20:22.200 --> 00:20:28.360 in the criteria manual that we feel should be in the DDC. And then the last item, not 00:20:28.360 --> 00:20:33.480 a high priority but something that we need to address are non-substantive changes, just 00:20:33.480 --> 00:20:40.920 corrections, references that need to be included or were incorrectly referenced, and also any 00:20:40.920 --> 00:20:48.880 additional language that would provide clarity as to make it clear to understand. I'm going 00:20:48.880 --> 00:20:54.920 to go and share us a working document that we have and that we will be forwarding to 00:20:54.920 --> 00:21:06.800 the DCRC. It is our list of code amendments, and as you can see, the references or the 00:21:06.800 --> 00:21:13.880 document itself, you have it. You'll see that it's color coded, similar to what you've 00:21:13.880 --> 00:21:20.680 seen in the PowerPoint slide. Anything black is non-substantive. Anything that is in purple 00:21:20.680 --> 00:21:26.760 are criteria manual transfers. Anything that is green is what we've identified as substantive 00:21:26.760 --> 00:21:32.520 changes. And then anything red are our high priority. And you can see as I scroll here 00:21:32.520 --> 00:21:36.280 that as we look- Just talk about number one. Explain number 00:21:36.280 --> 00:21:42.440 one. Number one, for example, is just one of those non-substantive changes. The reference 00:21:42.440 --> 00:21:49.200 that we have in the DDC is wastewater, and it's separated. The right reference to this 00:21:49.200 --> 00:21:57.400 is one word versus two words. So that is just a cleanup or a correction that we have identified. 00:21:57.400 --> 00:22:02.400 And again, this is one of many. I think the majority of these code amendments are similar 00:22:02.400 --> 00:22:07.800 in this nature, that they're just corrections. The same with number two. 00:22:07.800 --> 00:22:13.720 I'm sorry, Ron. Also explain that each of those sections, each of those are numbered 00:22:13.720 --> 00:22:20.600 out, and we'll get to what section it is when we get to those, but also we have the rationale, 00:22:20.600 --> 00:22:24.240 so please. Correct, correct. So this is obviously, it's 00:22:24.240 --> 00:22:27.960 numbered, and it's throughout the DDC, so it's not just one section. It's throughout 00:22:27.960 --> 00:22:34.200 the DDC. This correction would apply. The same with this number two. We have a change 00:22:34.200 --> 00:22:38.920 in the term site plan to zoning compliance plan, and that is the term that we're currently 00:22:38.920 --> 00:22:44.040 using as part of our development review process, so we want to make sure that what we're telling 00:22:44.040 --> 00:22:51.640 folks is consistent and is included in the DDC. Number three is more of a substantive 00:22:51.640 --> 00:22:58.080 change, because we're changing the requirement for pre-applications currently, or as part 00:22:58.080 --> 00:23:04.560 of the 2019, it's required to have a pre-application. However, we are changing that to a recommendation 00:23:04.560 --> 00:23:09.880 rather than a requirement, so that is something that we will need from the DCRC as far as 00:23:09.880 --> 00:23:16.640 direction, and again, we have the reasons associated with each of these. I'm gonna scroll 00:23:16.640 --> 00:23:23.760 down so we can see ones that are per the section. So here's an example where you have the reference 00:23:23.760 --> 00:23:30.400 section where we're amending section 1.3.4. What is being changed? Again, based on the 00:23:30.400 --> 00:23:36.880 color, this is a substantive change, so we require or we want to hear from the DCRC to 00:23:36.880 --> 00:23:44.320 move forward, and again, as you've seen, there's a reason to why these code amendments are 00:23:44.320 --> 00:23:50.320 requested or recommended. Sometimes it's just a cleanup and part of the reasons why we're 00:23:50.320 --> 00:23:56.440 doing code amendments. Sometimes there's some specific reasons why it needs to be changed. 00:23:56.440 --> 00:24:02.060 So again, I won't go through this whole list. It's about 85 pages. There's a number of amendments 00:24:02.060 --> 00:24:08.780 that are listed here and categorized. What we plan on doing is sending this to you all 00:24:08.780 --> 00:24:13.880 in the near future with a big draft on it because it's still a draft, and it will give 00:24:13.880 --> 00:24:19.120 you an idea of some of the items that we would like to bring forward, and again, it'll be 00:24:19.120 --> 00:24:26.120 organized as we move forward by those categories that we've just summarized a little bit in, 00:24:26.120 --> 00:24:30.780 which I will be sharing with you in a few seconds here. So does anybody have any questions 00:24:30.780 --> 00:24:36.400 with regards to this document? Again, it is our working document, but we really wanted 00:24:36.400 --> 00:24:42.320 to share it with you all so that you have an idea in advance of what staff is thinking. 00:24:42.320 --> 00:24:49.760 Obviously, it will be a draft. All of this will be draft until we hear and get obviously 00:24:49.760 --> 00:24:53.520 the direction and ultimately the consideration from the full council. 00:24:53.520 --> 00:25:00.160 Ron, if I might piggyback on that. So this document, you'll be sent in its entirety, 00:25:00.160 --> 00:25:10.080 so don't be scared because it's like 85 pages. The 85 pages, the vast majority are just corrections. 00:25:10.080 --> 00:25:14.640 Another part to that is so this document, when it first goes out, will kind of be that 00:25:14.640 --> 00:25:22.040 parent document. We'll keep that as a strike through and comment, so we'll know exactly 00:25:22.040 --> 00:25:27.960 what has changed throughout the entirety. But if we get to a section that we agree on 00:25:27.960 --> 00:25:34.320 how that's to move forward, we'll do a save as each week and send the updated document. 00:25:34.320 --> 00:25:41.720 So as we work through this and we get 10 meetings into this and we want to know what happened 00:25:41.720 --> 00:25:47.240 on a previous item that we'll be able to look at it and see it, but you'll have at least 00:25:47.240 --> 00:25:53.660 the most current decision that was made by this committee before it goes to council and 00:25:53.660 --> 00:25:58.080 ultimately in ordinance form. So it's a working document and just gives 00:25:58.080 --> 00:26:10.880 you a good roadmap of this, the significant changes and what we're going to be doing. 00:26:10.880 --> 00:26:13.440 So I'm going to go ahead and continue with the presentation. I think we've got a couple 00:26:13.440 --> 00:26:22.320 more slides here. Just diving in a little bit more on these categories. The priority 00:26:22.320 --> 00:26:30.160 change topics, some of these I know that the council had discussed in a prior work session. 00:26:30.160 --> 00:26:35.400 We also want to take it to the Planning and Zoning Commission. So batch one is what we're 00:26:35.400 --> 00:26:44.800 thinking of as far as items on the next DCRC meeting to get some input and feedback, which 00:26:44.800 --> 00:26:49.160 will ultimately bring forward to the Planning and Zoning Commission and city council. After 00:26:49.160 --> 00:26:57.600 batch one, we'll dive into batch two. And then again, those will be items that staff 00:26:57.600 --> 00:27:03.720 will be requesting direction from the DCRC, again, ultimately to the PNZ and then city 00:27:03.720 --> 00:27:09.560 council. Substantive changes, there is a number of 00:27:09.560 --> 00:27:15.360 code amendments that are related to these types of code amendments. The first three 00:27:15.360 --> 00:27:20.720 that you see here are ones that the DCRC has already discussed. So I don't anticipate a 00:27:20.720 --> 00:27:29.260 lot of discussion. I know that there was a lot of already directions made and recommendations. 00:27:29.260 --> 00:27:33.960 We just want to summarize that as we move forward with those code amendments. And then 00:27:33.960 --> 00:27:40.200 go into the next set of code amendments as it relates to these categories or these listed 00:27:40.200 --> 00:27:45.560 topics that you see here from subchapter two, which is the administrative and procedures 00:27:45.560 --> 00:27:53.000 section, our subchapter, and then getting into more of the standards and the requirements 00:27:53.000 --> 00:28:00.040 that you see here when it comes to the uses, landscaping, parking, and other site design 00:28:00.040 --> 00:28:07.880 requirements. So again, a lot of these are substantive changes that we just really need 00:28:07.880 --> 00:28:12.880 the DCRC to give us direction so that we can bring forward to the Planning, Zoning Commission 00:28:12.880 --> 00:28:21.080 and city council. These are the criteria manual transfer topics. As you all know, we are working 00:28:21.080 --> 00:28:29.720 and Becky's group has been working on identifying sections of the criteria manual for stormwater, 00:28:29.720 --> 00:28:36.400 water and wastewater and looking at where those language and those requirements are 00:28:36.400 --> 00:28:43.680 better suited and better included in the DDC. And so that is what these code amendments 00:28:43.680 --> 00:28:49.160 will be. It's essentially just introducing those languages from the criteria manuals 00:28:49.160 --> 00:28:57.600 into the DDC. We have similar topics or similar languages and texts from the transportation 00:28:57.600 --> 00:29:06.240 criteria manual, the solid waste criteria manual, and also the electric service standards. 00:29:06.240 --> 00:29:11.760 Wanted to include number six and number seven in this discussion just to provide you with 00:29:11.760 --> 00:29:18.360 an overall comprehensive look at what we're trying to do with our documents that we use 00:29:18.360 --> 00:29:26.000 in reviewing plans and design. We also have specifications and standard details that are 00:29:26.000 --> 00:29:31.560 being currently being reviewed. And my understanding is that this is going to be being will be 00:29:31.560 --> 00:29:38.360 brought forward to the full council for consideration in the near future. But it is a document that 00:29:38.360 --> 00:29:47.080 we also look at when reviewing our plans and design that are submitted to the city. Lastly, 00:29:47.080 --> 00:29:52.800 number seven is a development handbook where there is a lot of our processes that are not 00:29:52.800 --> 00:30:00.440 necessarily in the DDC per se, but are helpful for our general public, our development community, 00:30:00.440 --> 00:30:05.280 and this is something that we're working as well. So ultimately our goal is to have all 00:30:05.280 --> 00:30:11.080 of these included in either to the DDC or part of the criteria manual where it's a little 00:30:11.080 --> 00:30:20.880 bit more concise, less duplicative, and it's easier for everyone to understand. The last 00:30:20.880 --> 00:30:26.680 here is just the non-sensitivity changes, and we saw some examples of that earlier. 00:30:26.680 --> 00:30:33.760 Again, just typos and correcting references that are obviously were not correct. This 00:30:33.760 --> 00:30:40.160 is the schedule that we are planning on having. Obviously, we are pretty tight in trying to 00:30:40.160 --> 00:30:46.000 get them done, but we want to at least try to get them as much done as possible that 00:30:46.000 --> 00:30:52.100 is. There may be some that will have to fall to the next year, but as we continue through 00:30:52.100 --> 00:30:57.720 this effort, we want to make sure that you all know the schedule, and if we need to provide 00:30:57.720 --> 00:31:04.040 updates, we can certainly do that. But we want to tackle the priority changes first, 00:31:04.040 --> 00:31:12.240 get into the substantive changes, and then hitting the criteria manual transfers as well, 00:31:12.240 --> 00:31:18.720 and throughout all this, the non-substantive changes will be discussed throughout our meetings 00:31:18.720 --> 00:31:26.440 that we have with the DCRC. That concludes my presentation, and again, just wanted to 00:31:26.440 --> 00:31:33.560 thank you all for participating in this effort, and as we start to schedule the meetings that 00:31:33.560 --> 00:31:38.440 we have already discussed, we will make sure that you have the information well in advance, 00:31:38.440 --> 00:31:43.560 and we will be presented to you in a clear format so that, again, we can get your input 00:31:43.560 --> 00:31:46.560 in direction. 00:31:46.560 --> 00:31:47.560 >> Councilmember Briggs. 00:31:47.560 --> 00:31:55.320 >> I have a few questions, Ron, going back to the presentation. On page 10, I mean page 00:31:55.320 --> 00:32:04.760 9, I think it had HLC and ZBA listed as composition changes, and I'm wondering, did that or did 00:32:04.760 --> 00:32:09.760 those suggestions come from those boards, or did it come from -- where are those changes 00:32:09.760 --> 00:32:10.760 coming from? 00:32:10.760 --> 00:32:16.640 >> Sure. Let me pull that up so we can see that real quick. 00:32:16.640 --> 00:32:21.640 >> There were legislative changes that are prompting some of this. 00:32:21.640 --> 00:32:22.640 >> Okay. 00:32:22.640 --> 00:32:26.840 >> So for the ZBA specifically, there was a House bill that was passed. We want to make 00:32:26.840 --> 00:32:34.000 sure that the procedure section was included in the DDC as a result. As far as the composition, 00:32:34.000 --> 00:32:41.320 when we tried to amend the DDC back in 2019, there were things that we were going to include 00:32:41.320 --> 00:32:47.120 into the code of ordinances where some of these boards and commissions composition are 00:32:47.120 --> 00:32:53.680 located. However, we felt that it should be further clarified, specifically with the HLC 00:32:53.680 --> 00:32:58.840 as part of the DDC as well. So it's more or less a cleanup, nothing new specifically 00:32:58.840 --> 00:33:04.240 that we're trying to introduce. It's more or less making sure that it's covered in the 00:33:04.240 --> 00:33:11.240 DDC. We'll obviously make sure, and we have meetings scheduled with the ZBA and HLC next 00:33:11.240 --> 00:33:15.280 month in November, and we will be sharing with them some of what we're proposing to 00:33:15.280 --> 00:33:20.200 add into the DDC as it reflects their board and their commission. 00:33:20.200 --> 00:33:31.280 >> Okay. Thank you. Chair, I have one more question. On page 10, about the criteria manuals, 00:33:31.280 --> 00:33:37.960 and just help me remember, because I thought that we had specific direct you to those manuals 00:33:37.960 --> 00:33:42.400 because they're updated more regularly, and so I'm wondering why we're going back and 00:33:42.400 --> 00:33:49.960 integrating those into the text of the code unless I'm misunderstanding something. 00:33:49.960 --> 00:34:00.000 >> No, you're spot on. We had some concerns that were expressed through legal that some 00:34:00.000 --> 00:34:03.040 of these provisions need to be in the code, and that's why we're going to talk through 00:34:03.040 --> 00:34:08.720 those with the committee. >> Okay. So they'll just be pulled out of 00:34:08.720 --> 00:34:15.400 that and into the code, and then -- >> Correct. We won't necessarily lose anything. 00:34:15.400 --> 00:34:21.200 It's just where's the appropriate document for those components to be. So some of that 00:34:21.200 --> 00:34:28.400 will be in the criteria manual, and others of it will be within the code. 00:34:28.400 --> 00:34:33.560 >> My understanding is that those criteria manuals will continue to be reviewed annually, 00:34:33.560 --> 00:34:40.760 and if there is a need for an ordinance to amend it, that will also be done again as 00:34:40.760 --> 00:34:47.060 needed. >> Okay. Thank you. 00:34:47.060 --> 00:34:53.320 >> I might also suggest, Ron, on the slides, because we are being televised, that people 00:34:53.320 --> 00:35:00.200 may have questions, if -- whether it's your email address or planning@cityofdenton.com, 00:35:00.200 --> 00:35:06.280 that every one of the slides has a line on there that, if you have questions, email this, 00:35:06.280 --> 00:35:14.920 and then we can monitor that as well. So not necessarily as live, but certainly if we have 00:35:14.920 --> 00:35:19.680 individuals that are viewing this, that they're able to easily get to whoever they need to. 00:35:19.680 --> 00:35:26.200 >> We'll make sure that happens. >> Councilmember Riggs? 00:35:26.200 --> 00:35:31.800 >> I just have one last question. I know that in the introductions, we learned about a new 00:35:31.800 --> 00:35:36.360 law firm, and that's helping us. The last time we did this, we had, I think, was it 00:35:36.360 --> 00:35:43.440 Ms. McDonald from a different law firm? Was that -- is she going to be involved in this 00:35:43.440 --> 00:35:49.640 update or no? >> No. I believe we're just going to be using 00:35:49.640 --> 00:35:53.840 Borquez, and I don't know if Erin wants to speak to any of that or not, but currently, 00:35:53.840 --> 00:35:57.080 that's who we're utilizing. >> Okay. 00:35:57.080 --> 00:36:02.560 >> I can answer that, Councilmember Briggs. A lot of the work, as was explained to me, 00:36:02.560 --> 00:36:08.280 were primarily related to actually planning issues, not necessarily legal issues. Robin 00:36:08.280 --> 00:36:14.400 Meagher is an actual planner that happens to work in a law firm, so that's why we went 00:36:14.400 --> 00:36:19.760 to the Borquez law firm, and a lot of the legal issues, you know, we can -- if they 00:36:19.760 --> 00:36:24.000 do arise, we can handle those internally as well. 00:36:24.000 --> 00:36:37.080 >> Okay. Thank you for that. >> Anyone else? Additional questions? Ron, 00:36:37.080 --> 00:36:42.720 did you have anything else, or is that -- >> That's all we have. As far as input needed, 00:36:42.720 --> 00:36:52.800 I think we got as far as the meetings regarding when, how long, and start time and weekly 00:36:52.800 --> 00:36:58.840 meetings. So we'll start to push that as soon as we can get some calendars in place and 00:36:58.840 --> 00:37:03.880 send you all some surveys so that we can get going on these code amendments. 00:37:03.880 --> 00:37:09.560 >> I'd like to just personally, again, thank all of you. Certainly, it was quite daunting. 00:37:09.560 --> 00:37:13.760 We hope this is going to be much more simpler. We hope that the format that we're going to 00:37:13.760 --> 00:37:19.640 provide to you will create that ease, at least that you have, you know, the changes before 00:37:19.640 --> 00:37:24.920 you and the intent of what that is, and certainly give you opportunity to review the material 00:37:24.920 --> 00:37:33.240 in advance. Happy to build the agenda around the committee and, you know, how we move forward. 00:37:33.240 --> 00:37:38.680 Want to make this as fluid and simple as possible and just expedite as much as we can to get 00:37:38.680 --> 00:37:43.600 it done and get it done right. But thank you. 00:37:43.600 --> 00:37:49.000 >> Thank you, Scott. We do have concluding items on here. Anybody have any concluding 00:37:49.000 --> 00:37:56.320 items? All right. Then we will adjourn at 1148. Thank you, everyone. 00:37:56.320 --> 00:37:58.480 >> Thank you, everyone. Thank you.