Over the last few years/months, Jakub Moc has repeatably been abusive towards me with little provocation. I have now had enough. I'd particularly like to draw to your attention a few things, 1) the mass-keyword reassign that took place at 2005-07-18 03:10:23. as I'm in the UK, that's 3am local time, apparently an effort was made to contact me, although that effort was a ping on irc, to "peitolm" Now, it's not documented that I'm on irc as Peit|<something>, however a few people pointed this out to Jakub at the time, but no subsequent contact was made, jut a blanket change, (even disregarding the dev away that was in force at the time. #see bug 35148 for t)he time stamp. I'm including this for completenes. Please also see bugs, 2) #189660 "ebuild is broken, is broken, is broken... I give up, doesn't go anywhere." (if it was broken it wouldn't work at all.) 3) #82772 I note that even though I made no reference to Bug #82772 in my changelog, He still updates the bug with an attack. (without reading the whole of the commit) 4) #143519 Apart from the direct attacks and insults, commenting about other bugs does not help keep a conversation on track. If Jakub has a complaint about my work, then either raising it via email or on IRC(which would require it to be a 2 way conversation) would be the best avenue, failing that on a _separate_ bug, perhaps with a CC to devrel/recruitment/whoever, would be the polite and correct thing to do, a technical bug is _not_ the place for it. I'm going to assign this to fmccor as someone who's done ombudsman in the past and still appears to be happy to play that role. CC'ing Devrel and Jakub Reproducible: Always
Removing the restriction to devrel. I'll be following up on this in a day or so. Jakub, it would help the process if you would contact Colin directly (or Colin, for you to contact Jakub) bacause that will have to happen anyway. For the record so that everyone has about the same information, Colin and I have spoken briefly about the issues raised here, so I am likely to contact Jakub first. Hence, my suggestion that Jakub contact Colin and try to reach some understanding.
(In reply to comment #1) > Removing the restriction to devrel. I'll be following up on this in a day or > so. Jakub, it would help the process if you would contact Colin directly (or > Colin, for you to contact Jakub) bacause that will have to happen anyway. I have no wish to contact Colin. I've spoken to him a year ago, and it went nowhere. Same bugs still there, and everyone gets blamed but the developer in question responsible for the broken ebuilds and ignored bugs. Colin does his quarterly commit which fixing nothing, then goes for holidays, and the bugs are propagating from version to version to version infinitely. This is a QA issue and not a devrel one. Bug 82772, Bug 189660 etc. etc. etc.
(In reply to comment #0) > 1) the mass-keyword reassign that took place at 2005-07-18 03:10:23. Yeah, which happened after about a year has passed while the bugs were being ignored. And yeah and happened again on one year anniversary of your mass re-assigned back to yourself - which guess what - only resulted in the bugs getting ignored again. We've discussed this privately already. If you can't maintain something on a timely manner, then let others do the job and refrain from similar territorial pissings. > Please also see bugs, > 2) #189660 "ebuild is broken, is broken, is broken... I give up, doesn't go > anywhere." (if it was broken it wouldn't work at all.) At least stop misquoting, this is quite ridiculous: <snip> The *mailwrapper* *logic* in the ebuild is broken, is broken, is broken... </snip> > 3) #82772 > I note that even though I made no reference to Bug #82772 in my changelog, He > still updates the bug with an attack. (without reading the whole of the commit) Because it only took 3 years until now, and still it's broken. > 4) #143519 > Apart from the direct attacks and insults, commenting about other bugs does not > help keep a conversation on track. Already mentioned above... drop the territorial pissings when you don't care about fixing bugs. > If Jakub has a complaint about my work, then either raising it via email or on > IRC(which would require it to be a 2 way conversation) would be the best > avenue, failing that on a _separate_ bug, perhaps with a CC to > devrel/recruitment/whoever, would be the polite and correct thing to do, a > technical bug is _not_ the place for it. That conversation already took place on IRC last summer, alas stuff like Bug #82772 is still there almost one year later, and 3 years after the bug has been filed.
(In reply to comment #3) > (In reply to comment #0) > > 1) the mass-keyword reassign that took place at 2005-07-18 03:10:23. > > Yeah, which happened after about a year has passed while the bugs were being > ignored. And yeah and happened again on one year anniversary of your mass > re-assigned back to yourself - which guess what - only resulted in the bugs > getting ignored again. We've discussed this privately already. If you can't > maintain something on a timely manner, then let others do the job and refrain > from similar territorial pissings. > I don't believe this was the case, I'll acknowledge that there were some minor bugs that were over a year old, For example, #83269 was opened and closed only a few months previous > > Please also see bugs, > > 2) #189660 "ebuild is broken, is broken, is broken... I give up, doesn't go > > anywhere." (if it was broken it wouldn't work at all.) > > At least stop misquoting, this is quite ridiculous: > > <snip> > The *mailwrapper* *logic* in the ebuild is broken, is broken, is broken... > </snip> > My bad, however, I still disagree that the mail the logic is broken, see the comment on 2007-05-31 with reference to http://sources.gentoo.org/viewcvs.py/gentoo-x86/mail-mta/exim/exim-4.67-r1.ebuild The _logic_ was fixed then,, following consultation with, if memory serves, Ticho and G2boojum. > > > 4) #143519 > > Apart from the direct attacks and insults, commenting about other bugs does not > > help keep a conversation on track. > > Already mentioned above... drop the territorial pissings when you don't care > about fixing bugs. > Guess what, I do care, however, when every commit I make gets attacked, it's seriously demoralizing, > > If Jakub has a complaint about my work, then either raising it via email or on > > IRC(which would require it to be a 2 way conversation) would be the best > > avenue, failing that on a _separate_ bug, perhaps with a CC to > > devrel/recruitment/whoever, would be the polite and correct thing to do, a > > technical bug is _not_ the place for it. > > That conversation already took place on IRC last summer, alas stuff like Bug > #82772 is still there almost one year later, and 3 years after the bug has been > filed. I don't have a record of that conversation, I will see if I can dig it out, however, I don't recall it being all that productive.
Jakub is retired, so this is no longer relevant.
