/srv/irclogs.ubuntu.com/2019/03/19/#ubuntu-meeting.txt

cpaelzerpreping for doko cyphermox didrocks jamespage and jdstrand13:46
cpaelzersince most of us missed the meeting last few times and today we have something to discuss  (plus being in the week were daylight savings disagree) I thought it is worth to pre-ping :-)13:46
didrockscpaelzer: ahah, almost :)13:51
cpaelzer:-)13:52
cpaelzerbut now ...14:00
didrocksshould be now14:00
cpaelzerI'm actually fine if no one has objections on the email that I sent about the many mailman3 triggered MIRs14:01
cpaelzerbut doko correctly mentioned that it feels odd that the same person files and acks them14:01
cpaelzerso we wanted to discuss how to handle at least some of these14:01
cpaelzerlets give everyone some time to show up14:01
cyphermoxtbh I'd prefer if you just wrote whatever you want to write, so I can pay attention but we don't need to block on anyone14:03
cpaelzercyphermox: well I wrote what I wanted to write (in the mail on Friday)14:03
cpaelzerand I summarized above what doko wanted to discuss14:04
cpaelzermy initial approach was: I will handle all the more trivial MIRs that I opened, and for the more complex cases (or those that I think a Nack is needed or likely) I'd pull one of you in14:05
cpaelzeras mentioned doko said this morning to me that it feels odd that the same guy opens and Acks them14:05
cpaelzerthat is it, opinions about this?14:05
cyphermoxif it's a trivial thing; no14:05
cyphermoxif it feels like there might be contention, then I suppose yeah asking for help is a good plan14:06
didrocksyeah, I always refused to be the person NEWing new packages I upload or ACKing MIR I filed14:06
didrocksit's a little bit like a peer review, never a bad thing to have another person keeping you honest :)14:07
* doko is late 14:07
cpaelzerwell I'm not NEWing the packages they are in Debian/Ubuntu for quite a while, I'm just driving the MIR bugs as requestor and first level reviewer14:07
cpaelzerand I already spread the creation of the MIR requests in our team14:07
cpaelzerHere is a list of all the involved packages and MIR bugs https://git.launchpad.net/~ubuntu-server/+git/mailman3-MIR-party/tree/package-list.txt14:08
cpaelzerI'm trying to make the biggest problems to go away by cutting the dependency to e.g. nodejs and ruby bits14:08
cpaelzertherefore those have no bugs assigned to the Team yet14:08
dokoright, but in the past, the MIR bug submitter was the same as the MIR author14:09
didrockssounds like a MIR list similar the old unity time ;)14:09
cpaelzeryeah didrocks, might be14:09
cpaelzera bit smaller thou I guess14:09
didrockscpaelzer: I can only sympathize :)14:09
cpaelzerso how about letting me doing the first run on all of these - and next week same time we can dirstibute the more interesting cases that are left in the Team14:10
didrockssounds good to me14:10
cpaelzerthis would keep the majority of blunt processing from you, but get your opinions and insights on the cases where it is needed14:11
cpaelzerunless you distrust me that I silently bypass something14:11
cpaelzerin that case I'm very happy to -not- do all those reviews :-)14:11
dokoI can certainly help with stuff14:12
cyphermoxcpaelzer: the only thing that jumps out to me is nose14:12
cyphermoxit was previously in main14:12
cyphermoxI'd be for not dropping the dep; avoiding delta, and just putting it back in main.14:12
dokoare the S tags complete?14:12
dokowe should get these done first14:13
cpaelzercyphermox: I'm ok with handling nose that way - thanks14:13
cpaelzerdoko: the S tags got on the security Teams list just today14:13
cpaelzermore S tagged packages will come14:13
cyphermoxah, and one more thing; how about we decide right now if it's mailman3 or mailman3 + hyperkitty, whatever that is?14:13
cpaelzerit is all of them mailman3-full is the package starting the dependency tree14:14
cpaelzerwe discussed that in the Team upfront and later in Malta14:14
cyphermoxah ok14:14
cpaelzerthe problem is that only core (tag C) or core+archive (tags C+H) is not what people would want to use14:15
cpaelzeryou want a ML with frontent or you don't want a mailing list at all14:15
cpaelzernot promoting all of mailman3-full was just one of the options we evaluated in the past14:15
cpaelzerthanks for the hint on nose cyphermox - I'll give that a check later on14:16
cyphermoxwell, it depends what the server team feels comfortable supporting I guess14:16
cpaelzerbut it is nose(1) not nose2 - was that in main as well?14:16
cyphermoxsrc:nose is what I looked up in rmadison14:17
cpaelzeryeah that is the right one14:18
cpaelzerthanks14:18
cpaelzerI'l do the paperwork and updates in regard to that14:19
cpaelzerand as I said, I hope that next week by that time the list is down to those that I need your help on anyway14:19
cpaelzerok it seems that works for everyone then14:19
cpaelzerdoko: are you ok with distributing only those among the team next week then?14:19
cpaelzerdoko: can we take no answer as a yes and conclude until next weeks meeting?14:26
* cpaelzer thinks doko is busy building two more glibc updates for Disco14:27
dokocpaelzer: sorry, phone call. yes, sounds fine14:34
cpaelzerok, thanks14:34
donofriodang missed the metting wanted to know how do I get inxi to be inxi 3.0.32-00 (2019-02-07) to be included with 19.04?20:43
sarnolddonofrio: what's different between 3.0.32-00 and the 3.0.31-1-1 that's packaged? https://launchpad.net/ubuntu/+source/inxi/3.0.32-1-121:07

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!