[16:00] o/ [16:00] o/ [16:02] o/ [16:04] today is US holiday, that might impact attendance in today's meeting [16:05] o/ [16:06] I suppose we have a quorum? [16:06] Oh, no, wait [16:06] We need one more. [16:06] I'm just seeing things [16:08] schopin: while we're waiting, looking at https://udd.debian.org/cgi-bin/ubuntu-sponsorships.cgi?render=html&sponsor=&sponsor_search=name&sponsoree=*chopin*&sponsoree_search=name it's notable that you don't have an endorsement from ginggs even though he sponsored a very large number of your uploads. [16:09] ginggs: ^ [16:09] Could you get feedback from him please? IMHO it's quite a big issue if a major sponsor doesn't consider you ready. [16:10] I had his agreement to add his endorsement, but I'm guessing he hasn't had the time. [16:10] I'm here [16:12] hi [16:12] I guess we have a quorum. Who was to chair today? [16:13] sorry, i meant to add an endorsement, but it slipped through the cracks. i believe schopin is ready to be a core-dev, i'll write something quick right now [16:14] ginggs: thank you! [16:15] Okay, maybe in this case I'll try to chair, if there are no objections [16:15] I'll just need a minute [16:16] #startmeeting Developer Membership Board [16:16] Meeting started at 16:16:28 UTC. The chair is sil2100. Information about MeetBot at https://wiki.ubuntu.com/meetingology [16:16] Available commands: action, commands, idea, info, link, nick [16:17] One proposition I had: what would everyone think of moving the format a little bit, so that we handle applicants at the beginning of a meeting? [16:17] I suppose we should have a formal discussion/vote about that first, right? [16:17] I think that's fine, and you're the chair so you get to decide. [16:17] Since I'm always worried that the applicants have to wait until we're done with all the review items etc. unnecessarily [16:18] Maybe just ensure that there aren't any previous action items holding up applicants. [16:18] True [16:18] On the principle of giving applicants priority, strong +1 :) [16:18] +1 from me too [16:18] Ok, I think we're good from this POV, let's try that then [16:18] #topic Ubuntu Core Developer Applications [16:19] #subtopic Simon Chopin [16:19] #link https://discourse.ubuntu.com/t/simon-chopin-core-dev-application/28291 [16:19] schopin: o/ [16:19] o/ [16:19] schopin: hello! Can you introduce yourself briefly? [16:20] Hi! I am Simon Chopin, I'm a French software developer within the Foundations team of Canonical. [16:21] Questions? [16:21] Could you elaborate on how you could do better with attention to detail? [16:23] schopin: ^ ? [16:24] I oftentimes do small mistakes such as targetting the wrong series when uploading. Since I know this, it shouldn't happen, and yet... [16:25] schopin: Do you have any plans for avoiding small mistakes in the future? [16:25] I'm not sure if you're done, but I have a couple of questions when you're ready. [16:26] Oh sorry, I'll wait [16:28] bdmurray: besides looking into why dch -r targets my current series and not devel by default, I think I need to take the time to develop some "rituals"/checklists, and also some more wrappers. [16:29] Okay, thanks. Go ahead rbask [16:29] Could you tell me about feature freeze please? How do you determine if a freeze is active? If feature freeze is active, then how do you decide if feature freeze would apply to a package for example for an upstream version moving from 1.2~rc2 to 1.2? And if you need an exception, how do you request one? [16:34] After a few months of "open" development of the devel series, the archive enters Feature Freeze, during which autosync with Debian is disabled. To see when that happens I'd go to the release schedule on Discourse, or check the topic in #ubuntu-devel. We can upload to the archive if to fix bugs. New upstream releases are usually not uploaded, except if they are purely bugfix releases, which [16:34] I'd expect in 1.2~rc2 to 1.2. If I need an exception, I'll open a FFe bug against the package, attaching the debdiff that I want to upload, and subscribe the release team. [16:36] rbasak: ^ [16:36] How would you decide if something is a purely bugfix release or not? [16:39] I'll have a look at upstream's changelog and commit history. If they don't have the former and the latter is inexploitable, I'll probably err on the side of caution and not upload unless I know and trust upstream (which is unlikely if they don't have those two elements) [16:39] It helps if they have an explicit release policy. [16:41] Sometimes it's hard to decide if it's a bugfix or a feature, in which case I'll ask on #ubuntu-release [16:41] OK thanks. One more question from me please. How would you check if an upload will trigger a component mismatch? [16:43] I'm making this one up so this might be wrong, but I guess I could somehow run germinate? Previously I did it manually but I missed the rustc/llvm-13/z3 chain, so... [16:45] OK thanks. I have no further questions [16:45] No questions from me [16:45] kanashiro: questions? [16:45] schopin, let's suppose you uploaded a package to the development release and it caused a component mismatch, what are the possibilities to sort this out? [16:46] MIR the component, or somehow fix the package relationship that caused the component mismatch, by e.g. drop a Recommends into a Suggests. [16:46] schopin, thanks. [16:47] no further questions [16:48] Okay, time for the vote [16:48] #startvote schopin to become core-developer [16:49] ...guess that's vote [16:49] #vote schopin to become core-developer [16:49] Please vote on: schopin to become core-developer [16:49] Public votes can be registered by saying +1, -1 or +0 in channel (for private voting, private message me with 'vote +1|-1|+0 #channelname') [16:50] +1 [16:50] +1 received from rbasak [16:50] +1 [16:50] +1 received from bdmurray [16:50] +1 [16:50] +1 received from kanashiro [16:51] +1 [16:51] +1 received from sil2100 [16:51] #endvote [16:51] Voting ended on: schopin to become core-developer [16:51] Votes for: 4, Votes against: 0, Abstentions: 0 [16:51] Motion carried [16:51] schopin: congratulations! [16:51] Thanks :) [16:51] Who wants the action item of adding schopin to the core-dev's team? [16:51] schopin: Congratulations! [16:52] schopin, congrats! :) [16:52] thanks all :) [16:52] I can do it [16:52] rbasak: thanks! [16:52] #action rbasak to add schopin to core-dev [16:52] ACTION: rbasak to add schopin to core-dev [16:53] #action rbasak to announce schopin's successful application [16:53] ACTION: rbasak to announce schopin's successful application [16:53] Ok, moving on, since we only have 7 minutes left [16:53] #topic Review of previous action items [16:53] kanashiro to update our wiki documentation with respect to our agreed packageset creation criteria <- kanashiro ? [16:54] I started to work on that today, unfinished [16:54] Ok, let's carry over then! [16:54] #action kanashiro to update our wiki documentation with respect to our agreed packageset creation criteria (carried over) [16:54] ACTION: kanashiro to update our wiki documentation with respect to our agreed packageset creation criteria (carried over) [16:54] sil2100 update application docs and possibly DMB checklist, to make sure candidates have signed CoC before applying and before DMB approves (carried over) [16:54] I did one part of it (added it to the knowledge base), but need to update other places [16:54] So carry over for now [16:54] #action sil2100 update application docs and possibly DMB checklist, to make sure candidates have signed CoC before applying and before DMB approves (carried over) [16:54] ACTION: sil2100 update application docs and possibly DMB checklist, to make sure candidates have signed CoC before applying and before DMB approves (carried over) [16:54] teward follow up to get all application process wiki/docs to explain the process to be able to edit wiki pages, for applicants who don't yet have wiki edit access (carried over) [16:55] teward is absent (due to holidays), so carrying over [16:55] #action teward follow up to get all application process wiki/docs to explain the process to be able to edit wiki pages, for applicants who don't yet have wiki edit access (carried over) [16:55] ACTION: teward follow up to get all application process wiki/docs to explain the process to be able to edit wiki pages, for applicants who don't yet have wiki edit access (carried over) [16:55] #topic Outstanding mailing list requests to assign [16:55] I don't think we have anything new [16:55] #topic Open TB bugs [16:55] ...none [16:55] #topic AOB [16:55] ...5 minutes left, any other business? [16:57] none [16:57] Okay! Let's wrap it up then! [16:57] #endmeeting [16:57] Meeting ended at 16:57:18 UTC. Minutes at https://ubottu.com/meetingology/logs/ubuntu-meeting/2022/ubuntu-meeting.2022-05-30-16.16.moin.txt [16:57] Thank you everyone! [16:57] thanks for chairing sil2100 ! [16:58] o/ [16:58] congrats @schopin ! === cpaelzer_ is now known as cpaelzer